sigmasternchen/php-doc-en
1
0
Fork 0
mirror of https://github.com/sigmasternchen/php-doc-en synced 2025-03-16 00:48:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Expunge "you"

Browse source 
git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@291574 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Christopher Jones 2009-12-01 22:10:25 +00:00
parent c371744031
commit 6bd2ba8216
1 changed files with 18 additions and 19 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

37
reference/oci8/functions/oci-execute.xml
View file

@ -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 @@ for ($i = 1; $i <= oci_num_fields($stid); ++$i) {
&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 @@ for ($i = 1; $i <= oci_num_fields($stid); ++$i) {
</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>