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 > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Download the latest ColdFusion 8 utilities including Report Builder, plug-ins for Eclipse and Dreamweaver updates. http;//www.adobe.com/cfusion/entitlement/index.cfm?e=labs%5adobecf8%5Fbeta Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:288153 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
