Thomas,
thank you for this relevant information.
I did not manage to make it works completely. The hsqldb.ddl file created to
tables all right, but then I've get some exceptions when manipulating nodes and
properties : java.sql.SQLException: data exception: string data, right
truncation. Maybe I did not choose the field types well.
Anyway, I didn't know about the cached philosophy of HSQLDB. Now I understand
why we though it was a lot faster. I'll think we'll keep H2 for now.
F
Le 2011-02-14 à 3:03 AM, Thomas Mueller a écrit :
> Hi,
>
> I didn't test HSQLDB recently, but it looks like you would need to create
> a special hsqldb.ddl file first, in
> jackrabbit-core/src/main/resources/org/apache/jackrabbit/core/persistence/b
> undle/hsqldb.ddl - and then use the following configuration:
>
> <PersistenceManager
> class="org.apache.jackrabbit.core.persistence.pool.BundleDbPersistenceManag
> er">
> <param name="driver" value="org.hsqldb.jdbcDriver"/>
> <param name="url"
> value="jdbc:hsqldb:${wsp.home}/db;create=true;hsqldb.default_table_type=cac
> hed"/>
> <param name="schemaObjectPrefix" value="${wsp.name}_"/>
> <param name="databaseType" value=hsqldb/>
> </PersistenceManager>
>
>
> If you don't use "sqldb.default_table_type=cached", HSQLDB will try to
> keep all data in memory (which is faster, but quickly runs out of memory).
> When comparing HSQLDB with other databases, please note HSQLDB has lower
> durability goals (unlike H2, HSQLDB doesn't call FileDescriptor.sync).
>
> Regards,
> Thomas
>
