I would argue that this fixes the wrong problem, which is that you have privileges granted to people that they are not qualified to hold. Server version: 5.5.30 MySQL Community Server (GPL)ĮRROR 1175 (HY000): You are using safe update mode and you tried to update a table MySQL does have a mode that tries to protect you, by stopping you from executing updates or deletes that aren't using an index to find rows, with the -i-am-a-dummy flag that enables sql_safe_updates on a per-connection basis - or you can enable that setting at a global level on the server. The DBMS's job is to do what you ask in the most optimal way, not second-guess whether you know what you're doing. There is sure-fire no way for the system to correctly guess 'hey, that seems wrong' and ask you to rethink your decision. UPDATE users SET email = - not wrong, updates all rows with same value So you must be talking about something like this: DELETE FROM t1 - not wrong, deletes all of the rows by excluding none

and those aren't going to execute anyway. There is no such thing as a 'wrong' delete or update command unless it is 'wrong' in the sense of being syntactically invalid, referencing nonexistent objects, or attempting something for which the user does not have permission. If i issue some delete/update command wrongly

Sql prompt where clause warning