ibase_rollback_ret(3) [php man page]

IBASE_ROLLBACK_RET(3)							 1						     IBASE_ROLLBACK_RET(3)

ibase_rollback_ret - Roll back a transaction without closing it

SYNOPSIS

       bool ibase_rollback_ret NULL ([resource	$link_or_trans_identifier])

DESCRIPTION

	Rolls back a transaction without closing it.

PARAMETERS

	      o $link_or_trans_identifier
		-  If  called without an argument, this function rolls back the default transaction of the default link. If the argument is a con-
		nection identifier, the default transaction of the corresponding connection will be rolled back. If the argument is a  transaction
		identifier,  the  corresponding  transaction will be rolled back. The transaction context will be retained, so statements executed
		from within this transaction will not be invalidated.

RETURN VALUES

	Returns TRUE on success or FALSE on failure.

PHP Documentation Group 												     IBASE_ROLLBACK_RET(3)

OCI_COMMIT(3)															     OCI_COMMIT(3)

oci_commit - Commits the outstanding database transaction

SYNOPSIS

       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)