The following comment has been added to this issue:
Author: Gavin King
Created: Tue, 9 Dec 2003 4:51 PM
Body:
Please resubmit this as a patch, so that we can see exactly which lines changed.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-534
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-534
Summary: Table schema use in DatabaseMetadata
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1 beta 4
Assignee:
Reporter: xfgdf
Created: Tue, 9 Dec 2003 10:55 AM
Updated: Tue, 9 Dec 2003 4:51 PM
Environment: Hibernate 2.1 beta 4, Oracle 8i
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
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
