-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 
Author Message
 Post subject: Problem with implementing Optimistic Locking with version
PostPosted: Wed Feb 28, 2007 5:42 am 
Newbie

Joined: Wed Feb 28, 2007 3:44 am
Posts: 1
As I am implementing Optimistic locking using version number. I added the <version> element in my hbm.xml.

But the problem is when i package everything and deploy in JBoss, a new column for the version number is created in the table concerned which is holds a null value for every row.
Hence when i edit a particular row, instead of updating the row, a new row is created.

So is there anyway i can update the schema with the version column set to Not Null and Default value = 0? I mean through Hibernate.

If not, anyway I can avoid creating a new row?


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.