Table schema use in DatabaseMetadata

Description

When using SchemaUpdate, the DatabaseMetaData.getTableMetadata() looks for a table with the correct table name in any database schema and it take the first one it found. This behavior is uncorrect if I have a table existing in different schemas.

The correct behavior would be to first look in the schema with the login name and after in any schema.

user1.article
user2.article

I connected whith user2, DatabaseMetaData should first look for user2.article, then if not found to %.article.

Adrien

Environment

Hibernate 2.1 beta 4, Oracle 8i

Status

Assignee

Unassigned

Reporter

Adrien

Fix versions

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Components

Affects versions

Priority

Major
Configure