> According to the commit log, it seems that the purpose > is suppressing to be sent error message to client when "DROP TABLE". > In those days(pre 8.1), we did not have "DROP IF EXISTS" syntax, > so it was useful.
> If this was the reason, now(from 8.2) we have "DROP IF EXISTS" syntax,
Uh, that was one example of what it might be good for; I doubt that the use-case has now vanished entirely. While I'm still dubious about the reliability of suppressing error messages, if people have been using this type of coding for nearly 10 years then it probably works well enough ... and more to the point, they won't thank us for arbitrarily removing it.
Maybe so.
I think we should leave established practice alone here. It might be confusing at first glance, but that doesn't mean it's the wrong thing.
I see. If we delete it, it maybe become more confusing thing.
