ansaurus

Question

hibernate auto create in-memory hsqldb causes Sequence not found

Answer 1

+1 A:

Since you're using an in-memory database, it's not surprising that a sequence, like any other database object, is not there at export time. But I don't know why you get a full stacktrace like this. I just tried with a basic test case and here is what I get:

16:27:07.708 [main] DEBUG o.h.tool.hbm2ddl.SchemaExport - Unsuccessful: drop sequence MY_ENTITY_SEQ
16:27:07.709 [main] DEBUG o.h.tool.hbm2ddl.SchemaExport - Sequence not found in statement [drop sequence MY_ENTITY_SEQ]

In other words, it "fails" silently.

Maybe you could try to extend the HSQLDialect and override the following method:

protected String getDropSequenceString(String sequenceName) {
    return "drop sequence " + sequenceName;
}

into:

protected String getDropSequenceString(String sequenceName) {
    return "drop sequence " + sequenceName + " if exists";
}

Not tested though.

Pascal Thivent 2010-10-12 16:35:44

Thanks a lot for trying this out. I now figured out that org.lazyluke:log4jdbc-remix:0.2.4 is the one that is printing it out. If I comment out the following from my log4j.properties then these stack traces dissapear "log4j.logger.jdbc.sqlonly=info" . I'm not really sure how I can get rid of this, maybe I can configure log4j to skip it somehow.

AmanicA 2010-10-30 01:34:20

Answer 2

A:

Here is a technique I like to use to get a fresh in-memory database each test.

@Override
public void setUp() throws Exception {
    Properties p = new Properties();
    p.put(Context.INITIAL_CONTEXT_FACTORY, "org.apache.openejb.client.LocalInitialContextFactory");
    p.put("movieDatabase", "new://Resource?type=DataSource");
    p.put("movieDatabase.JdbcDriver", "org.hsqldb.jdbcDriver");
    p.put("movieDatabase.JdbcUrl", "jdbc:hsqldb:mem:moviedb" + System.currentTimeMillis());
    p.put("openejb.embedded.initialcontext.close", "DESTROY");

    initialContext = new InitialContext(p);
}

@Override
protected void tearDown() throws Exception {
    initialContext.close();
}

Basically, give a unique database name by appending System.currentTimeMillis() and rebuild the embedded container for each test.

Keeps you from having to cleanup after your tests yet doesn't require a new jvm for each test.

David Blevins 2010-10-14 22:23:39

Thanks, but as stated in Pascal's answer the problem is with hibernate dropping/creating the sequences but the error should really be ignored.

AmanicA 2010-10-30 01:41:24

ansaurus

tags:

views:

answers:

hibernate auto create in-memory hsqldb causes Sequence not found

related questions