JdbcTransactor

Opens a connection, executes f, and closes the connection on return.

Opens a connection, applies the requested isolation level and read-only flag, disables auto-commit, executes f, commits on success, and rolls back on exception. Previous autoCommit, isolation level and readOnly flag are restored and the connection is closed after commit or rollback.

For SqlDialect.SQLite, transact runs with busy_timeout=5000 and IMMEDIATE — fromUrl and sqlite create SQLite connections with busy_timeout=5000 and transaction_mode=IMMEDIATE, and transact also configures any SQLite Connection (including pooled/wrapped via isWrapperFor/unwrap) per-transaction so queue workers reserve the write lock before the SELECT and wait on contention instead of failing the later DELETE with SQLITE_BUSY. See PR #1534 discussion_r3863454094; SQLite is single-consumer.

SQLite note: SQLite natively supports only SERIALIZABLE (its default). Other levels are accepted and applied via Connection.setTransactionIsolation so behaviour is uniform across dialects, but on SQLite the engine still behaves as serializable — the requested level may be ignored by the engine even though it is set on the connection.

Opens a connection, disables auto-commit, executes f, commits on success, and rolls back on exception. The connection is closed after commit or rollback. Preserves the driver's default isolation level and readOnly flag — does not force SERIALIZABLE — so callers that previously relied on the driver default (e.g. PostgreSQL READ_COMMITTED) are not unexpectedly upgraded. Use the two-arg overload to request a specific isolation level.

For SqlDialect.SQLite, transact runs with busy_timeout=5000 and IMMEDIATE — fromUrl and sqlite create SQLite connections with busy_timeout=5000 and transaction_mode=IMMEDIATE, and transact also configures any SQLite Connection (including pooled/wrapped via isWrapperFor/unwrap) per-transaction so queue workers reserve the write lock before the SELECT and wait on contention instead of failing the later DELETE with SQLITE_BUSY. See PR #1534 discussion_r3863454094; SQLite is single-consumer.