]
Steve Ebersole commented on HHH-1853:
-------------------------------------
I think the only viable solution is a new construct that explicitly identifies the thing
to be created first and dropped last. Perhaps <database> as a corollary to
<database-object>? So <database> would name the create/drop commands just
like with <database-object> but their importance is in ordering.
What I certainly do not want is dialects having to know how to generated create/drop DDL
for these things.
WDYT?
CREATE SCHEMA inside database-object need to execute before tables
are created
------------------------------------------------------------------------------
Key: HHH-1853
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1853
Project: Hibernate Core
Issue Type: Improvement
Affects Versions: 3.1.3
Environment: hsqldb 1.8.0
Reporter: Mattias Jiderhamn
Priority: Minor
Attachments: create-schema.patch, create-schema2.patch
In order to have Hibernate create database schemas for hsqldb, you have to insert a
<database-object> in your mapping file
(
http://forums.hibernate.org/viewtopic.php?p=2305138). Problem is, all the database-object
statements are executed after the tables are created, so tables in non-default schemas
will not be created. To get around this, you have to first use
Configuration.generateSchemaCreationScript() to get the schemas, and then
Configuration.generateSchemaUpdateScript() to get the tables inside the schemas.
(This is a bit problematic when using Springs LocalSessionFactoryBean)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: