Bug #9955 edit button fails to light up on "sufficient identifying" query
Submitted: 16 Apr 2005 18:39 Modified: 26 Apr 2005 19:16
Reporter: avi weiss Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Query Browser Severity:S3 (Non-critical)
Version:1.1.6 OS:Windows (win XP)
Assigned to: CPU Architecture:Any

[16 Apr 2005 18:39] avi weiss
Description:
I have a table called lookup_team_type, which I imported from access via ODBC. I generated a resultset from the following query:

SELECT * FROM `lookup_team_type` l

however, the result set fails to have the edit button highlight. I know of no other way to make the resultset "sufficiently indentified" (as per the docs) to get the button to highlight. 

This is not the only table this happens on. It seems that the edit button fails to highlight on other tables as well, though I can find nothing common amoung the tables to understand why this would happen, as other tables I have imported from access have the "edit" button highlighted. please let me know if you find anything

How to repeat:
import table from access, perform select.
[26 Apr 2005 19:16] Michael G. Zinner
The table needs to have a primary key or you cannot edit it.
[26 Apr 2005 19:37] avi weiss
Thanks for that. Needing a primary key prior to being able to edit doesnt seem like a logical pre-requiste to me, nor is it spelled out in the online document related to the "edit" button. 

It might be helpful to either remove that requirement, or have edit highlighted, but when clicked, popup an alert indicating that a primary key is required.

thanks

-avi