Thanks Brian! Brian Kotek wrote: > Yes. CFTRANSACTION only creates a transaction for the current thread > (actually the current database connection from the connection pool). If > multiple threads could be running the same process at the same time, > resulting in a race condition, then you need to lock that set of queries as > well. Use a named lock so that it only applies to that block of code, or > move the code into a stored procedure which should allow the database itself > to manage any concurrency issues. > > On 9/11/07, Vince Collins <[EMAIL PROTECTED]> wrote: > >> Sorry for my ignorance on this, >> >> I would have suggested using cftransaction. However, now, I'm thinking >> that cftransaction may just ensure that that particular "thread" of >> commits are done in order but it doesn't prevent other "threads'" from >> colliding with the database which is why cflock is used? >> >> Is that correct? >> >> Vince >>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Check out the new features and enhancements in the latest product release - download the "What's New PDF" now http://download.macromedia.com/pub/labs/coldfusion/cf8_beta_whatsnew_052907.pdf Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:288155 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
