[PHP 5, PHP 7, PHP 8, PECL OCI8 >= 1.1.0]
oci_execute — Executes a statement
Description
oci_execute[resource $statement, int $mode = OCI_COMMIT_ON_SUCCESS]: bool
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
statementA valid OCI statement identifier.
modeAn optional second parameter can be one of the following constants:
Execution ModesOCI_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. Prior to PHP 5.3.2 [PECL OCI8 1.4] use OCI_DEFAULT which is equivalent to OCI_NO_AUTO_COMMIT.
|
Using 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 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 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 on success or
false on failure.
Examples
Example #1 oci_execute[] for queries
Results in "null", so performing an Identical test:
won't trap a problem, where as the Equal test [==] would:
So testing the result of a statement like oci_parse[] is important!