On 17.08.2007 22:53 John Siracusa wrote: >> So, if I understand it right, there are really two problems: >> - no rollback when it should be (my do_transaction above) >> - a rollback when there should be none (your warn) > > Once the database handle is reset to auto-commit, any subsequent > rollback will have no effect anyway, so one thing at a time :) > >> even if I comment the call to reset_startup_state out in Apache::DBI (as >> suggested before) the above do_transaction code still doesn't roll back. > > That's because DBI does the same thing as reset_startup_state() in its > connect() method (around line 683 in DBI.pm version 1.58) and you > didn't comment that out :)
Thanks for all the patient explanations from you and all the others who helped! > I just meant that it'd be a change in historic behavior that could > break some people's code when they upgrade (not that RDBO is 1.0 yet, > but it's still nice to avoid this kind of thing, if possible). Good attitude, but for me it looks safe then. - Michael ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
