There has not been any activity on this, except for Friday where we tried for several hours to reproduce this. We cannot. We have never seen this ourselves and have no other reports like this since the one back in 2008. Can you give some hints – for instance:
1) For how long did you have the program open when that happened, and do you remember what operations you had done before that?
2) You are using COMMUNITY version. This only allows for direct connections unless you establish a tunnel of some kind with some other program (Putty/Plink, some VPN software etc.). Do you?
3) Any 'oddities' with database and table identifiers/names (national and rarely used characters)?
4) Are you copying to another server or another database on same server?
5) Anything else about the environment that is non-trivial/unusual you can think of?
Please also tell MySQL server version(s) involved.
'Provoking the error at will' seems quite hopeless as we have tried for hours. The way forward will have to be by code review, I think. However it will be like seeking a needle in a haystack. So if you can reply to above questions it may limit the search to a corner of the haystack.
One possibility is that a specific (and rare) series of operations by user in the GUI causes a DROP statement to be executed before the USE statement,
