Ryan Wynn wrote: > > Actually, what I was saying was that applying session.lock in the > actionListener for my Datascroller fixed my Lazy exception. That is to > say it worked without the underlying data changing. I wonder what would > happen if between requests the data had changed. Is hibernate > consulting the underlying data or any cache to compare with my object? > If so what if it finds a difference? > > Well what happened to me once was that I locked the object changed it saved it and hibernate simply refused the safe and went on without throwing an exception ;-)
But that is not the case of locking changed data, what probably would happen is that it either would overwrite the data with the latest state of the db, or would throw an exception. Anyway hibernate is a total beast in this area unfortunately
