As a compromise, wouldn't it be preferable to change the ERROR to a simple HINT instead? The wording of the message resembles a hint, anyway. Then it's not an error (which I also concur) while also informing the user in case of unintentional choice of command. Regarding the view (NPI) expressed that because views and tables are similar objects and share a common namespace, the error makes sense when trying to DROP an existing object of the other type. If we accept this, we can also accept that either command (DROP VIEW or DROP TABLE) should drop the object, regardless of type. I think the OP's complain is valid. With DROP VIEW/TABLE IF EXISTS there should be no errors. And that MySQL does the same gives it extra validity.