You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@geode.apache.org by "Dakta (GitHub)" <gi...@apache.org> on 2019/02/20 19:09:18 UTC

[GitHub] [geode] Dakta commented on issue #3207: GEODE-6431: Change default catalog and schema to null

> Add a test (maybe to TableMetaDataManagerIntegrationTest) that defines the same table name in two different schemas. In that case if the defaults of "null" are used then both tables should be found and that should be an error

It looks like the behavior depends on the underlying database provider. Since different database systems have different treatment of "catalog", "schema", and "database", it may not even be possible to connect to a database server without specifying a valid catalog/schema combination.

For example, MySQL treats catalog/schema/database as synonymous terms, but JDBC will only connect to a server if a database is provided in the URI, or if a catalog is provided in the `jdbc-mapping`. In either case, it is not possible to create a database connection to a MySQL server that is not already limited/constrained to a single database. So a MySQL connection will never return results from more than one catalog/schema/database.

[ Full content available at: https://github.com/apache/geode/pull/3207 ]
This message was relayed via gitbox.apache.org for notifications@geode.apache.org