MySQL Bugs: #24104: Cannot edit a table that doesn't have a primary key

Bug #24104	Cannot edit a table that doesn't have a primary key
Submitted:	8 Nov 2006 21:08	Modified:	8 Jan 2007 9:48
Reporter:	Sean Downey	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.24	OS:	Windows (XP)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
You cannot edit a table that doesn't have a primary key, this is annoying. After thinking it over its probably due to the fact taht there needs to be a unique field in order to make sure you save the right data. There should at least be a warning or something to state so.

How to repeat:
create a table with out a primary key and try to edit it

Suggested fix:
try and find other unique fields that can allow this

Thank you for the bug report.

This should be marked as OS independent. This is internal behaviour and I think it must be really resolved.

SQLyog uses some techniques to investigate and decide to use in QB...

This behavior is by design and is technically necessary. In tools like QB where you have more than one record at the same time in the display, of which you cannot predict the order, you have to find a unique way to identify a particular record when updating it. So it is necessary to have a primary key, which provides that info.