[ http://opensource.atlassian.com/projects/hibernate/browse/HB-534?page=comments#action_23768 ]
Adrien commented on HB-534:
---------------------------
Gavin set this issue as Duplicate, but without saying the duplicate issue.
As far as I know, this issue is still not corrected in version 3.1.3. The patch is still not apply.
I just got the problem again recently, looking in the tracker for existing issue, and found my own issue submmited two years ago.
I am not sure I should submit this again and again. If you feel like it, go ahead.
Adrien
> Table schema use in DatabaseMetadata
> ------------------------------------
>
> Key: HB-534
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HB-534
> Project: Hibernate2
> Type: Bug
> Components: core
> Versions: 2.1 beta 4
> Environment: Hibernate 2.1 beta 4, Oracle 8i
> Reporter: Adrien
> Attachments: DatabaseMetadata.java, HB-534_patch.txt, TableMetadata.java
>
>
> 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
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
