Bug #14113 Updated: transaction / postgres backend

ID: 14113 Updated by: sander Reported By: n.dose@leo-media.de Old Status: Feedback Status: Closed Bug Type: Feature/Change Request Operating System: linux (suse) PHP Version: 4.0.6 New Comment: No feedback. Closing. Previous Comments: ------------------------------------------------------------------------ [2001-11-19 18:25:55] sniper@php.net There is this (undocumented) function: pg_last_notice() Which returns the last notice set by backend. Does this do what you need? (I don't know about postgresql so much. :) Also note that you should update your PHP to 4.1.0 as soon as it is released since there was a serious bug in this which caused segfaults. You can find the latest RC from: http://download.php.net/~zeev/php-4.1.0RC3.tar.gz --Jani ------------------------------------------------------------------------ [2001-11-19 06:18:32] n.dose@leo-media.de If I commit a transaction, if it is succesfully executed or not is not communicated: a pg_exec($conn, "commit") will always return TRUE, since the "commit" command itself is succesfully carried out (tho maybe each item in the transaction is not!) if there were some way to see if you were in *ABORT STATE* (what you would see in the backend in fouled-up transactions), that would solve everything. Or: generally, it would be useful in some scenarios to be able to obtain messages from the backend. There is already a pg_errormessage() function. Why not a pg_message() function? This would also solve my problem. thanks a bunch, otherwise i am a very happy customer! Nathaniel Dose ps: "features" is misspelled as "fatures" when you click the "+" button to insert user notes into the online documentation. ------------------------------------------------------------------------ Edit this bug report at http://bugs.php.net/?id=14113&edit=1