On 2 June 2014 14:46, Albert Lee <allee8...@gmail.com> wrote: > @Version is used to support optimistic locking semantics at the object > level and bear no implication to db row or ownership. > > "In what circumstances would the Parent version be bumped by one?" > > When an entity is changed and needs to be updated back to the database row, > the version field must be incremented to avoid updating row that may have > been updated by another client or catch the case where another client > already had the row updated. > > "Is there an option in OpenJPA to turn off bumping of the parent version?" > > You can disable optimistic lock versioning by removing @Version from the > version field. However you are risking overwriting object content in the > db unless your application can guarantee this scenario would not happen. >
You seem to have missed the point. I know what optimistic locking does and what it is for. I am seeing situations where a Child is modified, and no change is made to the Parent, but still the Parent version still gets bumped. What I want to know, is under what circumstances does OpenJPA consider a change to the Child, to be a change to the Parent, and is this rippling of changes up to parent possible to disable, without entirely disabling the optimistic locking on Parent or Child. Rupert
