If this is true - wrap the code in a named lock: <cflock name="aUniqueLockName" type="exclusive"> .... your SQL here </cflock>
A named lock ensures that only one thread at a time will be allowed to run the code within the cflock tag. CFTransaction will not give you this same level of isolation. Jake Pilgrim >You probably have a race condition, where two people execute the code >at the "same time", and the order goes like this: > >A - delete >B - delete >A - insert >B - insert > >In this case, you'd expect the fourth statement (the second insert) to >throw the dupe key exception. > >cheers, >barneyb > > > >-- >Barney Boisvert >[EMAIL PROTECTED] >http://www.barneyb.com/ > >Got Gmail? I have 100 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:288117 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
