Bug #8142 Updated: on exit() from method, interbase makes a mess with transaction ids
| From: | lobbin@php.net | Date: | Fri, 11 Jan 2002 21:53:10 +0000 |
| Subject: | Bug #8142 Updated: on exit() from method, interbase makes a mess with transaction ids | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-76692@lists.php.net to get a copy of this message | ||
ID: 8142
Updated by: lobbin
Reported By: hp@oeri.ch
Old Status: Open
Status: Feedback
Bug Type: InterBase related
Operating System: Linux 2.2.17
PHP Version: 4.0.3pl1
New Comment:
Do you still experience this problem on PHP 4.1.1?
Previous Comments:
------------------------------------------------------------------------
[2000-12-06 16:40:03] hp@oeri.ch
If I exit() or die() from within a method, a begun transaction is
automatically COMMITTED(!) and I get wierd errors in the http error
log.
<?
class InterBaseFailure {
var $dbh;
var $trh;
function InterBaseFailure() {
$this->dbh = ibase_pconnect( "ibase/outerdb.gdb", "web",
"pass"
);
$this->trh = ibase_trans( IBASE_DEFAULT, $this->dbh );
}
function Save( $num ) {
ibase_query( $this->trh, "insert into dummy values ($num)" );
// now, if we exit() from here either directly or indirectly
// there's a mess with the transaction handles. I get:
// a) an error in the httpd log
// "x is not a valid InterBase link resource
// b) A COMMITTED CHANGE!!!!!
exit();
}
}
$t = New InterBaseFailure();
$t->Save( 3 );
?>
------------------------------------------------------------------------
Edit this bug report at http://bugs.php.net/?id=8142&edit=1