note 1550 modified in function.ociexecute by felipe

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-- <p>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. <p>This tends to be a problem when using OCIPLogon, as a SQL statement may remain outstanding over the life of many webpages. <p>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