Fix for HHH-2208 rebuilds Settings for each table mapping --------------------------------------------------------- Key: HHH-2252 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2252 Project: Hibernate3 Type: Improvement Components: core Versions: 3.2.0.ga Environment: Hibernate 2.1 beta 4, Oracle 8i Reporter: Alex Burgel Fix For: 3.2.1 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira