Bug #8812 Inverted NON_UNIQUE column in DatabaseMetaData.getIndexInfo
Submitted: 25 Feb 2005 16:58 Modified: 3 Mar 2005 22:55
Reporter: Domagoj Cosic Email Updates:
Status: Closed Impact on me:
Category:Connector / J Severity:S2 (Serious)
Version:3.1.6 3.1.7 OS:Any (All)
Assigned to: Mark Matthews CPU Architecture:Any

[25 Feb 2005 16:58] Domagoj Cosic
Since Release 3.1.6 the column NON_UNIQUE returned by DatabaseMetaData.getIndexInfo is inverted, it returns TRUE insted of FALSE on an unique index!

How to repeat:
Create a simple table with one column which is primary key. DatabaseMetaData.getIndexInfo should return FALSE for a primary key index because it must be unique.

Suggested fix:
Until 3.1.5 gamma it worked correctly, just return it to that state...
[3 Mar 2005 22:55] Mark Matthews
Thanks for the bug report.

Fixed for 3.1.8, 3.0.17 and 3.2.1. You can grab a nightly snapshot of 3.1.8 with this fix applied from http://downloads.mysql.com/snapshots.php after 00:00 GMT.