Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 2.5.0b5

Request #16739 Transaction rolledback with persistant connection
Submitted: 2009-10-25 02:38 UTC
From: vivien Assigned:
Status: Open Package: MDB2 (version 2.5.0b2)
PHP Version: 5.2.5 OS: Linux
Roadmaps: (Not assigned)    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 47 - 12 = ?

 
 [2009-10-25 02:38 UTC] vivien (Vivien Malerba)
Description: ------------ Started transaction are automatically rolled back when the PHP script terminates which may be inconvenient for persistant connections (this behaviour has been tested for PostgreSQL, MySQL and SQLite at least), as visible in the disconnect() method. I really need a way to disable that automatic rolling back. I know that when the connection is opened again at least the @in_transaction and @nested_transaction_counter attributes of the connection _will_ be wrong because the connection is persistant, but maybe a solution can be found using $_SESSION to save all that extra information about the connection's transaction status. I really need that bug corrected, thanks a lot

Comments

 [2010-02-12 19:57 UTC] nilya (Ilya Nazarov)
You can't keep transaction open between script runs. This is PHP database modules architecture (and architecture of the web).
 [2010-03-02 15:39 UTC] doconnor (Daniel O'Connor)
-Type: Bug +Type: Feature/Change Request