Bug #81369 Shouldnt DatabaseMetaData.supportsSchemasInTableDefinitions return 'true' instea
Submitted: 10 May 2016 17:26 Modified: 11 May 2016 11:54
Reporter: Victor Hujvamaneregistracija Email Updates:
Status: Not a Bug Impact on me:
Category:Connector / J Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any
Tags: schemas

[10 May 2016 17:26] Victor Hujvamaneregistracija
DatabaseMetaData.supportsSchemasInTableDefinitions and it ancestors return 'false', but actually schema name can be used in mysql table name.

Why this can be a problem:
Hibernate 5 now automatically determine - is JDBC supports schemas, and if dont, then omit @Table(schema=?) property.

How to repeat:
Create simple connection with JDBC4DatabaseMetaData as meta data to mysql5 DB, for example.
[11 May 2016 11:54] Chiranjeevi Battula
Hello  Victor,

Thank you for the bug report.
MySQL doesn't support schemas and it will supports catalogs.
Please see in the forums Mark explains that because of legacy reasons the MySQL 'database' concept is mapped into JDBC 'catalog' concept.