Hi all,

I working on a project that using Hibernate for DAOs (in conjunction with Spring). For our unit testing, our underlying DB2 database is being swapped for an in-memory instance of HSQLDB, by injecting a new datasource into to client code using Spring.

The problem is due to Hibernates auto creation of schemas; the hbm files look like:


Inside of the Session Factory bean, we are setting to dynamically create the tables (as the database is in-memory and is setup each time the JVM runs) such that the DAOs are able to use the DB without any additional configuration. However, this tries to create a table similar to the example above using SQL such as:



This fails as the schema is not defined:



This has been discussed a few times, but without any resolution, esp. when using Spring. So far I can't find a solution without having my jUnit code manually create the schema (which defeats the point of using hbm2dll as the schema will only be created after this has already run), and forcing the Spring controlled beans to be lazily instantiated to control them from being loaded prior to any manual SQL being run.
Has anyone had prior experience of this, and any advice on how to overcome this problem? We're using Hibernate 3.2.1.ga.

Best regards,
-James

SCHEMA is a reserved word? =)

you apparently have set hibernate.default_schema to some schema name that does not exist.

I was using SCHEMA as an example...



This works for RDBMS's that support implicit schema creation, but not for ones that don't, i.e. HSQLDB.

I still don't think there is a workaround for this issue!

hibernate *only* put schema in their IIF schema attribute is set OR if hibernate.default_schema is set.

So if you really have a schema in your database make sure it is available for hibernate to create stuff in...it's that simple.

Thanks for your reply Max. Do you think that this could be a candidate feature for future versions of Hibernate?
When doing unit testing using an in-memory, in-process DB instance, its requires that the DB is initialized (i.e. schemas created) prior to Hibernate trying to create any tables that don't exist. I don't think this is possible as Hibernate fires off as soon as the JVM starts without having some sort of hook to act as a pre-processor to the Hib mapping process.

Hibernate does not fire off before you tell it to. Do the adjustments to the underlying database before you do that.

and yes there an issue for making this a more integrated part of schemaexport/update at some point...but until now noone have supplied a workable patch.

hi all,
has anyone found a workaround to this? i am stuck in the same situation using in-memory database and a schema.......

thanks in advance and regards
marco

Hi all.
I had the same problem.
My mappings have different schemas. Anybody has some solution ?
I'm using the HSQLDB that don't have implicit schema creation, in the same architecture that JHarvey :(

JHarvey, how do you do ?

thanks

Hi all.
I had the same problem.
My mappings have different schemas. Somebody has some solution ?
I'm using the HSQLDB that don't have implicit schema creation, in the same architecture that JHarvey :(

JHarvey, how do you do ?

thanks