[CONJ-471] PK_NAME returned by DatabaseMetadata.getPrimaryKeys() should not be null Created: 2017-05-15 Updated: 2017-05-31 Resolved: 2017-05-31 |
|
| Status: | Closed |
| Project: | MariaDB Connector/J |
| Component/s: | JDBC 4.2 compatibility, metadata |
| Affects Version/s: | 1.5.8, 1.5.9 |
| Fix Version/s: | 1.6.1, 2.0.2 |
| Type: | Bug | Priority: | Major |
| Reporter: | QING ZHU | Assignee: | Diego Dupin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
For MariaDB, driver version ="1.5.8" and "1.5.9", |
||
| Description |
|
PK_NAME returned in DatabaseMetadata.getPrimaryKeys() should not be null For MariaDB, driver version ="1.5.8" and "1.5.9", DatabaseMetadata.getPrimaryKeys() returns PK_NAME as null, which is incorrect. https://mariadb.com/kb/en/mariadb/create-table/, please note that constraint names cannot be defined by the user. This bug breaks IBM Cognos' mutual customers to generate relationship based on primary keys and foreign keys. |
| Comments |
| Comment by Diego Dupin [ 2017-05-16 ] | |||||||||||||||
|
Hi zhuq. | |||||||||||||||
| Comment by QING ZHU [ 2017-05-31 ] | |||||||||||||||
|
Hi diego dupin, I see this issue has been fixed in JDBC version 1.6.1 and 2.0.2. Is that correct? If so, where to download the fixed JDBC drivers? Thanks. | |||||||||||||||
| Comment by Diego Dupin [ 2017-05-31 ] | |||||||||||||||
|
They will be released in a few days, Snapshot are available though :
|