svn: /phpdoc/en/trunk/reference/oci8/functions/ oci-execute.xml

From: Date: Tue, 01 Dec 2009 22:10:25 +0000
Subject: svn: /phpdoc/en/trunk/reference/oci8/functions/ oci-execute.xml
Groups: php.doc.cvs 
Request: Send a blank email to doc-cvs+get-5599@lists.php.net to get a copy of this message
sixd Tue, 01 Dec 2009 22:10:25 +0000 Revision: http://svn.php.net/viewvc?view=revision&revision=291574 Log: Expunge "you" Changed paths: U phpdoc/en/trunk/reference/oci8/functions/oci-execute.xml Modified: phpdoc/en/trunk/reference/oci8/functions/oci-execute.xml =================================================================== --- phpdoc/en/trunk/reference/oci8/functions/oci-execute.xml 2009-12-01 21:51:27 UTC (rev 291573) +++ phpdoc/en/trunk/reference/oci8/functions/oci-execute.xml 2009-12-01 22:10:25 UTC (rev 291574) @@ -92,11 +92,11 @@ </table> </para> <para> - When using <constant>OCI_NO_AUTO_COMMIT</constant> mode, you're - creating a transaction. Transactions are automatically rolled - back when the connection is closed, or when the script ends. - Explicitly call <function>oci_commit</function> to commit a - transaction, or <function>oci_rollback</function> to abort it. + Using <constant>OCI_NO_AUTO_COMMIT</constant> mode starts a + transaction. Transactions are automatically rolled back when + the connection is closed, or when the script ends. Explicitly + call <function>oci_commit</function> to commit a transaction, + or <function>oci_rollback</function> to abort it. </para> <para> When inserting or updating data, using transactions is @@ -104,15 +104,16 @@ reasons. </para> <para> - If you use <constant>OCI_NO_AUTO_COMMIT</constant> mode for any - statement including queries, and you do not subsequently - call <function>oci_commit</function> - or <function>oci_rollback</function>, then OCI8 will perform a - rollback at the end of the script even if no data was changed. - To avoid an unnecessary rollback, many scripts do not + If <constant>OCI_NO_AUTO_COMMIT</constant> mode is used for any + statement including queries, and + <function>oci_commit</function> + or <function>oci_rollback</function> is not subsequently + called, then OCI8 will perform a rollback at the end of the + script even if no data was changed. To avoid an unnecessary + rollback, many scripts do not use <constant>OCI_NO_AUTO_COMMIT</constant> mode for queries or PL/SQL. Be careful to ensure the appropriate transactional - consistency for your application when + consistency for the application when using <function>oci_execute</function> with different modes in the same script. </para> @@ -253,10 +254,9 @@ &reftitle.notes; <note> <para> - Transactions are automatically rolled back when you close the - connection, or when the script ends, whichever is soonest. You - need to explicitly call <function>oci_commit</function> to commit - the transaction. + Transactions are automatically rolled back when connections are + closed, or when the script ends, whichever is soonest. Explicitly + call <function>oci_commit</function> to commit a transaction. </para> <para> Any call to <function>oci_execute</function> that uses @@ -280,9 +280,8 @@ </note> <note> <para> - In PHP versions before 5.0.0 you must - use <function>ociexecute</function> instead. - &oci.name.compat.note; + In PHP versions before 5.0.0 use <function>ociexecute</function> + instead. &oci.name.compat.note; </para> </note> </refsect1>

« previous php.doc.cvs (#5599) next »