To all who replied to my initial question ...
I actually did *not* have problems with transactions in the way I first
implemented my abstraction layer. In the case of PHP
"If a second call is made to pg_connect() with the same
connection_string, no new connection will be established, but instead,
the connection resource of the already opened connection will be returned."
The bug was in my transaction testing code. I was forcing PHP to time
out to check weather the transaction went through or not. In the script
I was catching the time-out but it so happens that there is a bug in PHP
when it comes to catching connection time outs using the
connection_status() function ...
Jc
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
- [PHP] PostgreSQL/PHP: transactions: how-to abstrac... Jean-Christian Imbeault
- Re: [PHP] PostgreSQL/PHP: transactions: how-t... Jason Sheets
- Re: [PHP] PostgreSQL/PHP: transactions: h... Jean-Christian Imbeault
- Re: [PHP] PostgreSQL/PHP: transaction... Ray Hunter
- Re: [PHP] PostgreSQL/PHP: transaction... Ray Hunter
- Jean-Christian Imbeault