Hibernate Automatic Versioning

Question

I have developed a customer maintenance application. Users can alter the customer details via web interface. I want to handle the following scenario:

User 1 loads customer1 details.
User 2 loads customer1 details.
User 1 changes and saves customer1's name.
User 2 only changes and saves customer1's age.

In the scenario above, finally database holds customer1's old name and the new age because User 2 overwrites User 1's update. I'm using Hibernate. I had heard that Hibernate Automatic Versioning supports this. If any one know how to handle this please advise me.

Behrang Saeedzadeh · Accepted Answer · 2011-10-03 05:33:11Z

13

You just need to add a field annotated with @Version:

public class Customer { @Id private Long id; @Version private Long version; // rest of the fields, etc. }

Read this article for more information.

answered Oct 3, 2011 at 5:33

Behrang Saeedzadeh

48.2k27 gold badges126 silver badges168 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

MeetJoeBlack Over a year ago

I use SpringJDBC over any ORM in my Java Project. But I need to add some Hibernate's @Version functionality, to prevent some situation like discribed there. So maybe you can suggest me JDBC realization?

Behrang Saeedzadeh Over a year ago

The general term for this approach is called optimistic locking. You can find some guidance here: stackoverflow.com/a/8880896/309683

Nirmal- thInk beYond · Accepted Answer · 2011-10-03 05:31:52Z

one solution, when second request tends to update details first check if it is updated after details loaded, if so then raise exception and allow user to change after loading details again, you can use modification time stamp to compare

Collectives™ on Stack Overflow

Hibernate Automatic Versioning

2 Answers 2

2 Comments

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

Comments

Linked

Related