Working on:
10. Lesson 1: Oracle JET 4.x - Lesson 1 - Part 9: Oracle JET Cookbook
(which I highly recommend)
and using the server loadavg code I wrote and have been adding gauges. All is great so far, and I'm loving JET, but have ran into an issue.
Here is the loadavg.js code:
/**
... (1 Reply)
Hi i'm trying to install centos ver 5 with apache server 1.3 and need to install
oracle client to connect from the php to oracle data base.
the problem is that evry package that i install needs some dependencis and
i coudent figure yet the right combination.
can any one help me to find... (3 Replies)
OCI_COMMIT(3)OCI_COMMIT(3)oci_commit - Commits the outstanding database transactionSYNOPSIS
bool oci_commit (resource $connection)
DESCRIPTION
Commits the outstanding transaction for the Oracle $connection. A commit ends the current transaction and makes permanent all changes. It
releases all locks held.
A transaction begins when the first SQL statement that changes data is executed with oci_execute(3) using the OCI_NO_AUTO_COMMIT flag.
Further data changes made by other statements become part of the same transaction. Data changes made in a transaction are temporary until
the transaction is committed or rolled back. Other users of the database will not see the changes until they are committed.
When inserting or updating data, using transactions is recommended for relational data consistency and for performance reasons.
PARAMETERS
o $connection
- An Oracle connection identifier, returned by oci_connect(3), oci_pconnect(3), or oci_new_connect(3).
RETURN VALUES
Returns TRUE on success or FALSE on failure.
EXAMPLES
Example #1
oci_commit(3) example
<?php
// Insert into several tables, rolling back the changes if an error occurs
$conn = oci_connect('hr', 'welcome', 'localhost/XE');
$stid = oci_parse($conn, "INSERT INTO mysalary (id, name) VALUES (1, 'Chris')");
// The OCI_NO_AUTO_COMMIT flag tells Oracle not to commit the INSERT immediately
// Use OCI_DEFAULT as the flag for PHP <= 5.3.1. The two flags are equivalent
$r = oci_execute($stid, OCI_NO_AUTO_COMMIT);
if (!$r) {
$e = oci_error($stid);
trigger_error(htmlentities($e['message']), E_USER_ERROR);
}
$stid = oci_parse($conn, 'INSERT INTO myschedule (startday) VALUES (12)');
$r = oci_execute($stid, OCI_NO_AUTO_COMMIT);
if (!$r) {
$e = oci_error($stid);
oci_rollback($conn); // rollback changes to both tables
trigger_error(htmlentities($e['message']), E_USER_ERROR);
}
// Commit the changes to both tables
$r = oci_commit($conn);
if (!$r) {
$e = oci_error($conn);
trigger_error(htmlentities($e['message']), E_USER_ERROR);
}
?>
NOTES
Note
Transactions are automatically rolled back when you close the connection, or when the script ends, whichever is soonest. You need
to explicitly call oci_commit(3) to commit the transaction.
Any call to oci_execute(3) that uses 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.
SEE ALSO oci_execute(3), oci_rollback(3).
PHP Documentation Group OCI_COMMIT(3)
