Defining read-only and read-write transactions

solidDB Help : Programming : Managing transactions : Defining read-only and read-write transactions

To define a transaction to be read-only or read-write, use the SET TRANSACTION statement, see SET TRANSACTION (read/write level).

You can use the following statement in a HotStandBy (HSB) configuration to change the workload connection server from the secondary server to the primary server for one transaction:

SET TRANSACTION WRITE

For more information, see Load balancing in Transparent Connectivity.

Note To detect conflicts between transactions, use the SET TRANSACTION ISOLATION LEVEL statement to define the transaction with a REPEATABLE READ or SERIALIZABLE isolation level. For details, see Controlling transaction isolation levels.

Transactions must be ended with the COMMIT WORK or ROLLBACK WORK statements unless autocommit is used.

Go up to

Managing transactions