Package-level declarations
Types
Common configuration for database connections to both Vert.x SqlClient and Exposed Database, currently supporting both TCP socket and Unix domain socket connections.
The main entry point for executing database operations using Vert.x SQL Client with Exposed SQL generation.
Configuration interface for DatabaseClient behavior.
A StatementPreparationExposedTransactionProvider that creates a new transaction for each call using an Exposed Database.
Note that this API is experimental and subject to change.
Marks APIs that are internal to the Exposed Vert.x SQL Client library.
Marks APIs that are experimental in the Exposed Vert.x SQL Client library.
Note that this API is experimental and subject to change.
A StatementPreparationExposedTransactionProvider that reuses a single JdbcTransaction for all SQL preparation calls.
Provider interface for creating and managing Exposed transactions used for SQL statement preparation.
Functions
See the DatabaseClientConfig interface for parameter descriptions.
An Exposed transaction is required if the FieldSet contains custom functions that depend on dialects.
This method has to be called within an ExposedTransaction.
To prevent SQL injection. Does not take into account quoted identifiers yet.
"single or no" means differently here from Iterable.singleOrNull.
Converts this socket connection config to an EvscConfig using the same config for both Vert.x SqlClient and Exposed Database. This is the simplest configuration for standard TCP/IP connections.
An alias of withSavepoint.
Currently only supported with PostgreSQL. A savepoint destroys one with the same name so be careful.
When using this function, it's recommended to name the lambda parameter the same as the outer receiver so that the outer DatabaseClient is shadowed, and so that you don't call the outer DatabaseClient without a transaction by accident.
When using this function, it's recommended to name the lambda parameter the same as the outer receiver so that the outer DatabaseClient is shadowed, and so that you don't call the outer DatabaseClient without a transaction by accident.
Polymorphic transaction function for DatabaseClient<*> with either Pool or SqlConnection as the DatabaseClient.vertxSqlClient.
Polymorphic transaction function for DatabaseClient<*> with either Pool or SqlConnection as the DatabaseClient.vertxSqlClient.
A variant of withTransaction that casts the SqlConnection to a specific subtype.
Polymorphic transaction function for DatabaseClient<*> with either Pool or SqlConnection as the DatabaseClient.vertxSqlClient.