Yes, we have a real world scenario and we're having that issue. We're also having the issue when we jump to other page in cflocation.
I agree the right thing to do would be to just rollback in the catch, but we're catching errors without rethrowing in parts of the application that doesn't and shouldn't ever know we're currently inside a transaction. That's why i think OpenBD shouldn't leave the transactions opened once the page execution have ended. Regards. On Fri, 2009-07-24 at 07:51 -0400, Adam Haskell wrote: > I'm not saying this should or should not be fixed but is there a real > world scenario where you would do this? I would like to think not, if > there is I would think that you should explicitly state you want the > transaction rolled back, or committed. > > Adam > > > On Fri, Jul 24, 2009 at 6:39 AM, Victor Balada Diaz > <[email protected]> wrote: > > Hello, > > When we do a cfabort inside a cftransaction the transaction > never ends and leaves the table locked instead of rolling back > the transaction. > > Example code: > > <cftransaction action="begin"> > <cfquery name="X" datasource="ds">INSERT INTO table > VALUES('a')</cfquery> > <cfabort/> > </cftransaction> > > If you execute this code, the first time it leaves the > connection > and the transaction opened. So if i try a second execution of > the same > code it waits forever until the first one is terminated, which > never > happens. > > FIX: > > cfabort should close all currently running transactions. > > Thanks in advance. > Regards. > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official site @ http://www.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
