]
Max Rydahl Andersen closed HBX-965.
-----------------------------------
Resolution: Fixed
Fix Version/s: 3.2.beta12
note: a better general fix is that we actually detect if there is more than one catalog
reverse engineered and only set the catalog if that is the case. (same for schema's)
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
Fix For: 3.2.beta12
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: