commit statement

If it weren't, we would expect the first insert in the anonymous block to be preserved by the commit statement in the LOG_ERRORS procedure.

Issuing a COMMIT records all the work since the last COMMIT statement "for keeps" in the database.

In an environment in which many short concurrent transactions occur, by default each COMMIT statement triggers one log buffer flush to disk.

Like the CREATE statement, the DROP statement automatically executes a COMMIT statement before and after dropping the table.

A COMMIT statement guarantees all of the transaction's modifications are made a permanent part of the database.

As with bulk loads from a file, therefore, it is better to issue a COMMIT statement periodically, so the logical log files can be flushed.

Next, we insert another 8 rows using an anonymous block declared as an autonomous transaction, which contains a commit statement.

The commit statement restores the session data to the previous commit or rollback statement.

The Replication Server holds the changes until a COMMIT statement arrives.

The nesting level is decreased by a COMMIT statement.

In order for the policy changes to take effect, you must issue a COMMIT statement after invoking these procedures.

Be sure to issue the COMMIT statement frequently in your application.

A COMMIT statement controls the unit of work.