[Info-ingres] Optimistic Locking approach for Asp.Net

[Ingres Forums]

(Caveat: I know nothing about your application so I don't know why
preemptive exclusive locking is so important to you nor what the limits
on an acceptable solution are.)

You could probably rig up some kind of versioning using rules and
procedures pretty easily, though I wouldn't use version numbers or
timestamps.  If I set up row versioning I'd probably tag the rows with
the transaction ID (*dbmsinfo('db_tran_id')*) that did the update.  That
way I wouldn't get spurious rejections of updates to rows I'd just
updated myself.


-- 
rhann
------------------------------------------------------------------------
rhann's Profile: http://community.actian.com/forum/member.php?userid=131
View this thread: http://community.actian.com/forum/showthread.php?t=16919