You need for this application level locking that someone mentioned few posts back - essentially implement "source safe" type of locking with your records like files in source safe.
I assume that users want to look at the record, make changes and save without having to worry about any other user doing the same thing to the same record at the same time. cftransaction locks that DB actually follows may lock the whole table and you should *never* place any user code or some prolonged operation inside transaction block. I.e. transactions should take as little time as possible - we are talking ms here not even seconds. TK ----- Original Message ----- From: "Claude Schneegans" <[EMAIL PROTECTED]> To: "CF-Talk" <cf-talk@houseoffusion.com> Sent: Thursday, September 07, 2006 10:48 AM Subject: Re: Locking Theory > >>Cftransaction with the isolation attribute. > > Ok, but the lock terminates with the closing </CFTRANSACTION tag, right ? > So how could one > 1. lock a record, > 2. read the record > 3. edit the record > 4. update the record > 5. unlock the record ? > > At least (1,2,3) and (4,5) could be in different templates. > > -- > _______________________________________ > REUSE CODE! Use custom tags; > See http://www.contentbox.com/claude/customtags/tagstore.cfm > (Please send any spam to this address: [EMAIL PROTECTED]) > Thanks. > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:252358 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
