]
Igor Regis da Silva Simões commented on HBX-548:
------------------------------------------------
I tested the DB2OS390MetaDataDialect and it works with DB2 9 on OS/390.
Could someone commit this new Dialect into SVN repository? As the hibernate tools
documentation at chapter 5 item 5.4 "Custom Database Metadata" the users are
invited to contribute with new Dialects. This new dialect is necessary because
JDBCMetaDataDialect don't process correctly the DB2 metadata, even with DECSTAT=YES,
because the columns names are not like the ones that are expected.
FAQ. DESCSTAT=YES required for DB2 on z/OS
------------------------------------------
Key: HBX-548
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HBX-548
Project: Hibernate Tools
Issue Type: Improvement
Components: reverse-engineer
Affects Versions: 2.1, 3.0alpha, 3.0alpha2, 3.0alpha3, 3.0alpha4, 3.0beta1, 3.0beta2,
3.0beta3, 3.1alpha5, 3.1beta1, 3.1beta2, 3.1beta3, 3.1beta4, 3.2LATER
Environment: DB2 os/390
Reporter: Matthew Aston
Priority: Trivial
Attachments: DB2OS390MetaDataDialect.java
When using Hibernate Tools with DB2 on z/OS (Mainframe), be aware that you need to set
DESCSTAT=YES and rebind the packages in order for getMetaData().getColumns etc to work.
NB. setting this will slightly increase your package size on DB2.
The reason for this is that within the Hibernate Tools class,
org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect, calls are made with the column name,
e.g. rs.getString("INDEX_NAME"). DB2 will not provide the column names without
the DESCSTAT setting. i.e. positioning works e.g. rs.getString(3). DB2 calls a packages
SYSIBM.SQLTABLES, SYSIBM.SQLCOLUMNS etc.
Alternately you can implement your own org.hibernate.cfg.reveng.dialect.MetaDataDialect
that works around this limitation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: