javax.persistence.Version is not mapped to the @version metadata in orientDB

[tade82]

Hi,

I am using OrientDB and strugling with version handling. I want to use optimistic locking on the client side but javax.persistence.Version is not mapped to the @Version metadata in OrientDB instead of that a new property column is created.

BR and keep up the good work,
Peter

[tade82]

Because the lack of version handling the optimistic locking is not working.
Eg.: If you have an entity in the database with id X and you create a new entity with the same X id and save it to the db, it will be saved flowlessly (overwrites the first version). In this case the proper working would be an OConcurrentModificationException since the versions are different.