Hibernate version:2.1.7

Hi.

Is it normal that when persisting new object, it's ID gets generated regardless of exception being raised because of some constraint issue?

My application manages presentation differently when dealing with fresh (getId() == null) and already persisted objects (getId() != null).
Problem is that when new object is to be persisted, in some situations some expected db exception is raised, handled as expected exception, but my app is confused because this new object, although hasn't been persisted successfuly, now has getd()!= null , thus my app thinks it's persisted !?

Some suggestion?

-Vjeran

Yes it is normal. Think about it like this.

You are trying to persist an object into the database. It needs an ID so one is genereted before attempting to insert the object. Then, the insert fails due to a constraint error but the ID has already been generated. Databases do not 'roll back' generated IDs when there is an error creating a database entry.

I suggest you rewrite your error handling so that failures are handled safely.

Rilux is 100% on this one. Just one point to remember is that hibernate does not roll back 'object state'. If you catch a (system) exception and wish to continue it may be more prudent to close the current session and open a new one. Of course this depends on what exactly caused the exception.