note 1550 modified in function.ociexecute by sixd
| From: | sixd@php.net | Date: | Mon, 05 Oct 2009 02:02:47 +0000 |
| Subject: | note 1550 modified in function.ociexecute by sixd | ||
| References: | 1 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-161320@lists.php.net to get a copy of this message | ||
There seems to be some interesting behavior when using OCI_DEFAULT as the second parameter to
ociexecute... once the autocommit behavior is turned off for a connection, it remains off for the
life of that connection.
This tends to be a problem when using OCIPLogon, as a SQL statement may remain outstanding over the
life of many webpages.
This is most problematic when you're doing an update or insert, and a table remains locked
while that connection is waiting for a commit/rollback. Be sure to explicitly commit or rollback if
you use OCI_DEFAULT at any point.
--was--
There seems to be some interesting behavior when using OCI_DEFAULT as the second parameter to
ociexecute... once the autocommit behavior is turned off for a connection, it remains off for the
life of that connection.
This tends to be a problem when using OCIPLogon, as a SQL statement may remain outstanding over the
life of many webpages.
This is most problematic when you're doing an update or insert, and a table remains locked
while that connection is waiting for a commit/rollback. Be sure to explicitly commit or rollback if
you use OCI_DEFAULT at any point.
http://php.net/manual/en/function.ociexecute.php