Neoview SQL Reference Manual (R2.3)

SET TRANSACTION MULTI COMMIT ON;
DELETE FROM persnl.employee
WHERE empnum = 23;
--- 1 row(s) deleted.
SET TRANSACTION MULTI COMMIT OFF;
Restrictions This are restrictions for the MULTI COMMIT option:
• Can be specified in the SET TRANSACTION statement along with other
transaction-mode. For example,
SET TRANSACTION ISOLATION LEVEL READ COMMITTED,
MULTI COMMIT ON,
READ WRITE;
• Not compatible with the READ UNCOMMITTED access option.
• Not compatible with READ ONLY access mode.
• Except for MULTI COMMIT, all of the SET TRANSACTION options are valid for the child
transactions and not the logical parent transaction.
• Not compatible with the NO ROLLBACK option set to ON.
This table shows the compatibility of MULTI COMMIT (ON and OFF) with other-SET
TRANSACTION modes:
OFFONMULTI COMMIT
X
X
X
X
--
X
X
X
READ UNCOMMITTED
READ COMMITTED
SERIALIZABLE
REPEATED READ
ISOLATION LEVEL ACCESS OPTION
X
X
--
X
READ ONLY
READ WRITE
ACCESS MODE
X
X
X
X
ON
OFF
AUTOCOMMIT
X
X
--
X
ON
OFF
NO ROLLBACK
X
X
X
X
X
X
TIMEOUT
0
RESET
AUTOABORT
X denotes compatible
-- denotes not compatible
Implicit Transactions
Most DML statements are transaction initiating—the system automatically initiates a transaction
when the statement begins executing.
The exceptions (statements that are not transaction initiating) are:
• COMMIT, FETCH, ROLLBACK, and SET TRANSACTION
• DML statements executing under READ UNCOMMITTED access
• EXECUTE or EXECUTE IMMEDIATE, which are transaction initiating only if the associated
statement is transaction-initiating
Explicit Transactions
You can issue an explicit BEGIN WORK even if the autocommit option is on. The autocommit
option is temporarily disabled until you explicitly issue COMMIT or ROLLBACK.
SET TRANSACTION Statement 173