You can always just use locking at the DB level. I am not sure about anything other than MSSQL but locking can be done there instead of CF if need be.
http://www.sql-server-performance.com/at_sql_locking.asp ----- Original Message ----- From: "Robertson-Ravo, Neil (RX)" <[EMAIL PROTECTED]> To: "CF-Talk" <cf-talk@houseoffusion.com> Sent: Thursday, September 07, 2006 10:13 AM Subject: Re: Locking Theory > Select with no lock should allow results to be returned - though it will > effectively be a dirty read. > > > > > > > > "This e-mail is from Reed Exhibitions (Oriel House, 26 The Quadrant, > Richmond, Surrey, TW9 1DL, United Kingdom), a division of Reed Business, > Registered in England, Number 678540. It contains information which is > confidential and may also be privileged. It is for the exclusive use of the > intended recipient(s). If you are not the intended recipient(s) please note > that any form of distribution, copying or use of this communication or the > information in it is strictly prohibited and may be unlawful. If you have > received this communication in error please return it to the sender or call > our switchboard on +44 (0) 20 89107910. The opinions expressed within this > communication are not necessarily those expressed by Reed Exhibitions." > Visit our website at http://www.reedexpo.com > > -----Original Message----- > From: Tom Kitta > To: CF-Talk > Sent: Thu Sep 07 17:03:20 2006 > Subject: Re: Locking Theory > > cftransaction could lock for the duration of user edit ... it however, > depending on the DB level of locking could prevent any other user from > reading data in the table. I would consider implementing such locking a bug > not a feature. > > Try the following in SQL server query analyzer: Begin Tran [some update of a > > table] > in new window try to select on the table and do some other ops. See what > happens. After you are done do 'commit' in transaction window or 'rollback'. > > Depending on locking you wil need to commit or rollback trans before you can > > see anything done by select > > TK > > > > > >>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. > > > > cftransaction is not a panacea either: it only locks for the time of a > > transaction, > > not for the time the user will edit a record. > > > > -- > > _______________________________________ > > 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:252369 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
