MySQL Bugs: #62893: table data is not editable because there is no primary key defined for the table

Bug #62893	table data is not editable because there is no primary key defined for the table
Submitted:	23 Oct 2011 13:39	Modified:	2 Aug 2012 4:22
Reporter:	Danny Zhong	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S1 (Critical)
Version:	5.2.41	OS:	Linux (Ubuntu 12.04)
Assigned to:		CPU Architecture:	Any
Tags:	edit table data primary key

Description:
Can't edit table data even if the table has a primary key.

table:
CREATE TABLE `testtable` (
  `id` int(11) NOT NULL,
  `usr` varchar(256) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8

MySql Workbench built with the patch http://bugs.mysql.com/file.php?id=17639.

How to repeat:
1. click the table 'testtable' using mouse right button
2. select the menu item "Edit Table Data" from the popup menu
3. check the sql editor output:
   Action: select * from `test`.`testtable` LIMIT 0, 1000
   Message: Error: `test`.`testtable`: table data is not editable because there is no primary key defined for the table

the operation result

Attachment: Screenshot at 2011-10-23 21:41:29.png (image/png, text), 134.52 KiB.

What exact server version, 5.x.y, are you working with?

The MySql server version is 5.1.42 .

mysqld --version:
/opt/mysql-5.1.41/libexec/mysqld  Ver 5.1.41-log for unknown-linux-gnu on x86_64 (Source distribution)

configuration:
CFLAGS="-O3" CXX=gcc CXXFLAGS="-O3 -felide-constructors \
-fno-exceptions -fno-rtti" \
./configure --prefix=/opt/mysql-5.1.45 --with-charset=utf8 --with-extra-charsets=all --enable-assembler \
--with-plugins=all \
--enable-thread-safe-client

BTW: the function "Alter Table" works fine.

Alter Table

Attachment: Screenshot at 2011-10-24 12:30:17.png (image/png, text), 77.42 KiB.

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

I tested again using the newer version 5.2.36, the bug still exist.

Error ouput:

0	21:45:39	SELECT * FROM test.testtable LIMIT 0, 1000	Error: `test`.`testtable`: table data is not editable because there is no primary key defined for the table

I run the workbench with --log-level option which assigned with 'debug3', but where can I get the debug logging? I want to upload the debug logging.

I have same bug/problem... In previous version this bug doesn't exist...

Danny, see Help -> System Info, which prints the location of the data folder. In this folder is a logs subfolder.

Actually, there is even a "Locate Log File" menu entry in the Help menu.

Thanks everybody. I launched the workbench using "mysql-workbench --log-level=debug3" and got the log file.

Attachment: wb.log (text/x-log), 1.92 KiB.

The bug is also present in the Windows version from MySQL Workbench. (Tested on Windows XP)

Not repeatable on Windows 7 64-bits.

Hello Danny.
A new WB version is out(5.2.37), would you mind give it a try and let us know the outcome?
http://dev.mysql.com/downloads/workbench/
Thanks.

the bug still exist in version 5.2.37.

Test Result:
0	10:38:49	SELECT * FROM test.testtable LIMIT 0, 1000	Error: `test`.`testtable`: table data is not editable because there is no primary key defined for the table

logging(wb.log):
10:38:14 [   Info][      WBContext]: WbContext::init
10:38:21 [   Info][      WBContext]: System info:
 	MySQL Workbench CE for Linux/Unix version 5.2.37  revision 8576
	Configuration Directory: /home/hdzhong/.mysql/workbench
	Data Directory: /usr/share/mysql-workbench
	Cairo Version: 1.10.2
	Rendering Mode: OpenGL is not available on this system, so Native is used for rendering.
	OS: Linux 3.0.0-14-generic
	CPU: 2x Intel(R) Core(TM)2 Duo CPU     P8400  @ 2.26GHz 2267.000 MHz, 3.8 GB RAM
10:38:21 [   Info][         (null)]: query.save_edits built-in command is being overwritten
10:38:21 [   Info][         (null)]: query.discard_edits built-in command is being overwritten
10:38:41 [   Info][     SSH tunnel]: Starting tunnel

I am also experiencing this bug in 5.2.37.  In my case, the table I'm querying has a composite primary key.  Interestingly, any select statement that includes al of the columns in the primary key (including a select *) gets this error, but a query that excludes columns in the key succeeds.

Is there an ETA on a fix?

Is testtable exactly the table that is not working for you? Does the error happen only with specific
tables or any tables?

I see this all the time with 5.2.37 on Windows 7 64 bit.  Is there a workaround to disable editing so I can at least select from a table?

I can select if I specify columns, but select * doesn't work.

BTW, .37 hangs and crashes a couple times a day.  I'd open a ticket, but I have not idea how to reproduce the behavior.  It just happens from time to time.

You can workaround by specifying a function in the column list, like
SELECT *, concat('','') FROM table

Alfredo: Thanks so much for the workaround! This bug was driving me nuts (on a table I had no permission or intention of ever editing).

Erik: Yes 5.2.37 really SUCKS also on my WinXP Pro 32b, so I doubt your Win7 64b is the problem. The many information tabs are now so bulky & static - worse than the version a few months ago and much worse than the (SPEEDY!) Query Browser from 3+ years ago...

On a positive note I just read the release notes to unreleased 5.2.38:
( http://dev.mysql.com/doc/workbench/en/wb-news-5-2-38.html )
and the devs knocked off a truly annoying long time bug where grouping WITH ROLLUP would give both an editor & execution error though it is valid MySQL code. Perhaps our current Bug #62893 will be added next...

As of right now, I have to add some silly function to my select statement for every select * query I use!  This is a most efficiency killing bug for me!  Nearly enough to make me quit using this product.

Just wanted to note that I'm experiencing the same issue with a Windows 7 x64 installation of MySQL Workbench.

The work-around works like a charm - though a bit annoying.

- Stan

I can reproduce this problem on 5.2.37 on Mac OS X 10.7.3. Can also confirm the workaround from Alfredo works.

I used Alfredo's workaround but found one with less typing. :)

SELECT *,'' FROM <tablename>

Hello Danny.
This bug has been fixed in WB 5.2.38.
Can you please give a try and confirm this?
Thanks.

Fixed! Thanks!

Looks to be fixed for me as well. Thanks!

The bug still exist.

Something enhance: the table object info is display(I will upload a screenshot).

WB log:
14:48:51 [INF][      WBContext]: WbContext::init
14:48:52 [INF][      WBContext]: System info:
 	MySQL Workbench CE for Linux/Unix version 5.2.38  revision 8753
	Configuration Directory: /home/hdzhong/.mysql/workbench
	Data Directory: /usr/share/mysql-workbench
	Cairo Version: 1.10.2
	OS: Linux 3.0.0-16-generic
	CPU: 2x Intel(R) Core(TM)2 Duo CPU     P8400  @ 2.26GHz 2267.000 MHz, 3.8 GB RAM
14:48:54 [INF][     SSH tunnel]: Starting tunnel

Bug and enhance

Attachment: MySQL Workbench_005.png (image/png, text), 105.83 KiB.

Updating to 5.2.38 appears to have fixed it for me on Windows Vista SP2.

Please try version 5.2.39. 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".

Bug fixed.

Downloaded the DEB install package from http://dev.mysql.com/downloads/workbench/5.2.html.