MySQL Bugs: #38537: The command "DELETE...FROM...WHERE..." makes all data deleted.

Bug #38537	The command "DELETE...FROM...WHERE..." makes all data deleted.
Submitted:	4 Aug 2008 13:13	Modified:	4 Sep 2008 15:53
Reporter:	andy hannibal	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.0.5 1b community	OS:	Windows (Wins XP SP2)
Assigned to:		CPU Architecture:	Any
Tags:	all data deleted, delete, where

Description:
Suppose i have table structure like this
Create Table myTable
(
   ID INT,
   DATA1 NVARCHAR(20), 
   DATA2 NVARCHAR(20),   
); 
*ID is not unique.

I need to delete data where ID = 8. Thus, i've executed this command (with MySQL Query Browser)...
"DELETE FROM myTable WHERE ID=8;"
Instead of deletion of data where ID=8, All data in myTable was deleted.!!!   

How to repeat:
Just try "DELETE FROM ... WHERE ID=some value;"

I've tested by some cases.

1. With PHPMyAdmin, I've executed "DELETE FROM MyTable WHERE ID=8;" and it works properly.Doing the same thing in MySQL Query Browser,it makes all data in  MyTable deleted.

2. With MySQL Administrator, i make stored procedure "sp_TestDelete(IN @id)" which have "DELETE FROM MyTable WHERE ID=@id;" command within it.
   After that,test in both PhpMyAdmin and MySql Query Browser, I've executed "CALL sp_TestDelete(8);" and the both makes all data in MyTable deleted.

Hope these may help.

Thank you for a problem report. Please, upload a complete test case (mysqldump results for the problematic table, if possible). What version of Query Browser do you use?

I'm using MySQL Query Browser version 1.2.12

I've just fixed it although i don't know why.
I just try changing storage engine from MyISAM to InnoDB and change it back to MyISAM again and it works until now.

It is the issue resolved? otherwise please provide the complete test case as requested. 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".