Interface PoolBatchOptions

Wrap the batch in a transaction with the given locking behavior. Any error rolls the whole batch back and rejects.

Without this, the batch is fail-fast: it stops at the first error, but earlier operations may already have committed. Omitting it also leaves each statement in its own implicit transaction, so two reads in one batch can observe different snapshots if another connection commits in between.