Claude Schneegans wrote: > > For my applications, I have no problem presently as few people are > working in the same time, > but in general, how would you lock a certain record in a table while > some one is > working on it ?
I wouldn't. I would refuse an update to an old row version and present the error to the user. It is basically serialized writing and read-committed reading. Check out chapter 5 "Multiversion Concurrency Control" of "Concurrency Control and Recovery in Database Systems" http://research.microsoft.com/pubs/ccontrol/ for more details. Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:252521 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
