[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1853?page=c...
]
Ed Gow commented on HHH-1853:
-----------------------------
The crux of the issue seems to be just the creation of schema, not dropping schema.
Earlier comments about dropping more than is intended provide good reason for not dropping
schema from Hibernate. Can a version of the patch for this bug that only creates, but
never drops, schema make it into a release?
This bug is a serious impediment for the common case of using an H2 in-memory database for
unit testing.
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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira