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:252364 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
