On May 18, 2006, at 7:34 PM, Bill Moseley wrote:
My transactions are all inside eval with a rollback (the modified do_transaction() code). Is there a situation that the transaction would not get rolled back and still have the apache child alive to do the cleanup?
i've had apache die and not roll back mid transaction in a few cases. then the next child resumes in that transaction. if the child dies, you shouldn't have anything to worry about - the db connection/request should time out and the db should rollback on its own.
personally though, i like to keep it safe and tack on a cleanup handler that forces a rollback on my write db
