savepoint

Rolls back an explicit or implicit transaction to the beginning of the transaction, or to a savepoint inside the transaction.

When used, it specifies that this is meant to be a unique savepoint within the scope of the current transaction.

Rollback of a user-specified transaction to the last savepoint inside a transaction or to the beginning of a transaction.

In the case of an error, the transaction logic can specify that the transaction rollback to a savepoint.

The ROLLBACK statement would fail with the error: Rollback to savepoint disallowed on updating an old server in same transaction.

When a transaction rolls back to a savepoint, all non-hold cursors opened after that savepoint are closed.

Or, if the optional svpt1 identifier is not used, rollback happens to the last savepoint specified in the current transaction.

All locks acquired after the specified SAVEPOINT statement are retained until the end of the transaction.

Therefore, a savepoint name needs to be unique only in its scope of execution.

Any reference to a released savepoint is invalid and results in an error.

The example in Listing 3 demonstrates the usage of the SAVEPOINT statement in a transaction connected to the stores_demo database.

No transaction or savepoint of that name was found .

It sets a savepoint named newcustomer before inserting a new customer and a savepoint named neworder before adding the new customer's order.

Any rollbacks to the savepoint fail if any updates were made on an older server.

Setting another savepoint named newcustomer with the UNIQUE keyword results in an error.

SAVEPOINT statement defines an intermediate point during a transaction .

When used, the statement rolls back the part of the transaction that occurred after the savepoint identified by svpt1.

Method to roll back to the savepoint instead of rolling back to the start of the transaction.

The svpt1 identifier is the name of the savepoint.

The SAVEPOINT statement sets a savepoint at the current position in the transaction.

These square brackets indicate that the savepoint-name is optional.

Once a RELEASE SAVEPOINT statement has been executed or the transaction has ended, you can no longer use the savepoint.

Applications using other clients can use savepoints in IDS by sending the savepoint statements directly to the server.

The code sets a savepoint with the same newcustomer name as the savepoint set inside the procedure.

LSN of the most recent savepoint for the transaction in the database log.

This rollback undoes all the operations that were performed after the neworder savepoint was set.

The example in Listing 5 demonstrates the effect of a RELEASE SAVEPOINT statement.

You can undo all changes after that point using a ROLLBACK TO SAVEPOINT statement.

Review savepoint and mark options for transactions.

You can use all of the savepoint statements within stored procedures.

Any non-hold cursor opened after the specified SAVEPOINT statement is closed.

If a 547 error occurs, it rolls back to the savepoint and returns the number of items on hand to the calling process.

Explicitly release the given savepoint.

As described earlier, you set savepoints with the SAVEPOINT statement.

A new class, IfxSavepoint, implements the java. sql. Savepoint interface.

You create a savepoint using the SAVE TRANSACTION savepoint_name statement.

If there is an error, the program rolls back the transaction to the neworder savepoint.

Roll back to the given savepoint.

If you set a savepoint and update a pre-11. 50. xC3 subordinate server in a transaction, you receive a warning.

This section describes the SQL statements that were introduced with IDS 11. 50. xC3 to support savepoint processing.

You probably won't need to use savepoints frequently.

If a savepoint with the same name that is specified for svpt1 already exists in the same transaction, this statement generates an error.

Method, you can create a named or unnamed savepoint within the current transaction, and the method will return a

Rollback to Savepoint Causes Assertion and Errors

you create a savepoint using the save method , and then later call the

Design and Implementation of Savepoint Based on MVCC