Impl

Resource that wraps a transaction block. It has the ability to specify a non-default isolation level and access mode.

Resource that wraps a transaction block. A transaction is begun before entering the use block, on success the block is executed, and on exit the following behavior holds.

• If the block exits normally, and the session transaction status is
  • Active, then the transaction will be committed.
  • Idle, then this means the user terminated the transaction explicitly inside the block and there is nothing to be done.
  • Error then this means the user encountered and handled an error but left the transaction in a failed state, and the transaction will be rolled back.
• If the block exits due to cancellation or an error and the session transaction status is not Idle then the transaction will be rolled back and any error will be re-raised.

Prepare if needed, then execute a parameterized command and yield a Completion.

Execute a non-parameterized command and yield a Completion. If you have parameters use prepare instead.

Transform a Query into a Pipe from inputs to outputs.

Transform a Command into a Pipe from inputs to Completions.

Prepares then caches an INSERT, UPDATE, or DELETE command that returns no rows. The resulting PreparedCommand can be executed multiple times with different arguments.

Prepare an INSERT, UPDATE, or DELETE command that returns no rows. The resulting PreparedCommand can be executed multiple times with different arguments.

Note: this method only exists to ease migration from Skunk 0.3 and prior. Use the non-resource variant instead.

Returns a stream that prepare if needed, then execute a parameterized query

Prepare if needed, then execute a parameterized query and returns a resource wrapping a cursor in the result set.

Prepare if needed, then execute a parameterized query and yield all results. If you wish to limit returned rows use prepare instead.

Execute a non-parameterized query and yield all results. If you have parameters or wish to limit returned rows use prepare instead.

Prepare if needed, then execute a parameterized query and yield at most one row, raising an exception if there are more.

Execute a non-parameterized query and yield at most one row, raising an exception if there are more. If you have parameters use prepare instead.

Prepares then caches a query, yielding a PreparedQuery which can be executed multiple times with different arguments.

Resource that prepares a query, yielding a PreparedQuery which can be executed multiple times with different arguments.

Note: this method only exists to ease migration from Skunk 0.3 and prior. Use the non-resource variant instead.

Prepare if needed, then execute a parameterized query and yield exactly one row, raising an exception if there are more or fewer.

Execute a non-parameterized query and yield exactly one row, raising an exception if there are more or fewer. If you have parameters use prepare instead.

Stream (possibly empty) of discrete values for the specified key, via parameters.

Signal representing the current state of all Postgres configuration variables announced to this session. These are sent after authentication and are updated asynchronously if the runtime environment changes. The current keys are as follows (with example values), but these may change with future releases so you should be prepared to handle unexpected ones.

Map(
 "application_name"            -> "",
 "client_encoding"             -> "UTF8",
 "DateStyle"                   -> "ISO, MDY",
 "integer_datetimes"           -> "on",       // cannot change after startup
 "IntervalStyle"               -> "postgres",
 "is_superuser"                -> "on",
 "server_encoding"             -> "UTF8",     // cannot change after startup
 "server_version"              -> "9.5.3",    // cannot change after startup
 "session_authorization"       -> "postgres",
 "standard_conforming_strings" -> "on",
 "TimeZone"                    -> "US/Pacific",
)

Signal representing the current transaction status.

A named asynchronous channel that can be used for inter-process communication.

Each session has access to the pool-wide cache of all statements that have been checked via the Describe protocol, which allows us to skip subsequent checks. Users can inspect and clear the cache through this accessor.

Each session has access to a cache of all statements that have been parsed by the Parse protocol, which allows us to skip a network round-trip. Users can inspect and clear the cache through this accessor.