|
database
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Update ConflictAppreciate if you guys can resolve my issues
I am trying to write a store procedure that can handle Update Conflict Senario to be handled --Row was deleted --Row was modified by other user --Row is locked What is the best way to do it in Stored Procedure also is Timestamp field is good choice for detecting update conflict and should I index that field also. Thanks Tanweer you will need to think of this only if you are going for optimistic row
locking. And if you do, its better to add a timestamp column to do the check. And you don't need to add it to the index. And how to implement it, You should read this post today Is my beloved TSEQUAL() officially dead in 2005? 5/2/2006 6:55 PM PST This will give you an idea. Hope this helps. Thanks for the great help.
Show quote "Tanweer" wrote: > Appreciate if you guys can resolve my issues > > I am trying to write a store procedure that can handle Update Conflict > Senario to be handled > --Row was deleted > --Row was modified by other user > --Row is locked > > What is the best way to do it in Stored Procedure also is Timestamp field is > good choice for detecting update conflict and should I index that field also. > > > Thanks > Tanweer  |
|||||||||||||||||||||||
Other interesting topics