btw...You can explicitly replace the auto used OracleMetaDataDialect with the generic JDBCMetaDataDialect detailed as follows:
Quote:
The OracleMetaDataDialect is now enabled by default for Oracle related dialects. The Oracle specific handling have also been improved greatly so now it is much faster than normal JDBC MetaData API.
If you experience issues with the OracleMetaDataDialect you can fall back to using the JDBC MetaData API by adding the following property to your hibernate.properties or hibernate.cfg.xml:
hibernatetool.metadatadialect=org.hibernate.cfg.rveng.dialect.JDBCMetaDataDialect
However, I encountered the following exception:
at org.hibernate.tool.ant.HibernateToolTask.execute(HibernateToolTask.ja
va:186)
... 16 more
Caused by: java.sql.SQLException: Invalid column name
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:169)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:211)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:274)
at oracle.jdbc.driver.OracleStatement.get_column_index(OracleStatement.j
ava:4541)
at oracle.jdbc.driver.OracleResultSetImpl.findColumn(OracleResultSetImpl
.java:666)
at oracle.jdbc.driver.OracleResultSet.getString(OracleResultSet.java:137
4)
at org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect$1.convertRow(JDB
CMetaDataDialect.java:37)
at org.hibernate.cfg.reveng.dialect.ResultSetIterator.next(ResultSetIter
ator.java:59)
... 30 more