Begins a database transaction.

Using this method is a preferred way of starting a transaction, using SQL statements to manage transaction state may lead to undefined behavior.

After the operation takes longer time than timeout, operation will be aborted. Note however, that it may not be feasible to abort the operation immediately.

Returned future can fail with:

• BeginTxException when general error occurs
• TimeoutException when maximum operation time has been exceeded

Commits a database transaction.

Using this method is a preferred way of committing a transaction, using SQL statements to manage transaction state may lead to undefined behavior.

After the operation takes longer time than timeout, operation will be aborted. Note however, that it may not be feasible to abort the operation immediately.

Returned future can fail with:

• CommmitTxException when general error occurs
• TimeoutException when maximum operation time has been exceeded

Releases the connection and underlying resources regardless of whether the connection is currently in use or not.

After calling this method no future operations on the instance are allowed.

Returned future can fail with:

• ConnectionReleaseException when general error occurs

Releases the connection and underlying resources.

Only idle connections can be released using this method. To forcibly release the connection use forceRelease method.

After calling this method no future operations on the instance are allowed.

Returned future can fail with:

• ConnectionReleaseException when general error occurs

Rolls back a database transaction.

Using this method is a preferred way of rolling back a transaction, using SQL statements to manage transaction state may lead to undefined behavior.

After the operation takes longer time than timeout, operation will be aborted. Note however, that it may not be feasible to abort the operation immediately.

Returned future can fail with:

• RollbackTxException when general error occurs
• TimeoutException when maximum operation time has been exceeded

Returns a ExecutableStatement instance bound to this connection that represents any parametrized SQL statement.

It's a shortcut for calling statement and then bind.

SqlWithParams parameter instance is meant to be constructed using sql string interpolator, for example:

import io.rdbc.sapi.Interpolators._
val x = 1
val y = 10
val stmt = conn.statement(sql"select * from table where colx > $x and coly < $y")

Throws:

• MixedParamTypesException when statement uses both positional and named parameters
• UncategorizedRdbcException when general error occurs
• MissingParamValException when some parameter value was not provided
• NoSuitableConverterFoundException when some parameter value's type is not convertible to a database type

Returns a ExecutableStatement instance bound to this connection that represents any parametrized SQL statement.

It's a shortcut for calling statement and then bind.

SqlWithParams parameter instance is meant to be constructed using sql string interpolator, for example:

import io.rdbc.sapi.Interpolators._
val x = 1
val y = 10
val stmt = conn.statement(sql"select * from table where colx > $x and coly < $y")

Throws:

• MixedParamTypesException when statement uses both positional and named parameters
• UncategorizedRdbcException when general error occurs
• MissingParamValException when some parameter value was not provided
• NoSuitableConverterFoundException when some parameter value's type is not convertible to a database type

Returns a Statement instance bound to this connection that represents any SQL statement.

For syntax of statement parametrization see a Connection documentation.

Throws:

• MixedParamTypesException when statement uses both positional and named parameters
• UncategorizedRdbcException when general error occurs

Returns a Statement instance bound to this connection that represents any SQL statement.

For syntax of statement parametrization see a Connection documentation.

Throws:

• MixedParamTypesException when statement uses both positional and named parameters
• UncategorizedRdbcException when general error occurs

Checks whether the connection is still usable.

If checking takes longer than timeout, connection is considered unusable.

Executes a function in a context of a transaction.

Executes a function (which can be passed as a code block) in a context of a transaction. Before the function is executed, transaction is started. After the function finishes, transaction is committed in case of a success and rolled back in case of a failure.

Because managing transaction state requires invoking functions that require specifying a timeout, this function requires an implicit timeout instance.