MySQL Bugs: #63964: Show create from Workbench

Bug #63964	Show create from Workbench
Submitted:	9 Jan 2012 7:44	Modified:	29 Jan 2013 3:44
Reporter:	Alessio Campani	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	5.2.31, 5.2.37	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
We have a large database with many schemas our system is configured as a replica with a master server and 3 slave servers; when we use Workbench, connected to the master server, to send a "show create" command on a table whose engine is "Memory" we have the following problem.
If we do something in the SQL scratch, such as selecting / copying some string, or cancelling the create statement to write another query, when closing the scratch itself we are asked to keep the modifications. If we refuse hitting "Canc" a delete command is sent to the table whose create statement had been requested, on every schema that has a table with that name. The delete command can be retrieved in the binary logs of the master.
We are using 5.2.31 release of Workbench.

How to repeat:
Using workbench, send a show create command to the SQL editor for a memory table. Do something in the scratch then close the scratch itself.
When requested to keep modifications, hit Cancel.

Please, check if the same problem still happens with a newer version, 5.2.37.

I've set up a test environment and installed the latest release of Workbench (5.2.37). The behaviour is the same: enable the binary logs, select a table (memory engine) , right-click, send to SQL Editor the create statement, edit the SQL scratch and close it. A prompt appears asking to keep the modifications, click on Cancel.
If you open the binary log you can find a delete statement on that table on every schema.

What exact server version, x.y.z, are you working with? I tried to reproduce on Windows XP while working with local server version 5.1.58, but do not see any DELETE statement for the memory table I've created in the general query log...

Are you sure that these DELETEs do not come from other server in your replication setup?

The version of MySQL is 5.1.46; we are pretty sure because the delete statements are written in the binary logs of the master itself.

Can you paste an example of the DELETE statement?

DELETE FROM 'datap2011_1'.'z4_forno_ft'
DELETE FROM 'datap2011_2'.'z4_forno_ft'

Nothing strange...

Is that all? No WHERE ?
I'm looking at the code to see if there's any possibility that such DELETE statements could
be issued from Workbench.

Today the problem has happened also after a simple select statement.
I've sent a select statement via Workbench to the master server of our replication; the table belongs to an historical database who has been compressed with myIsam.
This has caused a delete statement to be sent to all the slave server on many memory tables (the delete statements are written in the master's binary logs)

Are the queries you pasted *exactly* the queries that are being executed?
For example, there are no WHERE statements, while in Workbench I cannot find any code that
could generate such a query, specially with identifiers quoted with ' quotes instead of `

For the quote, I just typed the query on the keyboard.
Now, here's the paste directly from the binary log:
DELETE FROM `datap`.`de_real_time`

Please try version 5.2.45. Thanks.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".