I have set up the generator class for two classes. One works great, the other generates wild, seemingly random, numbers. I am using an ORacle database.

I put a println statement in my setUserId method, and it is in fact "1" the javaclass rst time through. However, the database always ends up conatining some wacky value. THe second tme through generally throws an exception, probably because it can't handle the wacky database value.

Again - I have another case that works perfectly, and I can't see any differences between the way that case is set up and the way that the problem case is set up.

Does anybody have any ideas?

Here are a few snips of relevant code:

from the hbm file:

<id name="userId" column="USER_ID" type="long">
<generator class="increment" />
</id>

the oracle table:

SQL> desc bidder
Name Null? Type
----------------------------------------- -------- ------------
USER_ID NOT NULL NUMBER(19)

From the java bean:

private long userId;


public long getUserId() { return userId;}

private void setUserId(long userId) {
System.out.println("*userID=" + userId);
this.userId = userId;
}

Why do u use long here?

Folks - One more piece of info on this... I added more println() statements to my code to see what is happening with the id value in the bean:


Transaction tx = session.beginTransaction();
System.out.println(" Before: " + user.getId());
session.save(user);
System.out.println(" After: " + user.getId());
tx.commit();
System.out.println(" After tx.commit(): " + user.getId());

ON the first insert to the table, I get exactly what i would expect:

Before: 0
userID=1 (this is a println that is inside the setID method)
After: 1
After tx.commit(): 1

So, everything looks like it's in order. But, when I select from the database, I get a surprise:

SQL> select id from bidder;

ID
----------
-a.000E+46

Could this be some kind of bug in the JDBC? Is thist even a valid value inside an Oracle number(19) column?

Ramnath - I have tried both long and int on this example, and both formats fail.

Both should work...

I also have another example that uses long i got working.

OK, here is the fix that I found...

I originally used HBM2DDL to generate the table. It created the ID column as number(19). I modified the table and redefined the ID column as number (without any qualifictons.). Now, it works.

But, what is still troubling, is that my other example that is still defined as number(19) also works! So, I have this feeling that I took care of the symptom but have no idea as to what is the actual cause of the problem.

Personally, I would be using a sequence generator for Oracle.

David - Yes, I plan to use sequences eventually. I'm just going through the Hibernate in Action book now and learning the api.

Thanks for the input.