Can I use the type 'integer' for an id that has generator 'identity' ?

I ask because the SQL to create the table created by SchemaExport is wrong for Sybase.

If I have the mapping file:
<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE hibernate-mapping
PUBLIC "-//Hibernate/Hibernate Mapping DTD//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd">
<hibernate-mapping>
<class name="test.ABusinessObject" table="ABusinessObject">
<id name="id" type="integer" unsaved-value="null">
<generator class="identity"/>
</id>
</class>
</hibernate-mapping>

then SchemaExport produces SQL:
create table ABusinessObject (id INT IDENTITY NOT NULL, primary key (id))
But this fails on Sybase ('Identity field 'id' must be a numeric with a scale of 0 and not null allowed')

If I change the type to long i.e.
<id name="id" type="long" unsaved-value="null">
the SQL is okay
create table ABusinessObject (id NUMERIC(19,0) IDENTITY NOT NULL, primary key (id))

my dialect property is set to
<property name="dialect">net.sf.hibernate.dialect.SybaseDialect</property>

is there a workaround I can use or do I have to have 'long' id's ?

try the sql-type attribute

thanks!

I changed my mapping to

this allowed SchemaExport to produce


So this gives me a mapping that I can also use to generate DDL for creating the table in Sybase.

But ...
It seems to me that this should be handled in the hibernate SybaseDialect.

Currently sqlCreateString method of net.sf.hibernate.mapping.Table gets the SQL for creating a column in two steps
1. ask the Dialect for the type to use for that column
2. if the column is flagged as an identity column ask the Dialect for the qualifier to apply (getIdentityColumnString() of Dialect)

from my perspective it looks like this should be changed to test if the column is flagged as an identiy column ask the Dialect for identity type && the identity column string
else
proceed as normal (i.e. existing code)

should l I raise this in the hibernate JIRA ?

yes please. With patch if you have time.

Hi,
I have posted an effort at a patch to fix this
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-684