Hi,

I generate a id by 'TableGenerator'

<id name="berichtId" column="bericht_id" type="integer">
<generator class="net.sf.hibernate.id.TableGenerator">
<param name="table">Primary_Key</param>
<param name="column">next_id</param>
</generator>
</id>

The table Primary_Key was updated after save a new record to the table bericht but the record have the wrong id. I try many configurations with the same result. What is wrong?

I use a Oracle 8 and hibernate 2.1

thanks for help

SUPPLEMENT:

I have with all other generators the same problem. The format of the saved id's are '1,3E-76' or '4,7E-105'. Who can help me?

Joe

I've also noticed similar behavior. It doesn't happen for every table, but it's reproducible when I find it. The problem doesn't seem to be with Hibernate, however. I've traced into the code and found that hibernate IS generating the correct PK, but somehow when it gets saved in the DB it's always some strange number. I am also using Hibernate 2.1.4 with Oracle 8.

One thing I've noticed is that my column is type Integer. Once I switched it to Number the problem went away. The weird thing is that we have many tables with Integer PK columns and this problem is sporadic. I've tried switching oracle jdbc drivers, but that didn't help. I also ran the test against a SQLServer database and the values inserted were correct. It seems like a problem with Oracle to me, possibly with our installation.

Are you by any chance inserting/updating a DATE data type in this?

If so, then I can point you at an Oracle bug (fixed by upgrading to 8.1.7.4) in which if you use a 9.2 or higher client to connect to an 8.1.7.3 or earlier database, you can get number corruptions if a date is inserted/upated also.


Solution:

Get the oracle server patched up to 8.1.7.4, or downgrade your jdbc drivers to a pre 9.2 version (depending on which is more appropriate to your installation)

(for the curious this is Oracle Bug# 2199718)

Yes it looks like it's happenening when Dates are involved. I tried to take the Date out of the inserts and it worked fine, so I think you're correct about this. We're currently using 8.1.7.0, and are going to try out the 8.1.7.4 patch.

Thanks for your help.