Bug #129 Unwanted mass update/delete via result grid if table primary key is double(32,0
Submitted: 6 Mar 2003 18:52 Modified: 6 Mar 2003 18:54
Reporter: Alexander Keremidarski Email Updates:
Status: Closed Impact on me:
None 
Category:MySQLCC Severity:S3 (Non-critical)
Version:0.8.10-beta OS:
Assigned to: Bugs System CPU Architecture:Any

[6 Mar 2003 18:53] Alexander Keremidarski
Thank you for your bug report. This issue has been fixed in the latest
development tree for that product. You can find more information about
accessing our development trees at 
    http://www.mysql.com/doc/en/Installing_source_tree.html
[6 Mar 2003 18:54] Alexander Keremidarski
How-To-Repeat:

1. Copy and execute following sql-script in mysqlcc SQL window of some test db:

############################
DROP TABLE IF EXISTS suser;
CREATE TABLE suser (
  uid double(32,0) NOT NULL auto_increment,
  username varchar(100) NOT NULL default '',
  password varchar(64) default NULL,
  PRIMARY KEY  (uid),
  KEY username (username)
) TYPE=MyISAM;
INSERT INTO suser VALUES (155,'abc','abc');
INSERT INTO suser VALUES (156,'def','def');
INSERT INTO suser VALUES (157,'xyz','xyz');

SELECT * FROM suser WHERE username = 'abc';

# update password in grid from abc to 123 --> 3 rows affected! (in fact all rows are affected)

# select single entry and press delete record button in toolbar --> 3 rows deleted! (in fact all rows are deleted)
############################

2. update password in grid from abc to 123 --> 3 rows affected! (in fact all rows are affected)

3. select single entry and press delete record button in toolbar --> 3 rows deleted! (in fact all rows are deleted)

4. re-run script with primary key column uid of type int and problem does not occur.