Currently, when a @Table does not have the catalog or schema defined, Validator will look for that table in all visible catalogs/schemas. If it is found, then Validator does not throw an exception.

Instead, Validator should only look in the default schema and/or catalog and throw an exception if it is not found.

The difficulty is that Hibernate does not understand which databases use catalog, which use schema and which use both. It needs to know this information in order for Validator to look in the right place when a @Table has a default schema or catalog.

A new API, SchemaSupport, is intended to resolve this complication.