Bug #43714 | useInformationSchema with DatabaseMetaData.getExportedKeys() throws exception | ||
---|---|---|---|
Submitted: | 17 Mar 2009 20:34 | Modified: | 23 Jun 2009 13:02 |
Reporter: | Jess Balint | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / J | Severity: | S3 (Non-critical) |
Version: | 5.1 | OS: | Any |
Assigned to: | Jess Balint | CPU Architecture: | Any |
[17 Mar 2009 20:34]
Jess Balint
[17 Mar 2009 21:16]
Jess Balint
fix + test
Attachment: bug43714.diff (text/x-diff), 1.91 KiB.
[17 Mar 2009 21:16]
Jess Balint
Only against MySQL 5.1
[2 Jun 2009 5:59]
Jess Balint
Pushed for release in 5.1.8
[23 Jun 2009 13:02]
Tony Bedford
An entry was added to the 5.1.8 changelog: Using useInformationSchema with DatabaseMetaData.getExportedKeys() generated the following exception: com.mysql.jdbc.exceptions.MySQLIntegrityConstraintViolationException: Column 'REFERENCED_TABLE_NAME' in where clause is ambiguous ... at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1772) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1923) at com.mysql.jdbc.DatabaseMetaDataUsingInfoSchema.executeMetadataQuery( DatabaseMetaDataUsingInfoSchema.java:50) at com.mysql.jdbc.DatabaseMetaDataUsingInfoSchema.getExportedKeys( DatabaseMetaDataUsingInfoSchema.java:603)