schema-selection is not applying pattern matching on oracle database -------------------------------------------------------------------- Key: HBX-866 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-866 Project: Hibernate Tools Type: Bug Components: reverse-engineer Versions: 3.2beta8, 3.2beta9 Environment: Hibernate 3.2.1, Oracle 10g (10.1.0.3.0) Reporter: Nicolas Romantzoff In the reverse-engineering file, when asking a pattern-matching schema and/or table in <schema-selection> (match-schema or match-table) it is ignored. Looks like table discovery is performing a raw '=' test. This behavior is seen with both OracleMetaDataDialect and JDBCMetaDataDialect Easy reproducible steps: - Create 1 single table "ABC" in an empty schema "TEST" Working schema-selections: <schema-selection/> => (select ... from all_tables;) <schema-selection match-schema="TEST"/> => (select ... from all_tables where owner='TEST';) <schema-selection match-table="ABC"/> => (select ... from all_tables where table_name='ABC';) <schema-selection match-schema="TEST" match-table="ABC"/> => (select ... from all_tables where owner='TEST' and table_name='ABC';) Not-Working schema-selections: <schema-selection match-schema=".*"/> => (select ... from all_tables where owner='.*'; !!!!!! ) <schema-selection match-table=".*"/> => (select ... from all_tables where table_name='.*'; !!!!!! ) <schema-selection match-schema="TEST" match-table=".*"/> => (select ... from all_tables where owner='TEST' and table_name='.*'; !!!!!! ) -- 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