greetings!

i create an entity instance which is persisted and is given id and version number (zero it is). There are no other entities with same unique persistent identity in persistence context (naturally). Version field holds 0 value until em.flush() is called (flushing is controlled via seam conversations, and is MANUAL). Context is written to db, but that particular entity gets version value 1 (sometimes even StaleStateException is thrown and data is still written to db). What could cause such a behavior?

thanks

The StaleStateException is fairly consistent in why it is thrown:



http://www.hibernate.org/hib_docs/v3/api/org/hibernate/StaleStateException.html

My guess is that you might be updating or deleting records before they are even committed to the database. saveOrUpdate does not need to be called if the objects are already associated with the session. You may be issuing this call too often. See if the objects you are saving are indeed detached or transient objects, and not persistent objects under the spell of the Hibernate Session.

This tutorial on How Hibernate Works might be helpful.

http://www.hiberbook.com/HiberBookWeb/learn.jsp?tutorial=07howhibernateworks

-Cameron McKenzie

Hi,
I think version value changes only when any update happens to the record. i.e. only when update query is fired.

First of all if you are not changing the value of a bean why do you need to call flush() method for it . I assume that you are calling flush() because some other object has changed.

Let us assume there is "User" entity with "company" column.
Let u1.comany="OsCommerce".

Whenver there is any change to u1.company field, Hibernate "marks" the change using "dirty flag" on the entity. At the time of flush a set of update statements will be run for all objects that are "dirty".
So you need to see if you are calling any setters on the object with the old values again set to the fields i.e. you call user.setCompany( "OsCommerce").
Here You are not actually changing the value. But still you are calling the setter method. I am not sure for such kind of setter invocations (where there is no change in the actual value), whether an update statement will be run or not. You need to enable show_Sql=true for hibernate and see what statements it is executing.
( What will happen if you call user.setCompany(new String("OsCommerce") )? I need to check )

What I suggest is to enable show_Sql=true in cfg.xml and see what statements are executed to understand whats going on.

thanks for explaining "dirty flag"concept, but i'm not sure that's the case:

my entity is brand new, and after persist() was called upon it no further setter accesses its attributes. i have sql output turned on and it shows insert command for the entity (among many others) and then at the and update command where version gets incremented.