[hibernate-issues] [Hibernate-JIRA] Updated: (HBX-965) conditionally exclude catalog in H2MetaDataDialect
[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-965?page=co...
]
Dan Allen updated HBX-965:
--------------------------
Attachment: HBX-965-v1.txt
I have created a patch that detects the build number of the H2 jar file, and excludes the
catalog if the build id is < 55. However, this sort of assumes that you are going to
use the same version of the jar file when you run Hibernate. I guess that is a safe
assumption.
But again, adding the H2 catalog is sort of a pointless measure, so maybe we should just
exclude it all together.
conditionally exclude catalog in H2MetaDataDialect
--------------------------------------------------
Key: HBX-965
URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-965
Project: Hibernate Tools
Issue Type: Improvement
Components: reverse-engineer
Affects Versions: 3.2beta10
Environment: H2 1.0 (2007-06-17) and H2 1.0 (2007-07-12)
Reporter: Dan Allen
Priority: Minor
Attachments: HBX-965-v1.txt
Original Estimate: 1 hour
Remaining Estimate: 1 hour
Prior to build 55 (aka version 1.0 2007-07-12), the H2 database did not understand a
query that included the catalog name. For instance, if you had a table called EMPLOYEE in
the PUBLIC schema, H2.PUBLIC.EMPLOYEE would not work. After build 55, H2 understands this
query.
However, this brings up a different issue. You cannot create catalogs in H2, so really
the H2 catalog is just a bogus place holder. That has to make you wonder if putting the
catalog in the reverse engineering dialect is even wise. It makes the hbm2java generated
classes very non-portable. This debate is a bit of a fuzzy area for me.
--
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