HSQL DB Identity & Auto Increment

Question

We are trying to write records to this table:
create table location_groups
group_id identity
,jdoversion integer
,jdoclass varchar(255) default 'path.impl.LocationGroup' not null
,group_name varchar(100) not null
,group_parent_id integer
Package.jdo is:
<package name="path">
<class name="LocationComponent">
</class>
</package>
<package name="path.impl">
<class name="LocationGroup" persistence-capable-superclass="path.LocationComponent">
<!--<extension vendor-name="kodo" key="jdbc-field-map" value="one-one"/>-->
<extension vendor-name="kodo" key="jdbc-auto-increment" value="true"/>
<field name="children" persistence-modifier="persistent" default-fetch-group="true">
<collection element-type="path.impl.Location"/>
</field>
</class>
and package.mapping is:
<package name="path">
<class name="LocationComponent">
<jdbc-class-map type="horizontal"/>
</class>
</package>
<package name="path.impl">
<class name="LocationGroup">
<jdbc-class-map type="base" pk-column="GROUP_ID" table="LOCATION_GROUPS"/>
<jdbc-version-ind type="version-number" column="JDOVERSION"/>
<jdbc-class-ind type="in-class-name" column="JDOCLASS"/>
<field name="path.LocationComponent.name">
<jdbc-field-map type="value" column="GROUP_NAME"/>
</field>
<field name="children">
<jdbc-field-map type="one-many" table="LOCATIONS" ref-column.GROUP_ID="GROUP_PARENT_ID"/>
</field>
</class>
</package>
I have tried all manner of configurations but the error remains the same:
25-Apr-2008 16:05:24 com.ea.albt.infrastructure.persistence.jdo.JDODataStore BeginTransaction
CONFIG: Starting transaction
25-Apr-2008 16:05:24 com.ea.albt.infrastructure.persistence.jdo.JDODataStore updateObjects
FINE: Updating object ALBT Loc1209135924484 (has not yet been persisted)
25-Apr-2008 16:05:25 com.ea.albt.infrastructure.persistence.jdo.JDODataStore updateObjects
WARNING: Failed to persist/update objectALBT Loc1209135924484
kodo.util.FatalDataStoreException: Attempt to update the sequence table "JDO_SEQUENCE" failed. The sequence table is typically created when you run the mappingtool's refresh action on any datastore identity class. If you have not run the mappingtool but want to create the sequence table, run:
java kodo.jdbc.schema.DBSequenceFactory -action add
NestedThrowables:
Why is Kodo trying to use the jdo_sequence table when we want it to use the HSQLdb identity field ?

Answer 1

We have many users using single field identity and auto-increment together.