We noticed that when we do not use an @Version property for the
optimistic locking check, then ebean will only check that the olf
values of the changed property's are still the same in the database
(in the where clause).
So if some columns in the database row are changed by an external
process but not by ebean then we will not get an optimistic locking
Is there a property or setting to tell Ebean that it's not the only
one changing the database? So that it will include all property's?
Of course such a property should affect caching also (by disabling the
Btw, this is more a generic remark then something we need. As we found
a way to use an @Version timestamp property that is updated by both
systems hitting the database.