<snip> > the pconnect supposedly allowed an app to use the same connection if > one was available. so an app would establish the connection on page > 1, and page 2 could use the same db connection... this is required as > i understand it if you're going to do transactional processing, as > once the connect dies, the actions being performed are rolled back if > you haven't done a "commit"... </snip>
AFAIK, transactions do not span across multiple script executions, only multiple queries within the same script execution. The purpose of a persistent connection is to reduce the total number of db connections which are open to a server. AFAIK a persistent connection will be reused when a request is made for a connection with a specific username, password and db, and one already exists with said parameters. AFAIK it has nothing to do with transactions spanning multiple script executions. Once a script has finished executing, as a previous poster wrote, PHP will close the connection (if it's persistent it's left in the pool to be reused) and if a transaction was not commited or rolled back, then it will be rolled back by default. So if you have one php script which starts a transaction and then executes five queries, at the end of that script being executed unless you commit the transaction, it will be rolled back by default. Even if you are using persistent connections, if this were to happen the transaction would still be rolled back. This is all AFAIK, so I could be wrong. If I've put some incorrect information here, please correct it and let me know where I've gone wrong. Cheers and HTH, Pablo -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
