Nullable ids with 3.0 tools

hsivonen · **Posted:** Sat May 07, 2005 2:16 pm

The id declarations in my mapping file look like this:
<id name="id" type="int" column="id">
<generator class="native"/>
</id>

The 2.x tools generated Integer fields which were obviously null when a new object was created using the no-args constructor.

The 3.0 Ant task (from CVS today) generates int fields which start out as zero. The persister complains about duplicate ids (multiple objects with 0 as the id).

How do I make the Ant task produce Integer ids?

max · **Posted:** Sat May 07, 2005 7:58 pm

hmm this is caused by the fact we now obey that when a properties column can not be null then we generate the basic type...but i guess for primary keys we should not do that.

make a jira issue for it - thank you.

hsivonen · **Posted:** Sun May 08, 2005 4:44 am

max wrote:

hmm this is caused by the fact we now obey that when a properties column can not be null then we generate the basic type...but i guess for primary keys we should not do that.

Is there a workaround?

max wrote:

make a jira issue for it - thank you.

Bug filed: http://opensource.atlassian.com/project ... se/HBX-258

max · **Posted:** Sun May 08, 2005 4:52 am

actually i'm surprised this causes problems since hibernate3 should detect that 0 means unsaved for you.

but try to set unsaved-value="0" and see if that works for you.

max · **Posted:** Sun May 08, 2005 5:03 am

a work around is also to use <meta attribute="property-type">TheTypeYouWant</meta>

which i just fixed a bug around in the cvs so it should soon work in the anoncvs too.

hsivonen · **Posted:** Sun May 08, 2005 9:51 am

unsaved-value="0" worked. Thank you.

max · **Posted:** Mon May 09, 2005 5:50 am

btw. i just tested this and unsaved-value="0" really should not be necessary!

How do you get the duplicate id error ?