PHP: Hypertext Preprocessor (original) (raw)

oci_execute

(PHP 5, PHP 7, PHP 8, PECL OCI8 >= 1.1.0)

oci_execute — Executes a statement

Description

After execution, statements like INSERT will have data committed to the database by default. For statements like SELECT, execution performs the logic of the query. Query results can subsequently be fetched in PHP with functions like oci_fetch_array().

Each parsed statement may be executed multiple times, saving the cost of re-parsing. This is commonly used for INSERT statements when data is bound with oci_bind_by_name().

Parameters

statement

A valid OCI statement identifier.

mode

An optional second parameter can be one of the following constants:

Execution Modes

Constant	Description
OCI_COMMIT_ON_SUCCESS	Automatically commit all outstanding changes for this connection when the statement has succeeded. This is the default.
OCI_DESCRIBE_ONLY	Make query meta data available to functions like oci_field_name() but do not create a result set. Any subsequent fetch call such as oci_fetch_array() will fail.
OCI_NO_AUTO_COMMIT	Do not automatically commit changes.

Using [OCI_NO_AUTO_COMMIT](oci8.constants.php#constant.oci-no-auto-commit) mode starts or continues a transaction. Transactions are automatically rolled back when the connection is closed, or when the script ends. Explicitly call oci_commit() to commit a transaction, or oci_rollback() to abort it.

When inserting or updating data, using transactions is recommended for relational data consistency and for performance reasons.

If [OCI_NO_AUTO_COMMIT](oci8.constants.php#constant.oci-no-auto-commit) mode is used for any statement including queries, and oci_commit() or oci_rollback() 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 [OCI_NO_AUTO_COMMIT](oci8.constants.php#constant.oci-no-auto-commit) mode for queries or PL/SQL. Be careful to ensure the appropriate transactional consistency for the application when using oci_execute() with different modes in the same script.

Return Values

Returns [true](reserved.constants.php#constant.true) on success or [false](reserved.constants.php#constant.false) on failure.

Examples

Example #1 oci_execute() for queries

`<?php

$conn

= oci_connect('hr', 'welcome', 'localhost/XE');$stid = oci_parse($conn, 'SELECT * FROM employees');
oci_execute($stid);

echo

\n";
while ($row = oci_fetch_array($stid, OCI_ASSOC+OCI_RETURN_NULLS)) {
echo "\n";
foreach ($row as $item) {
echo " \n";
}
echo "\n";
}
echo "

" . ($item !== null ? htmlentities($item, ENT_QUOTES) : " ") . "

\n";?>`

Example #2 oci_execute() without specifying a mode example

<?php// Before running, create the table: // CREATE TABLE MYTABLE (col1 NUMBER);$conn = oci_connect('hr', 'welcome', 'localhost/XE');$stid = oci_parse($conn, 'INSERT INTO mytab (col1) VALUES (123)');oci_execute($stid); // The row is committed and immediately visible to other users?>

Example #3 oci_execute() with [OCI_NO_AUTO_COMMIT](oci8.constants.php#constant.oci-no-auto-commit) example

<?php// Before running, create the table: // CREATE TABLE MYTABLE (col1 NUMBER);$conn = oci_connect('hr', 'welcome', 'localhost/XE');$stid = oci_parse($conn, 'INSERT INTO mytab (col1) VALUES (:bv)'); oci_bind_by_name($stid, ':bv', $i, 10); for ($i = 1; <math xmlns="http://www.w3.org/1998/Math/MathML"><semantics><mrow><mi>i</mi><mo><</mo><mo>=</mo><mn>5</mn><mo separator="true">;</mo><mo>+</mo><mo>+</mo></mrow><annotation encoding="application/x-tex">i <= 5; ++</annotation></semantics></math>i<=5;++i) { oci_execute($stid, OCI_NO_AUTO_COMMIT); } oci_commit($conn); // commits all new values: 1, 2, 3, 4, 5?>

Example #4 oci_execute() with different commit modes example

<?php// Before running, create the table: // CREATE TABLE MYTABLE (col1 NUMBER);$conn = oci_connect('hr', 'welcome', 'localhost/XE');$stid = oci_parse($conn, 'INSERT INTO mytab (col1) VALUES (123)'); oci_execute($stid, OCI_NO_AUTO_COMMIT); // data not committed$stid = oci_parse($conn, 'INSERT INTO mytab (col1) VALUES (456)'); oci_execute($stid); // commits both 123 and 456 values?>

Example #5 oci_execute() with[OCI_DESCRIBE_ONLY](oci8.constants.php#constant.oci-describe-only) example

`<?php

$conn

= oci_connect('hr', 'welcome', 'localhost/XE');$stid = oci_parse($conn, 'SELECT * FROM locations');
oci_execute($s, OCI_DESCRIBE_ONLY);
for ($i = 1; i<=ocinumfields(i <= oci_num_fields(i<=ocinumfields(stid); ++$i) {
echo oci_field_name($stid, $i) . "
\n";
}?>`

Notes

Note:

Transactions are automatically rolled back when connections are closed, or when the script ends, whichever is soonest. Explicitly call oci_commit() to commit a transaction.

Any call to oci_execute() that uses**[OCI_COMMIT_ON_SUCCESS](oci8.constants.php#constant.oci-commit-on-success)** mode explicitly or by default will commit any previous uncommitted transaction.

Any Oracle DDL statement such as CREATE or DROP will automatically commit any uncommitted transaction.

Note:

Because the oci_execute() function generally sends the statement to the database, oci_execute() can identify some statement syntax errors that the lightweight, local oci_parse() function does not.

Found A Problem?

tower98 at gmail dot com ¶

14 years ago

`Notice (PHP 5.2.12-pl0-gentoo):
You can parse empty query, you can execute empty query (returns true), but you cannot fetch data from empty query. So, if you provide query as variable, make sure it isn't empty.

q=ociparse(q = oci_parse(q=ociparse(c, ""); if($q != false){ // parsing empty query != false if(oci_execute($q){ // executing empty query != false if(oci_fetch_all($q, $data, 0, -1, OCI_FETCHSTATEMENT_BY_ROW) == false){ // but fetching executed empty query results in error (ORA-24338: statement handle not executed) e=ocierror(e = oci_error(e=ocierror(q); echo $e['message']; } } else{ e=ocierror(e = oci_error(e=ocierror(q); echo $e['message']; } } else{ e=ocierror(e = oci_error(e=ocierror(link); echo $e['message']; } ?>