MySQL Bugs: #25862: Edit data button initially not enabled, depends on format of select statement

Bug #25862	Edit data button initially not enabled, depends on format of select statement
Submitted:	26 Jan 2007 10:41	Modified:	1 Feb 2007 12:33
Reporter:	Heinz Schweitzer (Gold Quality Contributor)	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.2.9 rc	OS:	Windows (XP)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
Edit data button initially not enabled, depends on format of select statement

This is related to bug #25837

MySQL-Server-Information
--------------------------------------------------------------------------------
Mit MySQL-Serverinstanz verbunden
  Benutzername:            root
  Hostname:                localhost
  Port:                    3306
--------------------------------------------------------------------------------
Serverinformation
  MySQL-Version:           MySQL 5.0.24a-community-nt via TCP/IP
  Netzwerkname:            localhost
  IP:                      127.0.0.1
--------------------------------------------------------------------------------
Clientinformation
  Version:                 MySQL Client Version 5.1.11
  Netzwerkname:            xxxxxxxxx
  IP:                      xxxxxxxxx
  Betriebssystem:          Windows XP
  Hardware:                Intel(R) Pentium(R) M processor 1600MHz, 512 MB RAM

How to repeat:
Selected a table from a schema in MA then say
edit data like in screen shot s4

Query Browser starts up with records selected from
that table but the edit data button on the bottom is
disabled like in screen shot s2. Look also at the
format of the select string it refers to 'database'.'table'

Now change the format of the select string by deleting the
'database' part, place cursor at end of string and rerun the
select statement again.

Now the edit data button on the bottom is
enabled like in screen shot s3.

????

s4

Attachment: shot_4.jpg (image/jpeg, text), 87.29 KiB.

s2

Attachment: shot_2.jpg (image/jpeg, text), 81.73 KiB.

s3

Attachment: shot_3.jpg (image/jpeg, text), 82.60 KiB.

Thank you for a bug report. Verified just as described. Looks like in case of `db`.`tab` reference used QB is not checking for primary key properly.

Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Duplicate of Bug #25778