Bug #44867 DEFERRABILITY column in resultsets for database metadata has wrong data type

Submitted:	14 May 2009 9:40	Modified:	26 May 2009 10:52
Reporter:	Vivekanand Bachche	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / J	Severity:	S3 (Non-critical)
Version:	5.1.7	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
The column in database metadata resultsets which named as DEFERRABILITY is expected to be of type 'short' (i.e. small int). MySQL driver returns it as 'integer'.

Following are the metadata apis which return this column-
1. getImportedKeys
2. getExportedKeys
3. getCrossReferrence

This can give critical problems with BI tools which perform strict checking before retreiving metadata information.

How to repeat:
For each API mentioned in the description, check the type of column named "DEFERRABILITY" in the returned result set.

Logical cause and fix looks to be simialar for following bugs-
44791
44862
44863
44865
44867
44868
44869

Please exclude 44791 from the list in my previous comment.

Thank you for the problem report.

Fixed, see http://bazaar.launchpad.net/~mark-mysql/connectorj/5.1/revision/793

An entry has been added to the 5.1.8 changelog:

The DEFERRABILITY column in database metadata result sets was expected to be of type SHORT. However, Connector/J returned it as INTEGER.

This affected the following methods: getImportedKeys(), getExportedKeys(), getCrossReference().

Page generated in 0.052 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.