I'm using sybase ase 12.5 and I have a strange problem. I'm doing a

MyObj myObj = new MyObj();
myObj.setName("tim");

session.save(myObj);
transaction.commit();

(not verbatime)

On Oracle and MySQL, this works fine, but on sybase it complaints that the field "name" cannot be null. I have, of course, run it through the debugger and the "name" field on the object is certainly not null.

There is a constraint in the database that prevents the field from beeing null. When I remove it, it works fine.

Does Hibernate attempt to create an empty object in the DB first and then fill in the rest before commiting?

I don't suspect so. You could confirm this though by enabling debugging. Please post the trace, your hibernate mapping files and the java code you are executing.

Yes but only in this case AFAIK, and probably depending your id generator

I use the hilo generator

I used the wrong driver... it works now!!! sorry guys.