Sean A Corfield wrote: > > <cftransaction> > ... some code ... > callAnotherDatabaseMethod() > ... more code ... > </cftransaction> > > Any database activity in callAnotherdatabaseMethod() would not be > rolled back if you tried to rollback the cftransaction shown above.
Even worse, some people have reported that after callAnotherdatabaseMethod() is committed the transaction can not be rolled back anymore. I haven't had time to verify this myself, but you should check all your transactions for all possible errors that may occur. > This seems to be bug #49953 and my guess is that you won't see a fix > for this for quite a while (but I'm willing to be corrected by Phil or > Debbie or...!). <quote> Ok, I was able to find more information on this issue. I discovered that it is not actually a bug, but rather the result of a decision made during the CFMX design and development process. Because of the type of transactions being used, UDFs would have to be able to traverse up the tag tree to see if they are contained in a transaction, which they cannot do, which is why transactions appear to be broken when you call a UDF inside of them. As I wrote earlier, I think the work-around is to move your SQL up into your transaction. </quote> C. Cantrell http://webforums.macromedia.com/coldfusion/messageview.cfm?catid=6&threadid=446316 This would be a design decision I am not happy about. I would love to have the ability to pass transactions around into CFCs/UDFs (and it is pretty much the only way I can think of to implement this). Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
