Bug #39563 | SQLPrimaryKeys returns clobbered resultset rows for some tables | ||
---|---|---|---|
Submitted: | 20 Sep 2008 19:39 | Modified: | 25 Feb 2010 15:29 |
Reporter: | Farid Zidan (Candidate Quality Contributor) | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | Connector / ODBC | Severity: | S1 (Critical) |
Version: | 5.1.5 | OS: | Windows (XP SP3) |
Assigned to: | CPU Architecture: | Any | |
Tags: | clobbered resultset data, qc, SQLPrimaryKeys |
[20 Sep 2008 19:39]
Farid Zidan
[10 Oct 2008 0:36]
Jess Balint
Farid, Please include the output of "SHOW CREATE TABLE" for the problematic tables.
[10 Oct 2008 2:55]
Farid Zidan
Hello here is ddl for table that shows this issue. I also tried to view primary key info in WinSQL and do not get primary key name ( even if named the PK in the create DDL ). CREATE TABLE `test_pk` ( `cpt4` char(5) NOT NULL default '', `cpt4group` char(5) NOT NULL default '', `section_type` char(1) default NULL, `runid` int(11) default NULL, `rec_type` char(1) default 'X', `cpt4_rec_type` char(6) NOT NULL, `cpt4_desc` varchar(50) default NULL, `cpt4group_desc` varchar(50) default NULL, PRIMARY KEY (`cpt4_rec_type`), UNIQUE KEY `AK_Key_2` (`rec_type`,`cpt4`), UNIQUE KEY `x1_cpt4_cpt4group` (`cpt4`,`cpt4group`,`section_type`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
[10 Oct 2008 2:57]
Farid Zidan
Viewing PK name in WinSQL for the test table
Attachment: TestPK.jpg (image/jpeg, text), 137.64 KiB.
[25 Feb 2010 15:26]
Lawrenty Novitsky
I think this bug is a duplicate of the Bug#36441. If nobody minds, i will close it.
[25 Feb 2010 15:29]
Lawrenty Novitsky
setting as "duplicate" so far