Hi,
I implemented optimistic locking with version number. But Now I had a different requirement. Please go thru it.

I have order table, in which there is a coulmn called Deltek_Number.
User A--retrieves this order and start modifying it. (For him, deltekNumber is noneditable. infact, we dont show in the presentation tier)

User B--> retrieves Deltek Report ---> he can perform bulk update on orders for deltek number.

If user A tries to Update his order, naturally he will get optimistic locking exception. Client is asking us to avoid this problem in this situation.


Any pointers?

Thanks & Regards
Nagesh G

Need help with Hibernate? Read this first:
http://www.hibernate.org/ForumMailingli ... AskForHelp

Hibernate version:

Mapping documents:

Code between sessionFactory.openSession() and session.close():

Full stack trace of any exception that occurs:

Name and version of the database you are using:

The generated SQL (show_sql=true):

Debug level Hibernate log excerpt:

What the Client is asking for makes no sense. If you don't update the Version, then when A updates the Order, you will OVERWRITE what B has done. That's what you're trying to avoid by using a Locking Strategy.

Thats what I am trying to convince the client and that is the reason why we implemented optimistic locking.

With Hibernate3, you could use a hql update statement to implement UserB performing "bulk update on orders for deltek number". By default these update statements do not increment the version number.

Thank you.
Infact we didnt get that idea eventhough we are using bulk update in other places.
My mistake.

Thanks & regards
Nagesh G