Bug #89133 | Contribution: Update DatabaseMetaData.java | ||
---|---|---|---|
Submitted: | 8 Jan 2018 14:51 | Modified: | 24 Jun 2019 20:01 |
Reporter: | OCA Admin (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / J | Severity: | S3 (Non-critical) |
Version: | OS: | Any | |
Assigned to: | CPU Architecture: | Any |
[8 Jan 2018 14:51]
OCA Admin
[8 Jan 2018 14:51]
OCA Admin
Contribution submitted via Github - Update DatabaseMetaData.java (*) Contribution by Harald Aamot (Github aamotharald, mysql-connector-j/pull/26#issuecomment-355803703): I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.
Contribution: git_patch_158346477.txt (text/plain), 1.38 KiB.
[8 Jan 2018 16:21]
MySQL Verification Team
Thank you for the contribution.
[24 Jun 2019 20:01]
Daniel So
Posted by developer: Added the following entry to the Connector/J 8.0.17 changelog: "A new connection property, databaseTerm, sets which of the two terms is used in an application to refer to a database. The property takes one of the two values CATALOG or SCHEMA and uses it to determine which Connection methods can be used to set/get the current database, which arguments can be used within the various DatabaseMetaData methods to filter results, and which fields in the ResultSet returned by DatabaseMetaData methods contain the database identification information. See the entry for databaseTerm in Configuration Properties for details. Also, the connection property nullCatalogMeansCurrent has been renamed to nullDatabaseMeansCurrent. The old name remains an alias for the connection property. Thanks to Harald Aamot for contributing to the patch."