Bug #26155 Tables are uneditable
Submitted: 7 Feb 2007 17:41 Modified: 21 Feb 2007 0:32
Reporter: Michael Reeves Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Query Browser Severity:S2 (Serious)
Version:5.0r9, 1.2.9rc OS:Linux (RHEL 4)
Assigned to: Alfredo Kojima CPU Architecture:Any
Tags: gui tools, query browser

[7 Feb 2007 17:41] Michael Reeves
Description:
Using the RC version of QB, I'm no longer able to edit table data.

After selecting a table with data in it, the Start Editing button is not active.  In fact, it's grayed out.

How to repeat:
Open Query Browser

Double click a table in your database containing data

Observe that the Start Editing button is not available.

Suggested fix:
Hook it up.
[7 Feb 2007 22:17] MySQL Verification Team
Thank you for the bug report. Could you please provide the create
definition of the table you want to edit and the select statement
used to create the result set?. Thanks in advance.
[7 Feb 2007 22:36] Michael Reeves
CREATE TABLE 'COM_tbl_Preserved_Data' (
  'DataName' varchar(32) collate utf8_unicode_ci NOT NULL default 'Direction',
  'DataItem' varchar(50) collate utf8_unicode_ci NOT NULL default 'Y',
  KEY 'DataName' ('DataName')
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

INSERT INTO COM_tbl_Preserved_Data VALUES ('Num_Of_Rcpts','2'),('Data_Rate','350'),('Terminal_Name','Station Z'),('Modem_Operation','No Activity');

SELECT * FROM COM_tbl_Preserved_Data;

This pretty much is behaving the same way for every single table I have. 
SELECT * FROM information_schema.COLUMNS;
SELECT * FROM mysql.user;

etc, etc.
[8 Feb 2007 2:14] MySQL Verification Team
Thank you for the feedback. Notice by design QB to enable the edit button
needs that the table has a PK, so please try with the below table definition:

mysql> CREATE TABLE `COM_tbl_Preserved_Data` (
    ->   `DataName` varchar(32) collate utf8_unicode_ci NOT NULL default "Direction",
    ->   `DataItem` varchar(50) collate utf8_unicode_ci NOT NULL default "Y",
    ->   PRIMARY KEY `DataName` (`DataName`)
    -> ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
Query OK, 0 rows affected (0.03 sec)

Thanks in advance.
[8 Feb 2007 14:43] Michael Reeves
You mean like for instance mysql.user?  That table is not editable even though I'm logged in as root.

I've added a primary key to COM_tbl_Preserved_Data, and it is still not editable.
[8 Feb 2007 19:14] Sveta Smirnova
Thank you for the report.

I can edit tables with primary key in Query Browser on Ubuntu Linux.
[8 Feb 2007 19:56] Michael Reeves
Is it possible that this is only a RedHat issue?  I'm running 8 workstations, and every single one of them has this problem.  We're running RHEL 4 update 2.
[8 Feb 2007 20:02] Sveta Smirnova
Could you please provide screenshot with error and confirm that new table definition is same as in Miguel's post?
[8 Feb 2007 20:41] Michael Reeves
Sorry, I missed the second part of your request.  SHOW CREATE gives

CREATE TABLE `COM_tbl_Preserved_Data` (
  `DataName` varchar(32) collate utf8_unicode_ci NOT NULL default 'Direction',
  `DataItem` varchar(50) collate utf8_unicode_ci default 'Y',
  PRIMARY KEY (`DataName`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci

I would ask if this was an InnoDB issue, but since it's choking even in DB mysql, that doesn't seem right.
[12 Feb 2007 12:54] Wesley Hampton
Hey guys, we were kind of discussing this issue in a similar bug introduced in rc9.  The editing of table/query data came up about halfway down.

http://bugs.mysql.com/bug.php?id=25775

So to add another voice to this bug...I also cannot edit the results of queries that I used to be able to.  I use SuSE 10.2 and have QB 1.2.9rc installed from RPM.  Editing the results of queries worked just fine in rc8.

The addition of PK to queries does not seem to make any difference.
[21 Feb 2007 0:32] Alfredo Kojima
Hi

I can confirm this is a duplicate of a bug introduced in RC9.
The cause of the bug has been tracked and the next release will already
have this problem fixed.