MySQLi DELETE
Sara only reaches for MySQLi DELETE when fetch marks by roll has to stay correct in the college DB.
For MySQLi DELETE, Apache/Nginx is in play. Don’t blame it until you have traced fetch marks by roll.
Without MySQLi DELETE, the college DB gets messy and fetch marks by roll is hard to trust.
Use MySQLi DELETE when fetch marks by roll must stay clear. If a simpler PHP step works, use that instead.
If fetch marks by roll breaks under MySQLi DELETE, check string-concat SQL first.
After MySQLi DELETE, Sara should still remember string-concat SQL.
Close MySQLi DELETE with — “If I skip it, fetch marks by roll goes wrong like this: string-concat SQL.”
Say MySQLi DELETE in one breath, then prepared statement, then string-concat SQL.