1Z0-873 · Question #136
Which of the following statements are true with regard to savepoints in transactions?
The correct answer is A. Within a transaction, you can define multiple savepoints B. All savepoints must have unique identifiers C. You can rollback to any previous savepoint. E. If you rollback to a previous savepoint, all statements after this savepoint are rolled back and. If you want to roll back only part of a transaction, you can set a savepoint by using the SAVEPOINT statement: SAVEPOINT savepoint_name; Multiple savepoints can be set within a transaction. The SAVEPOINT statement sets a named transaction savepoint with a name of identifier. If…
Question
Which of the following statements are true with regard to savepoints in transactions?
Options
- AWithin a transaction, you can define multiple savepoints
- BAll savepoints must have unique identifiers
- CYou can rollback to any previous savepoint.
- DYou can rollback to only the latest savepoint.
- EIf you rollback to a previous savepoint, all statements after this savepoint are rolled back and
- FIf you rollback to a previous savepoint, you still can replay the statements after this savepoint.
How the community answered
(23 responses)- A83% (19)
- D4% (1)
- F13% (3)
Explanation
If you want to roll back only part of a transaction, you can set a savepoint by using the SAVEPOINT statement: SAVEPOINT savepoint_name; Multiple savepoints can be set within a transaction. The SAVEPOINT statement sets a named transaction savepoint with a name of identifier. If the current transaction has a savepoint with the same name, the old savepoint is deleted and a new The ROLLBACK TO SAVEPOINT statement rolls back a transaction to the named savepoint without terminating the transaction. Modifications that the current transaction made to rows after the savepoint was set are undone in the rollback, but InnoDB does not release the row locks that were stored in memory after the
Topics
Community Discussion
No community discussion yet for this question.