MySQL Bugs: #40800: Editing result sets does not automatically create a primary key

Bug #40800	Editing result sets does not automatically create a primary key
Submitted:	17 Nov 2008 19:48	Modified:	15 Dec 2009 15:01
Reporter:	Björn Voigt (OCA)	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Query Browser: Docs	Severity:	S3 (Non-critical)
Version:	1.2.14	OS:	Any
Assigned to:	Tony Bedford	CPU Architecture:	Any
Tags:	CHECKED

Description:
The "MySQL Query Browser Quick Start Guide" says in section "Editing Resultsets":

"For a resultset to be editable, the following conditions must be met: 
[...]
this table must contain a Primary Key column, although not necessarily in the query. If the query does not contain the primary key, it will be automatically added before the MySQL Query Browser sends the query to the MySQL server, but will display only the columns you requested;"

This does not seem to by true. MySQL query browser always hides the button "Start editing" if the queried table does not have a primary key. I could not found an automatically adding of primary keys in the Windows and Linux version of MySQL query browser.

How to repeat:
Read the "MySQL Query Browser Quick Start Guide" and test the functionality with a table without a primary key.

Suggested fix:
Fix the documentation

corrected category

I understand reading the mentioned text, that the query can't includes the primary  
key column but the table must have a primary key column. But anyway the text could be more clear.

It's not possible to edit table data within Query Browser, if the table does not have a primary key. It is likely that the Query Browser refuses to edit tables without primary keys, because it may not find the correct rows for the editing changes on the server.

But the documentation (see this report) says, that a missing primary key is created automatically. This is not the case and so the documentation is incorrect.

Verified that Quck Start documentation is confusing here also by newest version.

Active development of MySQL Query Browser has ended, so there's no point in fixing the docs for that product.