Well that's just it, from what Dave (and Simon's article) are saying, this is not the case. CFTRANSACTION (with the appropriate level of isolation) should handle concurrency across threads as well as handling rollbacks. I'd like to confirm that this is true, because if it is, my whole understanding of CFTRANSACTION was incorrect and things would be a lot easier without having to add locks manually.
On 9/11/07, Claude Schneegans <[EMAIL PROTECTED]> wrote: > > >>people had tried CFTRANSACTION alone and it didn't make a difference. > > CFTRANSACTION won't help for race condition problems, it only handles > rollback > if a problem happens during execution. > But two updates can still compete one against another without causing > any execution error. > > CFLOCK will handle race condition. > > -- > _______________________________________ > REUSE CODE! Use custom tags; > See http://www.contentbox.com/claude/customtags/tagstore.cfm > (Please send any spam to this address: [EMAIL PROTECTED]) > Thanks. > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Get involved in the latest ColdFusion discussions, product development sharing, and articles on the Adobe Labs wiki. http://labs/adobe.com/wiki/index.php/ColdFusion_8 Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:288195 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
