DSLContext (jOOQ 3.10.8 API)

All Superinterfaces:

java.lang.AutoCloseable, Scope

All Known Implementing Classes:

DefaultDSLContext
```
public interface DSLContext
extends Scope, java.lang.AutoCloseable
```
A contextual DSL providing "attached" implementations to the org.jooq interfaces.
Apart from the DSL, this contextual DSL is the main entry point for client code, to access jOOQ classes and functionality that are related to Query execution. Unlike objects created through the DSL type, objects created from a DSLContext will be "attached" to the DSLContext's Scope.configuration(), such that they can be executed immediately in a fluent style. An example is given here:
```
 DSLContext create = DSL.using(connection, dialect);

 // Immediately fetch results after constructing a query
 create.selectFrom(MY_TABLE).where(MY_TABLE.ID.eq(1)).fetch();

 // The above is equivalent to this "non-fluent" style
 create.fetch(DSL.selectFrom(MY_TABLE).where(MY_TABLE.ID.eq(1)));
 
```
The DSL provides convenient constructors to create a Configuration, which will be shared among all Query objects thus created. Optionally, you can pass a reusable Configuration to the DSL.using(Configuration) constructor. Please consider thread-safety concerns documented in Configuration, should you want to reuse the same Configuration instance in various threads and / or transactions.
Author:

Lukas Eder

See Also:

DSL, Configuration

Method Summary

All Methods Instance Methods Abstract Methods Deprecated Methods
Modifier and Type	Method and Description
`AlterIndexStep`	`alterIndex(Index index)` Create a new DSL `ALTER INDEX` statement.
`AlterIndexStep`	`alterIndex(Name index)` Create a new DSL `ALTER INDEX` statement.
`AlterIndexStep`	`alterIndex(java.lang.String index)` Create a new DSL `ALTER INDEX` statement.
`AlterIndexStep`	`alterIndexIfExists(Index index)` Create a new DSL `ALTER INDEX` statement.
`AlterIndexStep`	`alterIndexIfExists(Name index)` Create a new DSL `ALTER INDEX` statement.
`AlterIndexStep`	`alterIndexIfExists(java.lang.String index)` Create a new DSL `ALTER INDEX` statement.
`AlterSchemaStep`	`alterSchema(Name schema)` Create a new DSL `ALTER SCHEMA` statement.
`AlterSchemaStep`	`alterSchema(Schema schema)` Create a new DSL `ALTER SCHEMA` statement.
`AlterSchemaStep`	`alterSchema(java.lang.String schema)` Create a new DSL `ALTER SCHEMA` statement.
`AlterSchemaStep`	`alterSchemaIfExists(Name schema)` Create a new DSL `ALTER SCHEMA` statement.
`AlterSchemaStep`	`alterSchemaIfExists(Schema schema)` Create a new DSL `ALTER SCHEMA` statement.
`AlterSchemaStep`	`alterSchemaIfExists(java.lang.String schema)` Create a new DSL `ALTER SCHEMA` statement.
`AlterSequenceStep<java.math.BigInteger>`	`alterSequence(Name sequence)` Create a new DSL `ALTER SEQUENCE` statement.
`<T extends java.lang.Number> AlterSequenceStep<T>`	`alterSequence(Sequence<T> sequence)` Create a new DSL `ALTER SEQUENCE` statement.
`AlterSequenceStep<java.math.BigInteger>`	`alterSequence(java.lang.String sequence)` Create a new DSL `ALTER SEQUENCE` statement.
`AlterSequenceStep<java.math.BigInteger>`	`alterSequenceIfExists(Name sequence)` Create a new DSL `ALTER SEQUENCE` statement.
`<T extends java.lang.Number> AlterSequenceStep<T>`	`alterSequenceIfExists(Sequence<T> sequence)` Create a new DSL `ALTER SEQUENCE` statement.
`AlterSequenceStep<java.math.BigInteger>`	`alterSequenceIfExists(java.lang.String sequence)` Create a new DSL `ALTER SEQUENCE` statement.
`AlterTableStep`	`alterTable(Name table)` Create a new DSL `ALTER TABLE` statement.
`AlterTableStep`	`alterTable(java.lang.String table)` Create a new DSL `ALTER TABLE` statement.
`AlterTableStep`	`alterTable(Table<?> table)` Create a new DSL `ALTER TABLE` statement.
`AlterTableStep`	`alterTableIfExists(Name table)` Create a new DSL `ALTER TABLE` statement.
`AlterTableStep`	`alterTableIfExists(java.lang.String table)` Create a new DSL `ALTER TABLE` statement.
`AlterTableStep`	`alterTableIfExists(Table<?> table)` Create a new DSL `ALTER TABLE` statement.
`AlterViewStep`	`alterView(Name view)` Create a new DSL `ALTER VIEW` statement.
`AlterViewStep`	`alterView(java.lang.String view)` Create a new DSL `ALTER VIEW` statement.
`AlterViewStep`	`alterView(Table<?> view)` Create a new DSL `ALTER VIEW` statement.
`AlterViewStep`	`alterViewIfExists(Name view)` Create a new DSL `ALTER VIEW` statement.
`AlterViewStep`	`alterViewIfExists(java.lang.String view)` Create a new DSL `ALTER VIEW` statement.
`AlterViewStep`	`alterViewIfExists(Table<?> view)` Create a new DSL `ALTER VIEW` statement.
`void`	`attach(Attachable... attachables)` Attach this `DSLContext`'s underlying `Scope.configuration()` to some attachables.
`void`	`attach(java.util.Collection<? extends Attachable> attachables)` Attach this `DSLContext`'s underlying `Scope.configuration()` to some attachables.
`Batch`	`batch(java.util.Collection<? extends Query> queries)` Create a batch statement to execute a set of queries in batch mode (without bind values).
`Batch`	`batch(Queries queries)` Create a batch statement to execute a set of queries in batch mode (without bind values).
`Batch`	`batch(Query... queries)` Create a batch statement to execute a set of queries in batch mode (without bind values).
`BatchBindStep`	`batch(Query query)` Create a batch statement to execute a set of queries in batch mode (with bind values).
`Batch`	`batch(Query query, java.lang.Object[]... bindings)` Create a batch statement to execute a set of queries in batch mode (with bind values).
`Batch`	`batch(java.lang.String... queries)` Create a batch statement to execute a set of queries in batch mode (without bind values).
`BatchBindStep`	`batch(java.lang.String sql)` Create a batch statement to execute a set of queries in batch mode (with bind values).
`Batch`	`batch(java.lang.String sql, java.lang.Object[]... bindings)` Create a batch statement to execute a set of queries in batch mode (with bind values).
`Batch`	`batchDelete(java.util.Collection<? extends UpdatableRecord<?>> records)` Create a batch statement to execute a set of `DELETE` queries in batch mode (with bind values) according to `UpdatableRecord.delete()` sematics.
`Batch`	`batchDelete(UpdatableRecord<?>... records)` Create a batch statement to execute a set of `DELETE` queries in batch mode (with bind values) according to `UpdatableRecord.delete()` sematics.
`Batch`	`batchInsert(java.util.Collection<? extends TableRecord<?>> records)` Create a batch statement to execute a set of `INSERT` queries in batch mode (with bind values) according to `TableRecord.insert()` semantics.
`Batch`	`batchInsert(TableRecord<?>... records)` Create a batch statement to execute a set of `INSERT` queries in batch mode (with bind values) according to `TableRecord.insert()` semantics.
`Batch`	`batchStore(java.util.Collection<? extends UpdatableRecord<?>> records)` Create a batch statement to execute a set of `INSERT` and `UPDATE` queries in batch mode (with bind values) according to `UpdatableRecord.store()` semantics.
`Batch`	`batchStore(UpdatableRecord<?>... records)` Create a batch statement to execute a set of `INSERT` and `UPDATE` queries in batch mode (with bind values) according to `UpdatableRecord.store()` semantics.
`Batch`	`batchUpdate(java.util.Collection<? extends UpdatableRecord<?>> records)` Create a batch statement to execute a set of `UPDATE` queries in batch mode (with bind values) according to `UpdatableRecord.update()` semantics.
`Batch`	`batchUpdate(UpdatableRecord<?>... records)` Create a batch statement to execute a set of `UPDATE` queries in batch mode (with bind values) according to `UpdatableRecord.update()` semantics.
`int`	`bind(QueryPart part, java.sql.PreparedStatement stmt)` Deprecated. - [#2662] - 3.2.0 - Do not reuse this method. It will be removed with jOOQ 4.0
`BindContext`	`bindContext(java.sql.PreparedStatement stmt)` Deprecated. - [#6280] - 3.10 - Do not reuse this method. It will be completely internal with jOOQ 4.0
`void`	`close()` Close the underlying resources, if any resources have been allocated when constructing this `DSLContext`.
`void`	`connection(ConnectionRunnable runnable)` Run a `ConnectionRunnable` in the context of this `DSLContext`'s underlying `Scope.configuration()`'s `Configuration.connectionProvider()`.
`<T> T`	`connectionResult(ConnectionCallable<T> callable)` Run a `ConnectionCallable` in the context of this `DSLContext`'s underlying `Scope.configuration()`'s `Configuration.connectionProvider()`.
`CreateTableAsStep<Record>`	`createGlobalTemporaryTable(Name table)` Create a new DSL `CREATE GLOBAL TEMPORARY TABLE` statement.
`CreateTableAsStep<Record>`	`createGlobalTemporaryTable(java.lang.String table)` Create a new DSL `CREATE GLOBAL TEMPORARY TABLE` statement.
`CreateTableAsStep<Record>`	`createGlobalTemporaryTable(Table<?> table)` Create a new DSL `CREATE GLOBAL TEMPORARY TABLE` statement.
`CreateIndexStep`	`createIndex(Index index)` Create a new DSL `CREATE INDEX` statement.
`CreateIndexStep`	`createIndex(Name index)` Create a new DSL `CREATE INDEX` statement.
`CreateIndexStep`	`createIndex(java.lang.String index)` Create a new DSL `CREATE INDEX` statement.
`CreateIndexStep`	`createIndexIfNotExists(Index index)` Create a new DSL `CREATE INDEX IF NOT EXISTS` statement.
`CreateIndexStep`	`createIndexIfNotExists(Name index)` Create a new DSL `CREATE INDEX IF NOT EXISTS` statement.
`CreateIndexStep`	`createIndexIfNotExists(java.lang.String index)` Create a new DSL `CREATE INDEX IF NOT EXISTS` statement.
`CreateSchemaFinalStep`	`createSchema(Name schema)` Create a new DSL `CREATE SCHEMA` statement.
`CreateSchemaFinalStep`	`createSchema(Schema schema)` Create a new DSL `CREATE SCHEMA` statement.
`CreateSchemaFinalStep`	`createSchema(java.lang.String schema)` Create a new DSL `CREATE SCHEMA` statement.
`CreateSchemaFinalStep`	`createSchemaIfNotExists(Name schema)` Create a new DSL `CREATE SCHEMA` statement.
`CreateSchemaFinalStep`	`createSchemaIfNotExists(Schema schema)` Create a new DSL `CREATE SCHEMA` statement.
`CreateSchemaFinalStep`	`createSchemaIfNotExists(java.lang.String schema)` Create a new DSL `CREATE SCHEMA` statement.
`CreateSequenceFinalStep`	`createSequence(Name sequence)` Create a new DSL `CREATE SEQUENCE` statement.
`CreateSequenceFinalStep`	`createSequence(Sequence<?> sequence)` Create a new DSL `CREATE SEQUENCE` statement.
`CreateSequenceFinalStep`	`createSequence(java.lang.String sequence)` Create a new DSL `CREATE SEQUENCE` statement.
`CreateSequenceFinalStep`	`createSequenceIfNotExists(Name sequence)` Create a new DSL `CREATE SEQUENCE` statement.
`CreateSequenceFinalStep`	`createSequenceIfNotExists(Sequence<?> sequence)` Create a new DSL `CREATE SEQUENCE` statement.
`CreateSequenceFinalStep`	`createSequenceIfNotExists(java.lang.String sequence)` Create a new DSL `CREATE SEQUENCE` statement.
`CreateTableAsStep<Record>`	`createTable(Name table)` Create a new DSL `CREATE TABLE` statement.
`CreateTableAsStep<Record>`	`createTable(java.lang.String table)` Create a new DSL `CREATE TABLE` statement.
`CreateTableAsStep<Record>`	`createTable(Table<?> table)` Create a new DSL `CREATE TABLE` statement.
`CreateTableAsStep<Record>`	`createTableIfNotExists(Name table)` Create a new DSL `CREATE TABLE` statement.
`CreateTableAsStep<Record>`	`createTableIfNotExists(java.lang.String table)` Create a new DSL `CREATE TABLE` statement.
`CreateTableAsStep<Record>`	`createTableIfNotExists(Table<?> table)` Create a new DSL `CREATE TABLE` statement.
`CreateTableAsStep<Record>`	`createTemporaryTable(Name table)` Create a new DSL `CREATE TEMPORARY TABLE` statement.
`CreateTableAsStep<Record>`	`createTemporaryTable(java.lang.String table)` Create a new DSL `CREATE TEMPORARY TABLE` statement.
`CreateTableAsStep<Record>`	`createTemporaryTable(Table<?> table)` Create a new DSL `CREATE TEMPORARY TABLE` statement.
`CreateIndexStep`	`createUniqueIndex(Index index)` Create a new DSL `CREATE UNIQUE INDEX` statement.
`CreateIndexStep`	`createUniqueIndex(Name index)` Create a new DSL `CREATE UNIQUE INDEX` statement.
`CreateIndexStep`	`createUniqueIndex(java.lang.String index)` Create a new DSL `CREATE UNIQUE INDEX` statement.
`CreateIndexStep`	`createUniqueIndexIfNotExists(Index index)` Create a new DSL `CREATE UNIQUE INDEX` statement.
`CreateIndexStep`	`createUniqueIndexIfNotExists(Name index)` Create a new DSL `CREATE UNIQUE INDEX` statement.
`CreateIndexStep`	`createUniqueIndexIfNotExists(java.lang.String index)` Create a new DSL `CREATE UNIQUE INDEX` statement.
`CreateViewAsStep<Record>`	`createView(Name view, java.util.function.BiFunction<? super Field<?>,? super java.lang.Integer,? extends Name> fieldNameFunction)` Create a new DSL `CREATE VIEW` statement.
`CreateViewAsStep<Record>`	`createView(Name view, java.util.function.Function<? super Field<?>,? extends Name> fieldNameFunction)` Create a new DSL `CREATE VIEW` statement.
`CreateViewAsStep<Record>`	`createView(Name view, Name... fields)` Create a new DSL `CREATE VIEW` statement.
`CreateViewAsStep<Record>`	`createView(java.lang.String view, java.util.function.BiFunction<? super Field<?>,? super java.lang.Integer,? extends java.lang.String> fieldNameFunction)` Create a new DSL `CREATE VIEW` statement.
`CreateViewAsStep<Record>`	`createView(java.lang.String view, java.util.function.Function<? super Field<?>,? extends java.lang.String> fieldNameFunction)` Create a new DSL `CREATE VIEW` statement.
`CreateViewAsStep<Record>`	`createView(java.lang.String view, java.lang.String... fields)` Create a new DSL `CREATE VIEW` statement.
`CreateViewAsStep<Record>`	`createView(Table<?> view, java.util.function.BiFunction<? super Field<?>,? super java.lang.Integer,? extends Field<?>> fieldNameFunction)` Create a new DSL `CREATE VIEW` statement.
`CreateViewAsStep<Record>`	`createView(Table<?> view, Field<?>... fields)` Create a new DSL `CREATE VIEW` statement.
`CreateViewAsStep<Record>`	`createView(Table<?> view, java.util.function.Function<? super Field<?>,? extends Field<?>> fieldNameFunction)` Create a new DSL `CREATE VIEW` statement.
`CreateViewAsStep<Record>`	`createViewIfNotExists(Name view, java.util.function.BiFunction<? super Field<?>,? super java.lang.Integer,? extends Name> fieldNameFunction)` Create a new DSL `CREATE VIEW` statement.
`CreateViewAsStep<Record>`	`createViewIfNotExists(Name view, java.util.function.Function<? super Field<?>,? extends Name> fieldNameFunction)` Create a new DSL `CREATE VIEW` statement.
`CreateViewAsStep<Record>`	`createViewIfNotExists(Name view, Name... fields)` Create a new DSL `CREATE VIEW` statement.
`CreateViewAsStep<Record>`	`createViewIfNotExists(java.lang.String view, java.util.function.BiFunction<? super Field<?>,? super java.lang.Integer,? extends java.lang.String> fieldNameFunction)` Create a new DSL `CREATE VIEW` statement.
`CreateViewAsStep<Record>`	`createViewIfNotExists(java.lang.String view, java.util.function.Function<? super Field<?>,? extends java.lang.String> fieldNameFunction)` Create a new DSL `CREATE VIEW` statement.
`CreateViewAsStep<Record>`	`createViewIfNotExists(java.lang.String view, java.lang.String... fields)` Create a new DSL `CREATE VIEW` statement.
`CreateViewAsStep<Record>`	`createViewIfNotExists(Table<?> view, java.util.function.BiFunction<? super Field<?>,? super java.lang.Integer,? extends Field<?>> fieldNameFunction)` Create a new DSL `CREATE VIEW` statement.
`CreateViewAsStep<Record>`	`createViewIfNotExists(Table<?> view, Field<?>... fields)` Create a new DSL `CREATE VIEW` statement.
`CreateViewAsStep<Record>`	`createViewIfNotExists(Table<?> view, java.util.function.Function<? super Field<?>,? extends Field<?>> fieldNameFunction)` Create a new DSL `CREATE VIEW` statement.
`java.math.BigInteger`	`currval(Name sequence)` Convenience method to fetch the CURRVAL for a sequence directly from this `DSLContext`'s underlying JDBC `Connection`.
`<T extends java.lang.Number> T`	`currval(Sequence<T> sequence)` Convenience method to fetch the CURRVAL for a sequence directly from this `DSLContext`'s underlying JDBC `Connection`.
`java.math.BigInteger`	`currval(java.lang.String sequence)` Convenience method to fetch the CURRVAL for a sequence directly from this `DSLContext`'s underlying JDBC `Connection`.
`Queries`	`ddl(Catalog catalog)` Generate the complete creation script for the entire catalog.
`Queries`	`ddl(Catalog schema, DDLFlag... flags)` Generate a partial creation script for the entire catalog.
`Queries`	`ddl(Schema schema)` Generate the complete creation script for the entire schema.
`Queries`	`ddl(Schema schema, DDLFlag... flags)` Generate a partial creation script for the entire schema.
`Queries`	`ddl(Table<?> table)` Generate the complete creation script for a table.
`Queries`	`ddl(Table<?> table, DDLFlag... flags)` Generate a partial creation script for a table.
`<R extends Record> DeleteWhereStep<R>`	`delete(Table<R> table)` Create a new DSL delete statement.
`<R extends Record> DeleteWhereStep<R>`	`deleteFrom(Table<R> table)` Create a new DSL delete statement.
`<R extends Record> DeleteQuery<R>`	`deleteQuery(Table<R> table)` Create a new `DeleteQuery`
`DropIndexOnStep`	`dropIndex(Index index)` Create a new DSL `DROP INDEX` statement.
`DropIndexOnStep`	`dropIndex(Name index)` Create a new DSL `DROP INDEX` statement.
`DropIndexOnStep`	`dropIndex(java.lang.String index)` Create a new DSL `DROP INDEX` statement.
`DropIndexOnStep`	`dropIndexIfExists(Index index)` Create a new DSL `DROP INDEX IF EXISTS` statement.
`DropIndexOnStep`	`dropIndexIfExists(Name index)` Create a new DSL `DROP INDEX IF EXISTS` statement.
`DropIndexOnStep`	`dropIndexIfExists(java.lang.String index)` Create a new DSL `DROP INDEX IF EXISTS` statement.
`DropSchemaStep`	`dropSchema(Name schema)` Create a new DSL `DROP SCHEMA` statement.
`DropSchemaStep`	`dropSchema(Schema schema)` Create a new DSL `DROP SCHEMA` statement.
`DropSchemaStep`	`dropSchema(java.lang.String schema)` Create a new DSL `DROP SCHEMA` statement.
`DropSchemaStep`	`dropSchemaIfExists(Name schema)` Create a new DSL `DROP SCHEMA` statement.
`DropSchemaStep`	`dropSchemaIfExists(Schema schema)` Create a new DSL `DROP SCHEMA` statement.
`DropSchemaStep`	`dropSchemaIfExists(java.lang.String schema)` Create a new DSL `DROP SCHEMA` statement.
`DropSequenceFinalStep`	`dropSequence(Name sequence)` Create a new DSL `DROP SEQUENCE` statement.
`DropSequenceFinalStep`	`dropSequence(Sequence<?> sequence)` Create a new DSL `DROP SEQUENCE` statement.
`DropSequenceFinalStep`	`dropSequence(java.lang.String sequence)` Create a new DSL `DROP SEQUENCE` statement.
`DropSequenceFinalStep`	`dropSequenceIfExists(Name sequence)` Create a new DSL `DROP SEQUENCE IF EXISTS` statement.
`DropSequenceFinalStep`	`dropSequenceIfExists(Sequence<?> sequence)` Create a new DSL `DROP SEQUENCE IF EXISTS` statement.
`DropSequenceFinalStep`	`dropSequenceIfExists(java.lang.String sequence)` Create a new DSL `DROP SEQUENCE IF EXISTS` statement.
`DropTableStep`	`dropTable(Name table)` Create a new DSL `DROP TABLE` statement.
`DropTableStep`	`dropTable(java.lang.String table)` Create a new DSL `DROP TABLE` statement.
`DropTableStep`	`dropTable(Table<?> table)` Create a new DSL `DROP TABLE` statement.
`DropTableStep`	`dropTableIfExists(Name table)` Create a new DSL `DROP TABLE IF EXISTS` statement.
`DropTableStep`	`dropTableIfExists(java.lang.String table)` Create a new DSL `DROP TABLE IF EXISTS` statement.
`DropTableStep`	`dropTableIfExists(Table<?> table)` Create a new DSL `DROP TABLE IF EXISTS` statement.
`DropViewFinalStep`	`dropView(Name view)` Create a new DSL `DROP VIEW` statement.
`DropViewFinalStep`	`dropView(java.lang.String view)` Create a new DSL `DROP VIEW` statement.
`DropViewFinalStep`	`dropView(Table<?> view)` Create a new DSL `DROP VIEW` statement.
`DropViewFinalStep`	`dropViewIfExists(Name view)` Create a new DSL `DROP VIEW IF EXISTS` statement.
`DropViewFinalStep`	`dropViewIfExists(java.lang.String view)` Create a new DSL `DROP VIEW IF EXISTS` statement.
`DropViewFinalStep`	`dropViewIfExists(Table<?> view)` Create a new DSL `DROP VIEW IF EXISTS` statement.
`int`	`execute(Query query)` Execute a `Query` in the context of this `DSLContext`.
`int`	`execute(SQL sql)` Execute a query holding plain SQL.
`int`	`execute(java.lang.String sql)` Execute a query holding plain SQL.
`int`	`execute(java.lang.String sql, java.lang.Object... bindings)` Execute a new query holding plain SQL.
`int`	`execute(java.lang.String sql, QueryPart... parts)` Execute a new query holding plain SQL.
`<R extends UpdatableRecord<R>> int`	`executeDelete(R record)` Delete a record from a table.
`<R extends TableRecord<R>,T> int`	`executeDelete(R record, Condition condition)` Delete a record from a table.
`<R extends TableRecord<R>> int`	`executeInsert(R record)` Insert one record.
`<R extends UpdatableRecord<R>> int`	`executeUpdate(R record)` Update a table.
`<R extends TableRecord<R>,T> int`	`executeUpdate(R record, Condition condition)` Update a table.
`java.util.List<java.lang.Object>`	`extractBindValues(QueryPart part)` Retrieve the bind values that will be bound by a given `QueryPart`.
`Param<?>`	`extractParam(QueryPart part, java.lang.String name)` Get a named parameter from a `QueryPart`, provided its name.
`java.util.Map<java.lang.String,Param<?>>`	`extractParams(QueryPart part)` Get a `Map` of named parameters.
`<R extends Record> Result<R>`	`fetch(ResultQuery<R> query)` Execute a `ResultQuery` in the context of this `DSLContext` and return results.
`Result<Record>`	`fetch(java.sql.ResultSet rs)` Fetch all data from a JDBC `ResultSet` and transform it to a jOOQ `Result`.
`Result<Record>`	`fetch(java.sql.ResultSet rs, java.lang.Class<?>... types)` Fetch all data from a JDBC `ResultSet` and transform it to a jOOQ `Result`.
`Result<Record>`	`fetch(java.sql.ResultSet rs, DataType<?>... types)` Fetch all data from a JDBC `ResultSet` and transform it to a jOOQ `Result`.
`Result<Record>`	`fetch(java.sql.ResultSet rs, Field<?>... fields)` Fetch all data from a JDBC `ResultSet` and transform it to a jOOQ `Result`.
`Result<Record>`	`fetch(SQL sql)` Execute a new query holding plain SQL.
`Result<Record>`	`fetch(java.lang.String sql)` Execute a new query holding plain SQL.
`Result<Record>`	`fetch(java.lang.String sql, java.lang.Object... bindings)` Execute a new query holding plain SQL.
`Result<Record>`	`fetch(java.lang.String sql, QueryPart... parts)` Execute a new query holding plain SQL.
`<R extends Record> Result<R>`	`fetch(Table<R> table)` Execute and return all records for `SELECT * FROM [table]`.
`<R extends Record> Result<R>`	`fetch(Table<R> table, Condition condition)` Execute and return all records for `SELECT * FROM [table] WHERE [condition]` .
`<R extends Record> R`	`fetchAny(Table<R> table)` Execute and return zero or one record for `SELECT * FROM [table] LIMIT 1`.
`<R extends Record> R`	`fetchAny(Table<R> table, Condition condition)` Execute and return zero or one record for `SELECT * FROM [table] WHERE [condition] LIMIT 1`.
`<R extends Record> java.util.concurrent.CompletionStage<Result<R>>`	`fetchAsync(java.util.concurrent.Executor executor, ResultQuery<R> query)` Fetch results in a new `CompletionStage` that is asynchronously completed by a task running in the given executor.
`java.util.concurrent.CompletionStage<Result<Record>>`	`fetchAsync(java.util.concurrent.Executor executor, java.sql.ResultSet rs)` Fetch results in a new `CompletionStage` that is asynchronously completed by a task running in the given executor.
`java.util.concurrent.CompletionStage<Result<Record>>`	`fetchAsync(java.util.concurrent.Executor executor, java.sql.ResultSet rs, java.lang.Class<?>... types)` Fetch results in a new `CompletionStage` that is asynchronously completed by a task running in the given executor.
`java.util.concurrent.CompletionStage<Result<Record>>`	`fetchAsync(java.util.concurrent.Executor executor, java.sql.ResultSet rs, DataType<?>... types)` Fetch results in a new `CompletionStage` that is asynchronously completed by a task running in the given executor.
`java.util.concurrent.CompletionStage<Result<Record>>`	`fetchAsync(java.util.concurrent.Executor executor, java.sql.ResultSet rs, Field<?>... fields)` Fetch results in a new `CompletionStage` that is asynchronously completed by a task running in the given executor.
`java.util.concurrent.CompletionStage<Result<Record>>`	`fetchAsync(java.util.concurrent.Executor executor, SQL sql)` Fetch results in a new `CompletionStage` that is asynchronously completed by a task running in the given executor.
`java.util.concurrent.CompletionStage<Result<Record>>`	`fetchAsync(java.util.concurrent.Executor executor, java.lang.String sql)` Fetch results in a new `CompletionStage` that is asynchronously completed by a task running in the given executor.
`java.util.concurrent.CompletionStage<Result<Record>>`	`fetchAsync(java.util.concurrent.Executor executor, java.lang.String sql, java.lang.Object... bindings)` Fetch results in a new `CompletionStage` that is asynchronously completed by a task running in the given executor.
`java.util.concurrent.CompletionStage<Result<Record>>`	`fetchAsync(java.util.concurrent.Executor executor, java.lang.String sql, QueryPart... parts)` Fetch results in a new `CompletionStage` that is asynchronously completed by a task running in the given executor.
`<R extends Record> java.util.concurrent.CompletionStage<Result<R>>`	`fetchAsync(java.util.concurrent.Executor executor, Table<R> table)` Execute and return all records asynchronously for `SELECT * FROM [table]`.
`<R extends Record> java.util.concurrent.CompletionStage<Result<R>>`	`fetchAsync(java.util.concurrent.Executor executor, Table<R> table, Condition condition)` Execute and return all records asynchronously for `SELECT * FROM [table] WHERE [condition]` .
`<R extends Record> java.util.concurrent.CompletionStage<Result<R>>`	`fetchAsync(ResultQuery<R> query)` Fetch results in a new `CompletionStage`.
`java.util.concurrent.CompletionStage<Result<Record>>`	`fetchAsync(java.sql.ResultSet rs)` Fetch results in a new `CompletionStage`.
`java.util.concurrent.CompletionStage<Result<Record>>`	`fetchAsync(java.sql.ResultSet rs, java.lang.Class<?>... types)` Fetch results in a new `CompletionStage`.
`java.util.concurrent.CompletionStage<Result<Record>>`	`fetchAsync(java.sql.ResultSet rs, DataType<?>... types)` Fetch results in a new `CompletionStage`.
`java.util.concurrent.CompletionStage<Result<Record>>`	`fetchAsync(java.sql.ResultSet rs, Field<?>... fields)` Fetch results in a new `CompletionStage`.
`java.util.concurrent.CompletionStage<Result<Record>>`	`fetchAsync(SQL sql)` Fetch results in a new `CompletionStage`.
`java.util.concurrent.CompletionStage<Result<Record>>`	`fetchAsync(java.lang.String sql)` Fetch results in a new `CompletionStage`.
`java.util.concurrent.CompletionStage<Result<Record>>`	`fetchAsync(java.lang.String sql, java.lang.Object... bindings)` Fetch results in a new `CompletionStage`.
`java.util.concurrent.CompletionStage<Result<Record>>`	`fetchAsync(java.lang.String sql, QueryPart... parts)` Fetch results in a new `CompletionStage`.
`<R extends Record> java.util.concurrent.CompletionStage<Result<R>>`	`fetchAsync(Table<R> table)` Execute and return all records asynchronously for `SELECT * FROM [table]`.
`<R extends Record> java.util.concurrent.CompletionStage<Result<R>>`	`fetchAsync(Table<R> table, Condition condition)` Execute and return all records asynchronously for `SELECT * FROM [table] WHERE [condition]` .
`<R extends TableRecord<R>> Result<R>`	`fetchByExample(R example)` Execute a "Query by Example" (QBE) based on an example record.
`int`	`fetchCount(Select<?> query)` Execute a `Select` query in the context of this `DSLContext` and return a `COUNT(*)` value.
`int`	`fetchCount(Table<?> table)` Count the number of records in a table.
`int`	`fetchCount(Table<?> table, Condition condition)` Count the number of records in a table that satisfy a condition.
`boolean`	`fetchExists(Select<?> query)` Check if a `Select` would return any records, if it were executed.
`boolean`	`fetchExists(Table<?> table)` Check if a table has any records.
`boolean`	`fetchExists(Table<?> table, Condition condition)` Check if a table has any records that satisfy a condition.
`Result<Record>`	`fetchFromCSV(java.lang.String string)` Fetch all data from a CSV string.
`Result<Record>`	`fetchFromCSV(java.lang.String string, boolean header)` Fetch all data from a CSV string.
`Result<Record>`	`fetchFromCSV(java.lang.String string, boolean header, char delimiter)` Fetch all data from a CSV string.
`Result<Record>`	`fetchFromCSV(java.lang.String string, char delimiter)` Fetch all data from a CSV string.
`Result<Record>`	`fetchFromHTML(java.lang.String string)` Convert an HTML table into a jOOQ `Result`.
`Result<Record>`	`fetchFromJSON(java.lang.String string)` Fetch all data from a JSON string.
`Result<Record>`	`fetchFromStringData(java.util.List<java.lang.String[]> data)` Fetch all data from a list of strings.
`Result<Record>`	`fetchFromStringData(java.util.List<java.lang.String[]> data, boolean header)` Fetch all data from a list of strings.
`Result<Record>`	`fetchFromStringData(java.lang.String[]... data)` Fetch all data from a list of strings.
`Result<Record>`	`fetchFromTXT(java.lang.String string)` Fetch all data from a formatted string.
`Result<Record>`	`fetchFromTXT(java.lang.String string, java.lang.String nullLiteral)` Fetch all data from a formatted string.
`<R extends Record> Cursor<R>`	`fetchLazy(ResultQuery<R> query)` Execute a `ResultQuery` in the context of this `DSLContext` and return a cursor.
`Cursor<Record>`	`fetchLazy(java.sql.ResultSet rs)` Wrap a JDBC `ResultSet` into a jOOQ `Cursor`.
`Cursor<Record>`	`fetchLazy(java.sql.ResultSet rs, java.lang.Class<?>... types)` Wrap a JDBC `ResultSet` into a jOOQ `Cursor`.
`Cursor<Record>`	`fetchLazy(java.sql.ResultSet rs, DataType<?>... types)` Wrap a JDBC `ResultSet` into a jOOQ `Cursor`.
`Cursor<Record>`	`fetchLazy(java.sql.ResultSet rs, Field<?>... fields)` Wrap a JDBC `ResultSet` into a jOOQ `Cursor`.
`Cursor<Record>`	`fetchLazy(SQL sql)` Execute a new query holding plain SQL and "lazily" return the generated result.
`Cursor<Record>`	`fetchLazy(java.lang.String sql)` Execute a new query holding plain SQL and "lazily" return the generated result.
`Cursor<Record>`	`fetchLazy(java.lang.String sql, java.lang.Object... bindings)` Execute a new query holding plain SQL and "lazily" return the generated result.
`Cursor<Record>`	`fetchLazy(java.lang.String sql, QueryPart... parts)` Execute a new query holding plain SQL and "lazily" return the generated result.
`<R extends Record> Cursor<R>`	`fetchLazy(Table<R> table)` Execute and return all records lazily for `SELECT * FROM [table]`.
`<R extends Record> Cursor<R>`	`fetchLazy(Table<R> table, Condition condition)` Execute and return all records lazily for `SELECT * FROM [table] WHERE [condition]` .
`<R extends Record> Results`	`fetchMany(ResultQuery<R> query)` Execute a `ResultQuery` in the context of this `DSLContext` and return a cursor.
`Results`	`fetchMany(SQL sql)` Execute a new query holding plain SQL, possibly returning several result sets.
`Results`	`fetchMany(java.lang.String sql)` Execute a new query holding plain SQL, possibly returning several result sets.
`Results`	`fetchMany(java.lang.String sql, java.lang.Object... bindings)` Execute a new query holding plain SQL, possibly returning several result sets.
`Results`	`fetchMany(java.lang.String sql, QueryPart... parts)` Execute a new query holding plain SQL, possibly returning several result sets.
`<R extends Record> R`	`fetchOne(ResultQuery<R> query)` Execute a `ResultQuery` in the context of this `DSLContext` and return a record.
`Record`	`fetchOne(java.sql.ResultSet rs)` Fetch a record from a JDBC `ResultSet` and transform it to a jOOQ `Record`.
`Record`	`fetchOne(java.sql.ResultSet rs, java.lang.Class<?>... types)` Fetch a record from a JDBC `ResultSet` and transform it to a jOOQ `Record`.
`Record`	`fetchOne(java.sql.ResultSet rs, DataType<?>... types)` Fetch a record from a JDBC `ResultSet` and transform it to a jOOQ `Record`.
`Record`	`fetchOne(java.sql.ResultSet rs, Field<?>... fields)` Fetch a record from a JDBC `ResultSet` and transform it to a jOOQ `Record`.
`Record`	`fetchOne(SQL sql)` Execute a new query holding plain SQL.
`Record`	`fetchOne(java.lang.String sql)` Execute a new query holding plain SQL.
`Record`	`fetchOne(java.lang.String sql, java.lang.Object... bindings)` Execute a new query holding plain SQL.
`Record`	`fetchOne(java.lang.String sql, QueryPart... parts)` Execute a new query holding plain SQL.
`<R extends Record> R`	`fetchOne(Table<R> table)` Execute and return zero or one record for `SELECT * FROM [table]`.
`<R extends Record> R`	`fetchOne(Table<R> table, Condition condition)` Execute and return zero or one record for `SELECT * FROM [table] WHERE [condition]` .
`<R extends Record> java.util.Optional<R>`	`fetchOptional(ResultQuery<R> query)` Execute a `ResultQuery` in the context of this `DSLContext` and return a record.
`java.util.Optional<Record>`	`fetchOptional(java.sql.ResultSet rs)` Fetch a record from a JDBC `ResultSet` and transform it to a jOOQ `Record`.
`java.util.Optional<Record>`	`fetchOptional(java.sql.ResultSet rs, java.lang.Class<?>... types)` Fetch a record from a JDBC `ResultSet` and transform it to a jOOQ `Record`.
`java.util.Optional<Record>`	`fetchOptional(java.sql.ResultSet rs, DataType<?>... types)` Fetch a record from a JDBC `ResultSet` and transform it to a jOOQ `Record`.
`java.util.Optional<Record>`	`fetchOptional(java.sql.ResultSet rs, Field<?>... fields)` Fetch a record from a JDBC `ResultSet` and transform it to a jOOQ `Record`.
`java.util.Optional<Record>`	`fetchOptional(SQL sql)` Execute a new query holding plain SQL.
`java.util.Optional<Record>`	`fetchOptional(java.lang.String sql)` Execute a new query holding plain SQL.
`java.util.Optional<Record>`	`fetchOptional(java.lang.String sql, java.lang.Object... bindings)` Execute a new query holding plain SQL.
`java.util.Optional<Record>`	`fetchOptional(java.lang.String sql, QueryPart... parts)` Execute a new query holding plain SQL.
`<R extends Record> java.util.Optional<R>`	`fetchOptional(Table<R> table)` Execute and return zero or one record for `SELECT * FROM [table]`.
`<R extends Record> java.util.Optional<R>`	`fetchOptional(Table<R> table, Condition condition)` Execute and return zero or one record for `SELECT * FROM [table] WHERE [condition]` .
`<T,R extends Record1<T>> java.util.Optional<T>`	`fetchOptionalValue(ResultQuery<R> query)` Execute a `ResultQuery` in the context of this `DSLContext` and return a single value.
`java.util.Optional<?>`	`fetchOptionalValue(java.sql.ResultSet rs)` Fetch a record from a JDBC `ResultSet` and return the only contained value.
`<T> java.util.Optional<T>`	`fetchOptionalValue(java.sql.ResultSet rs, java.lang.Class<T> type)` Fetch a record from a JDBC `ResultSet` and return the only contained value.
`<T> java.util.Optional<T>`	`fetchOptionalValue(java.sql.ResultSet rs, DataType<T> type)` Fetch a record from a JDBC `ResultSet` and return the only contained value.
`<T> java.util.Optional<T>`	`fetchOptionalValue(java.sql.ResultSet rs, Field<T> field)` Fetch a record from a JDBC `ResultSet` and return the only contained value.
`java.util.Optional<?>`	`fetchOptionalValue(SQL sql)` Execute a new query holding plain SQL.
`java.util.Optional<?>`	`fetchOptionalValue(java.lang.String sql)` Execute a new query holding plain SQL.
`java.util.Optional<?>`	`fetchOptionalValue(java.lang.String sql, java.lang.Object... bindings)` Execute a new query holding plain SQL.
`java.util.Optional<?>`	`fetchOptionalValue(java.lang.String sql, QueryPart... parts)` Execute a new query holding plain SQL.
`<T> java.util.Optional<T>`	`fetchOptionalValue(TableField<?,T> field)` Execute a `ResultQuery` in the context of this `DSLContext` and return a single value.
`<R extends Record> R`	`fetchSingle(ResultQuery<R> query)` Execute a `ResultQuery` in the context of this `DSLContext` and return a record.
`Record`	`fetchSingle(java.sql.ResultSet rs)` Fetch a record from a JDBC `ResultSet` and transform it to a jOOQ `Record`.
`Record`	`fetchSingle(java.sql.ResultSet rs, java.lang.Class<?>... types)` Fetch a record from a JDBC `ResultSet` and transform it to a jOOQ `Record`.
`Record`	`fetchSingle(java.sql.ResultSet rs, DataType<?>... types)` Fetch a record from a JDBC `ResultSet` and transform it to a jOOQ `Record`.
`Record`	`fetchSingle(java.sql.ResultSet rs, Field<?>... fields)` Fetch a record from a JDBC `ResultSet` and transform it to a jOOQ `Record`.
`Record`	`fetchSingle(SQL sql)` Execute a new query holding plain SQL.
`Record`	`fetchSingle(java.lang.String sql)` Execute a new query holding plain SQL.
`Record`	`fetchSingle(java.lang.String sql, java.lang.Object... bindings)` Execute a new query holding plain SQL.
`Record`	`fetchSingle(java.lang.String sql, QueryPart... parts)` Execute a new query holding plain SQL.
`<R extends Record> R`	`fetchSingle(Table<R> table)` Execute and return exactly one record for `SELECT * FROM [table]`.
`<R extends Record> R`	`fetchSingle(Table<R> table, Condition condition)` Execute and return exactly one record for `SELECT * FROM [table] WHERE [condition]` .
`<R extends Record> java.util.stream.Stream<R>`	`fetchStream(ResultQuery<R> query)` Execute a `ResultQuery` in the context of this `DSLContext` and return a stream.
`java.util.stream.Stream<Record>`	`fetchStream(java.sql.ResultSet rs)` Wrap a JDBC `ResultSet` into a jOOQ `Stream`.
`java.util.stream.Stream<Record>`	`fetchStream(java.sql.ResultSet rs, java.lang.Class<?>... types)` Wrap a JDBC `ResultSet` into a jOOQ `Stream`.
`java.util.stream.Stream<Record>`	`fetchStream(java.sql.ResultSet rs, DataType<?>... types)` Wrap a JDBC `ResultSet` into a jOOQ `Stream`.
`java.util.stream.Stream<Record>`	`fetchStream(java.sql.ResultSet rs, Field<?>... fields)` Wrap a JDBC `ResultSet` into a jOOQ `Stream`.
`java.util.stream.Stream<Record>`	`fetchStream(SQL sql)` Execute a new query holding plain SQL and "lazily" return the generated result.
`java.util.stream.Stream<Record>`	`fetchStream(java.lang.String sql)` Execute a new query holding plain SQL and "lazily" return the generated result.
`java.util.stream.Stream<Record>`	`fetchStream(java.lang.String sql, java.lang.Object... bindings)` Execute a new query holding plain SQL and "lazily" return the generated result.
`java.util.stream.Stream<Record>`	`fetchStream(java.lang.String sql, QueryPart... parts)` Execute a new query holding plain SQL and "lazily" return the generated result.
`<R extends Record> java.util.stream.Stream<R>`	`fetchStream(Table<R> table)` Execute and return all records lazily for `SELECT * FROM [table]`.
`<R extends Record> java.util.stream.Stream<R>`	`fetchStream(Table<R> table, Condition condition)` Execute and return all records lazily for `SELECT * FROM [table] WHERE [condition]` .
`<T,R extends Record1<T>> T`	`fetchValue(ResultQuery<R> query)` Execute a `ResultQuery` in the context of this `DSLContext` and return a single value.
`java.lang.Object`	`fetchValue(java.sql.ResultSet rs)` Fetch a record from a JDBC `ResultSet` and return the only contained value.
`<T> T`	`fetchValue(java.sql.ResultSet rs, java.lang.Class<T> type)` Fetch a record from a JDBC `ResultSet` and return the only contained value.
`<T> T`	`fetchValue(java.sql.ResultSet rs, DataType<T> type)` Fetch a record from a JDBC `ResultSet` and return the only contained value.
`<T> T`	`fetchValue(java.sql.ResultSet rs, Field<T> field)` Fetch a record from a JDBC `ResultSet` and return the only contained value.
`java.lang.Object`	`fetchValue(SQL sql)` Execute a new query holding plain SQL.
`java.lang.Object`	`fetchValue(java.lang.String sql)` Execute a new query holding plain SQL.
`java.lang.Object`	`fetchValue(java.lang.String sql, java.lang.Object... bindings)` Execute a new query holding plain SQL.
`java.lang.Object`	`fetchValue(java.lang.String sql, QueryPart... parts)` Execute a new query holding plain SQL.
`<T> T`	`fetchValue(TableField<?,T> field)` Execute a `ResultQuery` in the context of this `DSLContext` and return a single value.
`<T,R extends Record1<T>> java.util.List<T>`	`fetchValues(ResultQuery<R> query)` Execute a `ResultQuery` in the context of this `DSLContext` and return all values for the only column.
`java.util.List<?>`	`fetchValues(java.sql.ResultSet rs)` Fetch a result from a JDBC `ResultSet` and return the only contained column's values.
`<T> java.util.List<T>`	`fetchValues(java.sql.ResultSet rs, java.lang.Class<T> type)` Fetch a result from a JDBC `ResultSet` and return the only contained column's values.
`<T> java.util.List<T>`	`fetchValues(java.sql.ResultSet rs, DataType<T> type)` Fetch a result from a JDBC `ResultSet` and return the only contained column's values.
`<T> java.util.List<T>`	`fetchValues(java.sql.ResultSet rs, Field<T> field)` Fetch a result from a JDBC `ResultSet` and return the only contained column's values.
`java.util.List<?>`	`fetchValues(SQL sql)` Execute a new query holding plain SQL.
`java.util.List<?>`	`fetchValues(java.lang.String sql)` Execute a new query holding plain SQL.
`java.util.List<?>`	`fetchValues(java.lang.String sql, java.lang.Object... bindings)` Execute a new query holding plain SQL.
`java.util.List<?>`	`fetchValues(java.lang.String sql, QueryPart... parts)` Execute a new query holding plain SQL.
`<T> java.util.List<T>`	`fetchValues(TableField<?,T> field)` Fetch all values in a given `Table`'s `TableField`.
`InformationSchema`	`informationSchema(Catalog... catalogs)` Export a set of catalogs to the `InformationSchema` format.
`InformationSchema`	`informationSchema(Catalog catalog)` Export a catalog to the `InformationSchema` format.
`InformationSchema`	`informationSchema(Schema... schemas)` Export a set of schemas to the `InformationSchema` format.
`InformationSchema`	`informationSchema(Schema schema)` Export a schema to the `InformationSchema` format.
`InformationSchema`	`informationSchema(Table<?>... table)` Export a set of tables to the `InformationSchema` format.
`InformationSchema`	`informationSchema(Table<?> table)` Export a table to the `InformationSchema` format.
`<R extends Record> InsertSetStep<R>`	`insertInto(Table<R> into)` Create a new DSL insert statement.
`<R extends Record> InsertValuesStepN<R>`	`insertInto(Table<R> into, java.util.Collection<? extends Field<?>> fields)` Create a new DSL insert statement.
`<R extends Record> InsertValuesStepN<R>`	`insertInto(Table<R> into, Field<?>... fields)` Create a new DSL insert statement.
`<R extends Record,T1> InsertValuesStep1<R,T1>`	`insertInto(Table<R> into, Field<T1> field1)` Create a new DSL insert statement.
`<R extends Record,T1,T2> InsertValuesStep2<R,T1,T2>`	`insertInto(Table<R> into, Field<T1> field1, Field<T2> field2)` Create a new DSL insert statement.
`<R extends Record,T1,T2,T3> InsertValuesStep3<R,T1,T2,T3>`	`insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3)` Create a new DSL insert statement.
`<R extends Record,T1,T2,T3,T4> InsertValuesStep4<R,T1,T2,T3,T4>`	`insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4)` Create a new DSL insert statement.
`<R extends Record,T1,T2,T3,T4,T5> InsertValuesStep5<R,T1,T2,T3,T4,T5>`	`insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5)` Create a new DSL insert statement.
`<R extends Record,T1,T2,T3,T4,T5,T6> InsertValuesStep6<R,T1,T2,T3,T4,T5,T6>`	`insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6)` Create a new DSL insert statement.
`<R extends Record,T1,T2,T3,T4,T5,T6,T7> InsertValuesStep7<R,T1,T2,T3,T4,T5,T6,T7>`	`insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7)` Create a new DSL insert statement.
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8> InsertValuesStep8<R,T1,T2,T3,T4,T5,T6,T7,T8>`	`insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8)` Create a new DSL insert statement.
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9> InsertValuesStep9<R,T1,T2,T3,T4,T5,T6,T7,T8,T9>`	`insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9)` Create a new DSL insert statement.
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10> InsertValuesStep10<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10>`	`insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10)` Create a new DSL insert statement.
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11> InsertValuesStep11<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11>`	`insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11)` Create a new DSL insert statement.
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12> InsertValuesStep12<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12>`	`insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12)` Create a new DSL insert statement.
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13> InsertValuesStep13<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13>`	`insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13)` Create a new DSL insert statement.
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14> InsertValuesStep14<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14>`	`insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14)` Create a new DSL insert statement.
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15> InsertValuesStep15<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15>`	`insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15)` Create a new DSL insert statement.
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16> InsertValuesStep16<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16>`	`insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16)` Create a new DSL insert statement.
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17> InsertValuesStep17<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17>`	`insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17)` Create a new DSL insert statement.
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18> InsertValuesStep18<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18>`	`insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18)` Create a new DSL insert statement.
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19> InsertValuesStep19<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19>`	`insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19)` Create a new DSL insert statement.
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20> InsertValuesStep20<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20>`	`insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20)` Create a new DSL insert statement.
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21> InsertValuesStep21<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21>`	`insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20, Field<T21> field21)` Create a new DSL insert statement.
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22> InsertValuesStep22<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22>`	`insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20, Field<T21> field21, Field<T22> field22)` Create a new DSL insert statement.
`<R extends Record> InsertQuery<R>`	`insertQuery(Table<R> into)` Create a new `InsertQuery`
`java.math.BigInteger`	`lastID()` Retrieve the last inserted ID.
`<R extends Record> LoaderOptionsStep<R>`	`loadInto(Table<R> table)` Create a new `Loader` object to load data from a CSV or XML source.
`Schema`	`map(Schema schema)` Map a schema to another one.
`<R extends Record> Table<R>`	`map(Table<R> table)` Map a table to another one.
`<R extends Record> MergeUsingStep<R>`	`mergeInto(Table<R> table)` Create a new DSL SQL standard MERGE statement.
`<R extends Record> MergeKeyStepN<R>`	`mergeInto(Table<R> table, java.util.Collection<? extends Field<?>> fields)` Create a new DSL merge statement (H2-specific syntax).
`<R extends Record> MergeKeyStepN<R>`	`mergeInto(Table<R> table, Field<?>... fields)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`<R extends Record,T1> MergeKeyStep1<R,T1>`	`mergeInto(Table<R> table, Field<T1> field1)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`<R extends Record,T1,T2> MergeKeyStep2<R,T1,T2>`	`mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`<R extends Record,T1,T2,T3> MergeKeyStep3<R,T1,T2,T3>`	`mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`<R extends Record,T1,T2,T3,T4> MergeKeyStep4<R,T1,T2,T3,T4>`	`mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`<R extends Record,T1,T2,T3,T4,T5> MergeKeyStep5<R,T1,T2,T3,T4,T5>`	`mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`<R extends Record,T1,T2,T3,T4,T5,T6> MergeKeyStep6<R,T1,T2,T3,T4,T5,T6>`	`mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`<R extends Record,T1,T2,T3,T4,T5,T6,T7> MergeKeyStep7<R,T1,T2,T3,T4,T5,T6,T7>`	`mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8> MergeKeyStep8<R,T1,T2,T3,T4,T5,T6,T7,T8>`	`mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9> MergeKeyStep9<R,T1,T2,T3,T4,T5,T6,T7,T8,T9>`	`mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10> MergeKeyStep10<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10>`	`mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11> MergeKeyStep11<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11>`	`mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12> MergeKeyStep12<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12>`	`mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13> MergeKeyStep13<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13>`	`mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14> MergeKeyStep14<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14>`	`mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15> MergeKeyStep15<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15>`	`mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16> MergeKeyStep16<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16>`	`mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17> MergeKeyStep17<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17>`	`mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18> MergeKeyStep18<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18>`	`mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19> MergeKeyStep19<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19>`	`mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20> MergeKeyStep20<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20>`	`mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21> MergeKeyStep21<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21>`	`mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20, Field<T21> field21)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22> MergeKeyStep22<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22>`	`mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20, Field<T21> field21, Field<T22> field22)` Create a new DSL UPSERT statement (`SQLDialect.H2` `MERGE`) or `SQLDialect.HANA` `UPSERT`).
`Meta`	`meta()` Access the database meta data.
`Meta`	`meta(InformationSchema schema)` Access the databse meta data from its serialised form.
`void`	`mock(MockDataProvider provider, MockRunnable mockable)` Run a `MockRunnable` in the context of this `DSLContext` 's underlying `Scope.configuration()`'s, and of a `MockDataProvider`.
`<T> T`	`mockResult(MockDataProvider provider, MockCallable<T> mockable)` Run a `MockRunnable` in the context of this `DSLContext` 's underlying `Scope.configuration()`'s, and of a `MockDataProvider` and return the `mockable`'s outcome.
`Record`	`newRecord(Field<?>... fields)` Create a new empty `Record`.
`<T1> Record1<T1>`	`newRecord(Field<T1> field1)` Create a new empty `Record`.
`<T1,T2> Record2<T1,T2>`	`newRecord(Field<T1> field1, Field<T2> field2)` Create a new empty `Record`.
`<T1,T2,T3> Record3<T1,T2,T3>`	`newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3)` Create a new empty `Record`.
`<T1,T2,T3,T4> Record4<T1,T2,T3,T4>`	`newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4)` Create a new empty `Record`.
`<T1,T2,T3,T4,T5> Record5<T1,T2,T3,T4,T5>`	`newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5)` Create a new empty `Record`.
`<T1,T2,T3,T4,T5,T6> Record6<T1,T2,T3,T4,T5,T6>`	`newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6)` Create a new empty `Record`.
`<T1,T2,T3,T4,T5,T6,T7> Record7<T1,T2,T3,T4,T5,T6,T7>`	`newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7)` Create a new empty `Record`.
`<T1,T2,T3,T4,T5,T6,T7,T8> Record8<T1,T2,T3,T4,T5,T6,T7,T8>`	`newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8)` Create a new empty `Record`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9> Record9<T1,T2,T3,T4,T5,T6,T7,T8,T9>`	`newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9)` Create a new empty `Record`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10> Record10<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10>`	`newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10)` Create a new empty `Record`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11> Record11<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11>`	`newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11)` Create a new empty `Record`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12> Record12<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12>`	`newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12)` Create a new empty `Record`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13> Record13<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13>`	`newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13)` Create a new empty `Record`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14> Record14<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14>`	`newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14)` Create a new empty `Record`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15> Record15<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15>`	`newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15)` Create a new empty `Record`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16> Record16<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16>`	`newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16)` Create a new empty `Record`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17> Record17<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17>`	`newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17)` Create a new empty `Record`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18> Record18<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18>`	`newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18)` Create a new empty `Record`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19> Record19<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19>`	`newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19)` Create a new empty `Record`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20> Record20<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20>`	`newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20)` Create a new empty `Record`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21> Record21<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21>`	`newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20, Field<T21> field21)` Create a new empty `Record`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22> Record22<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22>`	`newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20, Field<T21> field21, Field<T22> field22)` Create a new empty `Record`.
`<R extends Record> R`	`newRecord(Table<R> table)` Create a new `Record` that can be inserted into the corresponding table.
`<R extends Record> R`	`newRecord(Table<R> table, java.lang.Object source)` Create a new pre-filled `Record` that can be inserted into the corresponding table.
`<R extends UDTRecord<R>> R`	`newRecord(UDT<R> type)` Create a new `UDTRecord`.
`Result<Record>`	`newResult(Field<?>... fields)` Create a new empty `Record`.
`<T1> Result<Record1<T1>>`	`newResult(Field<T1> field1)` Create a new empty `Result`.
`<T1,T2> Result<Record2<T1,T2>>`	`newResult(Field<T1> field1, Field<T2> field2)` Create a new empty `Result`.
`<T1,T2,T3> Result<Record3<T1,T2,T3>>`	`newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3)` Create a new empty `Result`.
`<T1,T2,T3,T4> Result<Record4<T1,T2,T3,T4>>`	`newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4)` Create a new empty `Result`.
`<T1,T2,T3,T4,T5> Result<Record5<T1,T2,T3,T4,T5>>`	`newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5)` Create a new empty `Result`.
`<T1,T2,T3,T4,T5,T6> Result<Record6<T1,T2,T3,T4,T5,T6>>`	`newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6)` Create a new empty `Result`.
`<T1,T2,T3,T4,T5,T6,T7> Result<Record7<T1,T2,T3,T4,T5,T6,T7>>`	`newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7)` Create a new empty `Result`.
`<T1,T2,T3,T4,T5,T6,T7,T8> Result<Record8<T1,T2,T3,T4,T5,T6,T7,T8>>`	`newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8)` Create a new empty `Result`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9> Result<Record9<T1,T2,T3,T4,T5,T6,T7,T8,T9>>`	`newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9)` Create a new empty `Result`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10> Result<Record10<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10>>`	`newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10)` Create a new empty `Result`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11> Result<Record11<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11>>`	`newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11)` Create a new empty `Result`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12> Result<Record12<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12>>`	`newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12)` Create a new empty `Result`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13> Result<Record13<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13>>`	`newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13)` Create a new empty `Result`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14> Result<Record14<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14>>`	`newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14)` Create a new empty `Result`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15> Result<Record15<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15>>`	`newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15)` Create a new empty `Result`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16> Result<Record16<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16>>`	`newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16)` Create a new empty `Result`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17> Result<Record17<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17>>`	`newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17)` Create a new empty `Result`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18> Result<Record18<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18>>`	`newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18)` Create a new empty `Result`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19> Result<Record19<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19>>`	`newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19)` Create a new empty `Result`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20> Result<Record20<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20>>`	`newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20)` Create a new empty `Result`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21> Result<Record21<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21>>`	`newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20, Field<T21> field21)` Create a new empty `Result`.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22> Result<Record22<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22>>`	`newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20, Field<T21> field21, Field<T22> field22)` Create a new empty `Result`.
`<R extends Record> Result<R>`	`newResult(Table<R> table)` Create a new empty `Result`.
`java.math.BigInteger`	`nextval(Name sequence)` Convenience method to fetch the NEXTVAL for a sequence directly from this `DSLContext`'s underlying JDBC `Connection`.
`<T extends java.lang.Number> T`	`nextval(Sequence<T> sequence)` Convenience method to fetch the NEXTVAL for a sequence directly from this `DSLContext`'s underlying JDBC `Connection`.
`java.math.BigInteger`	`nextval(java.lang.String sequence)` Convenience method to fetch the NEXTVAL for a sequence directly from this `DSLContext`'s underlying JDBC `Connection`.
`Parser`	`parser()` Access the parser API.
`java.sql.Connection`	`parsingConnection()` A JDBC connection that runs each statement through the `parser()` first, prior to re-generating and running the SQL.
`Queries`	`queries(java.util.Collection<? extends Query> queries)` Wrap a collection of queries.
`Queries`	`queries(Query... queries)` Wrap a collection of queries.
`Query`	`query(SQL sql)` Create a new query holding plain SQL.
`Query`	`query(java.lang.String sql)` Create a new query holding plain SQL.
`Query`	`query(java.lang.String sql, java.lang.Object... bindings)` Create a new query holding plain SQL.
`Query`	`query(java.lang.String sql, QueryPart... parts)` Create a new query holding plain SQL.
`java.lang.String`	`render(QueryPart part)` Render a QueryPart in the context of this `DSLContext`.
`RenderContext`	`renderContext()` Deprecated. - [#6280] - 3.10 - Do not reuse this method. It will be completely internal with jOOQ 4.0
`java.lang.String`	`renderInlined(QueryPart part)` Render a QueryPart in the context of this `DSLContext`, inlining all bind variables.
`java.lang.String`	`renderNamedOrInlinedParams(QueryPart part)` Render a QueryPart in the context of this `DSLContext`, rendering bind variables as named parameters, or inlined parameters if they have no name.
`java.lang.String`	`renderNamedParams(QueryPart part)` Render a QueryPart in the context of this `DSLContext`, rendering bind variables as named parameters.
`ResultQuery<Record>`	`resultQuery(SQL sql)` Create a new query holding plain SQL.
`ResultQuery<Record>`	`resultQuery(java.lang.String sql)` Create a new query holding plain SQL.
`ResultQuery<Record>`	`resultQuery(java.lang.String sql, java.lang.Object... bindings)` Create a new query holding plain SQL.
`ResultQuery<Record>`	`resultQuery(java.lang.String sql, QueryPart... parts)` Create a new query holding plain SQL.
`SelectSelectStep<Record>`	`select(java.util.Collection<? extends SelectField<?>> fields)` Create a new DSL select statement.
`SelectSelectStep<Record>`	`select(SelectField<?>... fields)` Create a new DSL select statement.
`<T1> SelectSelectStep<Record1<T1>>`	`select(SelectField<T1> field1)` Create a new DSL select statement.
`<T1,T2> SelectSelectStep<Record2<T1,T2>>`	`select(SelectField<T1> field1, SelectField<T2> field2)` Create a new DSL select statement.
`<T1,T2,T3> SelectSelectStep<Record3<T1,T2,T3>>`	`select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3)` Create a new DSL select statement.
`<T1,T2,T3,T4> SelectSelectStep<Record4<T1,T2,T3,T4>>`	`select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5> SelectSelectStep<Record5<T1,T2,T3,T4,T5>>`	`select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6> SelectSelectStep<Record6<T1,T2,T3,T4,T5,T6>>`	`select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7> SelectSelectStep<Record7<T1,T2,T3,T4,T5,T6,T7>>`	`select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8> SelectSelectStep<Record8<T1,T2,T3,T4,T5,T6,T7,T8>>`	`select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9> SelectSelectStep<Record9<T1,T2,T3,T4,T5,T6,T7,T8,T9>>`	`select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10> SelectSelectStep<Record10<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10>>`	`select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11> SelectSelectStep<Record11<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11>>`	`select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12> SelectSelectStep<Record12<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12>>`	`select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13> SelectSelectStep<Record13<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13>>`	`select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14> SelectSelectStep<Record14<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14>>`	`select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15> SelectSelectStep<Record15<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15>>`	`select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16> SelectSelectStep<Record16<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16>>`	`select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17> SelectSelectStep<Record17<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17>>`	`select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18> SelectSelectStep<Record18<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18>>`	`select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17, SelectField<T18> field18)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19> SelectSelectStep<Record19<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19>>`	select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17, SelectField<T18> field18, SelectField<T19> field19) Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20> SelectSelectStep<Record20<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20>>`	select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17, SelectField<T18> field18, SelectField<T19> field19, SelectField<T20> field20) Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21> SelectSelectStep<Record21<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21>>`	select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17, SelectField<T18> field18, SelectField<T19> field19, SelectField<T20> field20, SelectField<T21> field21) Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22> SelectSelectStep<Record22<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22>>`	select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17, SelectField<T18> field18, SelectField<T19> field19, SelectField<T20> field20, SelectField<T21> field21, SelectField<T22> field22) Create a new DSL select statement.
`SelectSelectStep<Record1<java.lang.Integer>>`	`selectCount()` Create a new DSL select statement for `COUNT(*)`.
`SelectSelectStep<Record>`	`selectDistinct(java.util.Collection<? extends SelectField<?>> fields)` Create a new DSL select statement.
`SelectSelectStep<Record>`	`selectDistinct(SelectField<?>... fields)` Create a new DSL select statement.
`<T1> SelectSelectStep<Record1<T1>>`	`selectDistinct(SelectField<T1> field1)` Create a new DSL select statement.
`<T1,T2> SelectSelectStep<Record2<T1,T2>>`	`selectDistinct(SelectField<T1> field1, SelectField<T2> field2)` Create a new DSL select statement.
`<T1,T2,T3> SelectSelectStep<Record3<T1,T2,T3>>`	`selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3)` Create a new DSL select statement.
`<T1,T2,T3,T4> SelectSelectStep<Record4<T1,T2,T3,T4>>`	`selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5> SelectSelectStep<Record5<T1,T2,T3,T4,T5>>`	`selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6> SelectSelectStep<Record6<T1,T2,T3,T4,T5,T6>>`	`selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7> SelectSelectStep<Record7<T1,T2,T3,T4,T5,T6,T7>>`	`selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8> SelectSelectStep<Record8<T1,T2,T3,T4,T5,T6,T7,T8>>`	`selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9> SelectSelectStep<Record9<T1,T2,T3,T4,T5,T6,T7,T8,T9>>`	`selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10> SelectSelectStep<Record10<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10>>`	`selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11> SelectSelectStep<Record11<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11>>`	`selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12> SelectSelectStep<Record12<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12>>`	`selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13> SelectSelectStep<Record13<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13>>`	`selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14> SelectSelectStep<Record14<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14>>`	`selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15> SelectSelectStep<Record15<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15>>`	`selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16> SelectSelectStep<Record16<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16>>`	`selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17> SelectSelectStep<Record17<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17>>`	`selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18> SelectSelectStep<Record18<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18>>`	`selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17, SelectField<T18> field18)` Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19> SelectSelectStep<Record19<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19>>`	selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17, SelectField<T18> field18, SelectField<T19> field19) Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20> SelectSelectStep<Record20<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20>>`	selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17, SelectField<T18> field18, SelectField<T19> field19, SelectField<T20> field20) Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21> SelectSelectStep<Record21<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21>>`	selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17, SelectField<T18> field18, SelectField<T19> field19, SelectField<T20> field20, SelectField<T21> field21) Create a new DSL select statement.
`<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22> SelectSelectStep<Record22<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22>>`	selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17, SelectField<T18> field18, SelectField<T19> field19, SelectField<T20> field20, SelectField<T21> field21, SelectField<T22> field22) Create a new DSL select statement.
`<R extends Record> SelectWhereStep<R>`	`selectFrom(Table<R> table)` Create a new DSL select statement.
`SelectSelectStep<Record1<java.lang.Integer>>`	`selectOne()` Create a new DSL select statement for a constant `1` literal.
`SelectQuery<Record>`	`selectQuery()` Create a new `SelectQuery`
`<R extends Record> SelectQuery<R>`	`selectQuery(TableLike<R> table)` Create a new `SelectQuery`
`SelectSelectStep<Record1<java.lang.Integer>>`	`selectZero()` Create a new DSL select statement for a constant `0` literal.
`Query`	`setCatalog(Catalog catalog)` Set the current catalog to a new value.
`Query`	`setCatalog(Name catalog)` Set the current catalog to a new value.
`Query`	`setCatalog(java.lang.String catalog)` Set the current catalog to a new value.
`Query`	`setSchema(Name schema)` Set the current schema to a new value.
`Query`	`setSchema(Schema schema)` Set the current schema to a new value.
`Query`	`setSchema(java.lang.String schema)` Set the current schema to a new value.
`void`	`transaction(ContextTransactionalRunnable transactional)` Run a `ContextTransactionalRunnable` in the context of this `DSLContext`'s underlying `Scope.configuration()`'s `Configuration.transactionProvider()`.
`void`	`transaction(TransactionalRunnable transactional)` Run a `TransactionalRunnable` in the context of this `DSLContext`'s underlying `Scope.configuration()`'s `Configuration.transactionProvider()`.
`java.util.concurrent.CompletionStage<java.lang.Void>`	`transactionAsync(java.util.concurrent.Executor executor, TransactionalRunnable transactional)` Run a `TransactionalRunnable` asynchronously.
`java.util.concurrent.CompletionStage<java.lang.Void>`	`transactionAsync(TransactionalRunnable transactional)` Run a `TransactionalRunnable` asynchronously.
`<T> T`	`transactionResult(ContextTransactionalCallable<T> transactional)` Run a `ContextTransactionalRunnable` in the context of this `DSLContext`'s underlying `Scope.configuration()`'s `Configuration.transactionProvider()`, and return the `transactional`'s outcome.
`<T> T`	`transactionResult(TransactionalCallable<T> transactional)` Run a `TransactionalCallable` in the context of this `DSLContext`'s underlying `Scope.configuration()`'s `Configuration.transactionProvider()`, and return the `transactional`'s outcome.
`<T> java.util.concurrent.CompletionStage<T>`	`transactionResultAsync(java.util.concurrent.Executor executor, TransactionalCallable<T> transactional)` Run a `TransactionalCallable` asynchronously.
`<T> java.util.concurrent.CompletionStage<T>`	`transactionResultAsync(TransactionalCallable<T> transactional)` Run a `TransactionalCallable` asynchronously.
`TruncateIdentityStep<Record>`	`truncate(Name table)` Create a new DSL truncate statement.
`TruncateIdentityStep<Record>`	`truncate(java.lang.String table)` Create a new DSL truncate statement.
`<R extends Record> TruncateIdentityStep<R>`	`truncate(Table<R> table)` Create a new DSL truncate statement.
`<R extends Record> UpdateSetFirstStep<R>`	`update(Table<R> table)` Create a new DSL update statement.
`<R extends Record> UpdateQuery<R>`	`updateQuery(Table<R> table)` Create a new `UpdateQuery`
`WithStep`	`with(CommonTableExpression<?>... tables)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep`	`with(Name alias)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep`	`with(Name alias, Name... fieldAliases)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep1`	`with(Name alias, Name fieldAlias1)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep2`	`with(Name alias, Name fieldAlias1, Name fieldAlias2)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep3`	`with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep4`	`with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep5`	`with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep6`	`with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep7`	`with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep8`	`with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep9`	`with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep10`	`with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep11`	`with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep12`	`with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11, Name fieldAlias12)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep13`	`with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11, Name fieldAlias12, Name fieldAlias13)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep14`	`with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11, Name fieldAlias12, Name fieldAlias13, Name fieldAlias14)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep15`	`with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11, Name fieldAlias12, Name fieldAlias13, Name fieldAlias14, Name fieldAlias15)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep16`	`with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11, Name fieldAlias12, Name fieldAlias13, Name fieldAlias14, Name fieldAlias15, Name fieldAlias16)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep17`	`with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11, Name fieldAlias12, Name fieldAlias13, Name fieldAlias14, Name fieldAlias15, Name fieldAlias16, Name fieldAlias17)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep18`	`with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11, Name fieldAlias12, Name fieldAlias13, Name fieldAlias14, Name fieldAlias15, Name fieldAlias16, Name fieldAlias17, Name fieldAlias18)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep19`	`with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11, Name fieldAlias12, Name fieldAlias13, Name fieldAlias14, Name fieldAlias15, Name fieldAlias16, Name fieldAlias17, Name fieldAlias18, Name fieldAlias19)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep20`	`with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11, Name fieldAlias12, Name fieldAlias13, Name fieldAlias14, Name fieldAlias15, Name fieldAlias16, Name fieldAlias17, Name fieldAlias18, Name fieldAlias19, Name fieldAlias20)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep21`	`with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11, Name fieldAlias12, Name fieldAlias13, Name fieldAlias14, Name fieldAlias15, Name fieldAlias16, Name fieldAlias17, Name fieldAlias18, Name fieldAlias19, Name fieldAlias20, Name fieldAlias21)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep22`	`with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11, Name fieldAlias12, Name fieldAlias13, Name fieldAlias14, Name fieldAlias15, Name fieldAlias16, Name fieldAlias17, Name fieldAlias18, Name fieldAlias19, Name fieldAlias20, Name fieldAlias21, Name fieldAlias22)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep`	`with(java.lang.String alias)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep`	`with(java.lang.String alias, java.util.function.BiFunction<? super Field<?>,? super java.lang.Integer,? extends java.lang.String> fieldNameFunction)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep`	`with(java.lang.String alias, java.util.function.Function<? super Field<?>,? extends java.lang.String> fieldNameFunction)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep`	`with(java.lang.String alias, java.lang.String... fieldAliases)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep1`	`with(java.lang.String alias, java.lang.String fieldAlias1)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep2`	`with(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep3`	`with(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep4`	`with(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep5`	`with(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep6`	`with(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep7`	`with(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep8`	`with(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep9`	`with(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep10`	`with(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep11`	`with(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep12`	`with(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11, java.lang.String fieldAlias12)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep13`	`with(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11, java.lang.String fieldAlias12, java.lang.String fieldAlias13)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep14`	`with(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11, java.lang.String fieldAlias12, java.lang.String fieldAlias13, java.lang.String fieldAlias14)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep15`	`with(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11, java.lang.String fieldAlias12, java.lang.String fieldAlias13, java.lang.String fieldAlias14, java.lang.String fieldAlias15)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep16`	with(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11, java.lang.String fieldAlias12, java.lang.String fieldAlias13, java.lang.String fieldAlias14, java.lang.String fieldAlias15, java.lang.String fieldAlias16) Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep17`	with(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11, java.lang.String fieldAlias12, java.lang.String fieldAlias13, java.lang.String fieldAlias14, java.lang.String fieldAlias15, java.lang.String fieldAlias16, java.lang.String fieldAlias17) Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep18`	with(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11, java.lang.String fieldAlias12, java.lang.String fieldAlias13, java.lang.String fieldAlias14, java.lang.String fieldAlias15, java.lang.String fieldAlias16, java.lang.String fieldAlias17, java.lang.String fieldAlias18) Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep19`	with(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11, java.lang.String fieldAlias12, java.lang.String fieldAlias13, java.lang.String fieldAlias14, java.lang.String fieldAlias15, java.lang.String fieldAlias16, java.lang.String fieldAlias17, java.lang.String fieldAlias18, java.lang.String fieldAlias19) Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep20`	with(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11, java.lang.String fieldAlias12, java.lang.String fieldAlias13, java.lang.String fieldAlias14, java.lang.String fieldAlias15, java.lang.String fieldAlias16, java.lang.String fieldAlias17, java.lang.String fieldAlias18, java.lang.String fieldAlias19, java.lang.String fieldAlias20) Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep21`	with(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11, java.lang.String fieldAlias12, java.lang.String fieldAlias13, java.lang.String fieldAlias14, java.lang.String fieldAlias15, java.lang.String fieldAlias16, java.lang.String fieldAlias17, java.lang.String fieldAlias18, java.lang.String fieldAlias19, java.lang.String fieldAlias20, java.lang.String fieldAlias21) Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep22`	with(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11, java.lang.String fieldAlias12, java.lang.String fieldAlias13, java.lang.String fieldAlias14, java.lang.String fieldAlias15, java.lang.String fieldAlias16, java.lang.String fieldAlias17, java.lang.String fieldAlias18, java.lang.String fieldAlias19, java.lang.String fieldAlias20, java.lang.String fieldAlias21, java.lang.String fieldAlias22) Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithStep`	`withRecursive(CommonTableExpression<?>... tables)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep`	`withRecursive(Name alias)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep`	`withRecursive(Name alias, Name... fieldAliases)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep1`	`withRecursive(Name alias, Name fieldAlias1)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep2`	`withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep3`	`withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep4`	`withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep5`	`withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep6`	`withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep7`	`withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep8`	`withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep9`	`withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep10`	`withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep11`	`withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep12`	`withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11, Name fieldAlias12)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep13`	`withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11, Name fieldAlias12, Name fieldAlias13)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep14`	`withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11, Name fieldAlias12, Name fieldAlias13, Name fieldAlias14)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep15`	`withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11, Name fieldAlias12, Name fieldAlias13, Name fieldAlias14, Name fieldAlias15)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep16`	`withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11, Name fieldAlias12, Name fieldAlias13, Name fieldAlias14, Name fieldAlias15, Name fieldAlias16)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep17`	`withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11, Name fieldAlias12, Name fieldAlias13, Name fieldAlias14, Name fieldAlias15, Name fieldAlias16, Name fieldAlias17)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep18`	`withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11, Name fieldAlias12, Name fieldAlias13, Name fieldAlias14, Name fieldAlias15, Name fieldAlias16, Name fieldAlias17, Name fieldAlias18)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep19`	`withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11, Name fieldAlias12, Name fieldAlias13, Name fieldAlias14, Name fieldAlias15, Name fieldAlias16, Name fieldAlias17, Name fieldAlias18, Name fieldAlias19)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep20`	`withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11, Name fieldAlias12, Name fieldAlias13, Name fieldAlias14, Name fieldAlias15, Name fieldAlias16, Name fieldAlias17, Name fieldAlias18, Name fieldAlias19, Name fieldAlias20)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep21`	`withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11, Name fieldAlias12, Name fieldAlias13, Name fieldAlias14, Name fieldAlias15, Name fieldAlias16, Name fieldAlias17, Name fieldAlias18, Name fieldAlias19, Name fieldAlias20, Name fieldAlias21)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep22`	`withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10, Name fieldAlias11, Name fieldAlias12, Name fieldAlias13, Name fieldAlias14, Name fieldAlias15, Name fieldAlias16, Name fieldAlias17, Name fieldAlias18, Name fieldAlias19, Name fieldAlias20, Name fieldAlias21, Name fieldAlias22)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep`	`withRecursive(java.lang.String alias)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep`	`withRecursive(java.lang.String alias, java.util.function.BiFunction<? super Field<?>,? super java.lang.Integer,? extends java.lang.String> fieldNameFunction)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep`	`withRecursive(java.lang.String alias, java.util.function.Function<? super Field<?>,? extends java.lang.String> fieldNameFunction)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep`	`withRecursive(java.lang.String alias, java.lang.String... fieldAliases)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep1`	`withRecursive(java.lang.String alias, java.lang.String fieldAlias1)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep2`	`withRecursive(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep3`	`withRecursive(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep4`	`withRecursive(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep5`	`withRecursive(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep6`	`withRecursive(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep7`	`withRecursive(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep8`	`withRecursive(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep9`	`withRecursive(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep10`	`withRecursive(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep11`	`withRecursive(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep12`	`withRecursive(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11, java.lang.String fieldAlias12)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep13`	`withRecursive(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11, java.lang.String fieldAlias12, java.lang.String fieldAlias13)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep14`	`withRecursive(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11, java.lang.String fieldAlias12, java.lang.String fieldAlias13, java.lang.String fieldAlias14)` Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep15`	withRecursive(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11, java.lang.String fieldAlias12, java.lang.String fieldAlias13, java.lang.String fieldAlias14, java.lang.String fieldAlias15) Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep16`	withRecursive(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11, java.lang.String fieldAlias12, java.lang.String fieldAlias13, java.lang.String fieldAlias14, java.lang.String fieldAlias15, java.lang.String fieldAlias16) Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep17`	withRecursive(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11, java.lang.String fieldAlias12, java.lang.String fieldAlias13, java.lang.String fieldAlias14, java.lang.String fieldAlias15, java.lang.String fieldAlias16, java.lang.String fieldAlias17) Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep18`	withRecursive(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11, java.lang.String fieldAlias12, java.lang.String fieldAlias13, java.lang.String fieldAlias14, java.lang.String fieldAlias15, java.lang.String fieldAlias16, java.lang.String fieldAlias17, java.lang.String fieldAlias18) Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep19`	withRecursive(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11, java.lang.String fieldAlias12, java.lang.String fieldAlias13, java.lang.String fieldAlias14, java.lang.String fieldAlias15, java.lang.String fieldAlias16, java.lang.String fieldAlias17, java.lang.String fieldAlias18, java.lang.String fieldAlias19) Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep20`	withRecursive(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11, java.lang.String fieldAlias12, java.lang.String fieldAlias13, java.lang.String fieldAlias14, java.lang.String fieldAlias15, java.lang.String fieldAlias16, java.lang.String fieldAlias17, java.lang.String fieldAlias18, java.lang.String fieldAlias19, java.lang.String fieldAlias20) Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep21`	withRecursive(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11, java.lang.String fieldAlias12, java.lang.String fieldAlias13, java.lang.String fieldAlias14, java.lang.String fieldAlias15, java.lang.String fieldAlias16, java.lang.String fieldAlias17, java.lang.String fieldAlias18, java.lang.String fieldAlias19, java.lang.String fieldAlias20, java.lang.String fieldAlias21) Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.
`WithAsStep22`	withRecursive(java.lang.String alias, java.lang.String fieldAlias1, java.lang.String fieldAlias2, java.lang.String fieldAlias3, java.lang.String fieldAlias4, java.lang.String fieldAlias5, java.lang.String fieldAlias6, java.lang.String fieldAlias7, java.lang.String fieldAlias8, java.lang.String fieldAlias9, java.lang.String fieldAlias10, java.lang.String fieldAlias11, java.lang.String fieldAlias12, java.lang.String fieldAlias13, java.lang.String fieldAlias14, java.lang.String fieldAlias15, java.lang.String fieldAlias16, java.lang.String fieldAlias17, java.lang.String fieldAlias18, java.lang.String fieldAlias19, java.lang.String fieldAlias20, java.lang.String fieldAlias21, java.lang.String fieldAlias22) Create a `WITH` clause to supply subsequent `SELECT`, `UPDATE`, `INSERT`, `DELETE`, and `MERGE` statements with `CommonTableExpression`s.

Methods inherited from interface org.jooq.Scope
configuration, data, data, data, dialect, dsl, family, settings

Method Detail

close
```
void close()
    throws DataAccessException
```
Close the underlying resources, if any resources have been allocated when constructing this DSLContext.
Some DSLContext constructors, such as DSL.using(String), DSL.using(String, Properties), or DSL.using(String, String, String) allocate a Connection resource, which is inaccessible to the outside of the DSLContext implementation. Proper resource management must thus be done via this close() method.

Specified by:

close in interface java.lang.AutoCloseable

Throws:

DataAccessException - When something went wrong closing the underlying resources.

map
```
Schema map(Schema schema)
```
Map a schema to another one.
This will map a schema onto another one, depending on configured schema mapping in this DSLContext. If no applicable schema mapping can be found, the schema itself is returned.

Parameters:

schema - A schema

Returns:

The mapped schema

map
```
<R extends Record> Table<R> map(Table<R> table)
```
Map a table to another one.
This will map a table onto another one, depending on configured table mapping in this DSLContext. If no applicable table mapping can be found, the table itself is returned.

Parameters:

table - A table

Returns:

The mapped table

parser
```
Parser parser()
```
Access the parser API.
This is experimental functionality.

parsingConnection
```
java.sql.Connection parsingConnection()
```
A JDBC connection that runs each statement through the parser() first, prior to re-generating and running the SQL.
The resulting Connection wraps an underlying JDBC connection that has been obtained from ConnectionProvider.acquire() and must be released by calling Connection.close().
This is experimental functionality:
- While this works well for static Statement executions, bind variables and their position calculation might cause issues when the generated SQL output involves more complex SQL transformation. See also https://github.com/jOOQ/jOOQ/issues/5759.
- Batching statements is currently not supported. See also https://github.com/jOOQ/jOOQ/issues/5757.

meta
```
Meta meta()
```
Access the database meta data.
This method returns a wrapper type that gives access to your JDBC connection's database meta data.

meta
```
Meta meta(InformationSchema schema)
```
Access the databse meta data from its serialised form.

informationSchema
```
InformationSchema informationSchema(Catalog catalog)
```
Export a catalog to the InformationSchema format.
This allows for serialising schema meta information as XML using JAXB. See also Constants.XSD_META for details.

informationSchema
```
InformationSchema informationSchema(Catalog... catalogs)
```
Export a set of catalogs to the InformationSchema format.
This allows for serialising schema meta information as XML using JAXB. See also Constants.XSD_META for details.

informationSchema
```
InformationSchema informationSchema(Schema schema)
```
Export a schema to the InformationSchema format.
This allows for serialising schema meta information as XML using JAXB. See also Constants.XSD_META for details.

informationSchema
```
InformationSchema informationSchema(Schema... schemas)
```
Export a set of schemas to the InformationSchema format.
This allows for serialising schema meta information as XML using JAXB. See also Constants.XSD_META for details.

informationSchema
```
InformationSchema informationSchema(Table<?> table)
```
Export a table to the InformationSchema format.
Exporting a single table will not include any foreign key definitions in the exported data.
This allows for serialising schema meta information as XML using JAXB. See also Constants.XSD_META for details.

informationSchema
```
InformationSchema informationSchema(Table<?>... table)
```
Export a set of tables to the InformationSchema format.
Only those foreign keys whose referenced table is also included in the export will be exported.
This allows for serialising schema meta information as XML using JAXB. See also Constants.XSD_META for details.

transactionResult
```
<T> T transactionResult(TransactionalCallable<T> transactional)
```
Run a TransactionalCallable in the context of this DSLContext's underlying Scope.configuration()'s Configuration.transactionProvider(), and return the transactional's outcome.
The argument transactional code should not capture any scope but derive its Configuration from the TransactionalCallable.run(Configuration) argument in order to create new statements.

Parameters:

transactional - The transactional code

Returns:

The transactional outcome

Throws:

java.lang.RuntimeException - any runtime exception thrown by the transactional logic, indicating that a rollback has occurred.

DataAccessException - any database problem that may have arised when executing the transactional logic, or a wrapper for any checked exception thrown by the transactional logic, indicating that a rollback has occurred.

transactionResult
```
<T> T transactionResult(ContextTransactionalCallable<T> transactional)
                 throws ConfigurationException
```
Run a ContextTransactionalRunnable in the context of this DSLContext's underlying Scope.configuration()'s Configuration.transactionProvider(), and return the transactional's outcome.
The argument transactional code may capture scope to derive its Configuration from the "context" in order to create new statements. This context can be provided, for instance, by ThreadLocalTransactionProvider automatically.

Parameters:

transactional - The transactional code

Returns:

The transactional outcome

Throws:

ConfigurationException - if the underlying Configuration.transactionProvider() is not able to provide context (i.e. currently, it is not a ThreadLocalTransactionProvider).

java.lang.RuntimeException - any runtime exception thrown by the transactional logic, indicating that a rollback has occurred.

DataAccessException - any database problem that may have arised when executing the transactional logic, or a wrapper for any checked exception thrown by the transactional logic, indicating that a rollback has occurred.

transaction
```
void transaction(TransactionalRunnable transactional)
```
Run a TransactionalRunnable in the context of this DSLContext's underlying Scope.configuration()'s Configuration.transactionProvider().
The argument transactional code should not capture any scope but derive its Configuration from the TransactionalCallable.run(Configuration) argument in order to create new statements.

Parameters:

transactional - The transactional code

Throws:

java.lang.RuntimeException - any runtime exception thrown by the transactional logic, indicating that a rollback has occurred.

DataAccessException - any database problem that may have arised when executing the transactional logic, or a wrapper for any checked exception thrown by the transactional logic, indicating that a rollback has occurred.

transaction
```
void transaction(ContextTransactionalRunnable transactional)
          throws ConfigurationException
```
Run a ContextTransactionalRunnable in the context of this DSLContext's underlying Scope.configuration()'s Configuration.transactionProvider().
The argument transactional code may capture scope to derive its Configuration from the "context" in order to create new statements. This context can be provided, for instance, by ThreadLocalTransactionProvider automatically.

Parameters:

transactional - The transactional code

Throws:

ConfigurationException - if the underlying Configuration.transactionProvider() is not able to provide context (i.e. currently, it is not a ThreadLocalTransactionProvider).

java.lang.RuntimeException - any runtime exception thrown by the transactional logic, indicating that a rollback has occurred.

DataAccessException - any database problem that may have arised when executing the transactional logic, or a wrapper for any checked exception thrown by the transactional logic, indicating that a rollback has occurred.

transactionResultAsync
```
<T> java.util.concurrent.CompletionStage<T> transactionResultAsync(TransactionalCallable<T> transactional)
                                                            throws ConfigurationException
```
Run a TransactionalCallable asynchronously.
The TransactionCallable is run in the context of this DSLContext's underlying Scope.configuration()'s Configuration.transactionProvider(), and returns the transactional's outcome in a new CompletionStage that is asynchronously completed by a task run by an Executor provided by the underlying Scope.configuration()'s Configuration.executorProvider().

Parameters:

transactional - The transactional code

Returns:

The transactional outcome

Throws:

ConfigurationException - If this is run with a ThreadLocalTransactionProvider.

transactionAsync
```
java.util.concurrent.CompletionStage<java.lang.Void> transactionAsync(TransactionalRunnable transactional)
                                                               throws ConfigurationException
```
Run a TransactionalRunnable asynchronously.
The TransactionRunnable is run in the context of this DSLContext's underlying Scope.configuration()'s Configuration.transactionProvider(), and returns the transactional's outcome in a new CompletionStage that is asynchronously completed by a task run by an Executor provided by the underlying Scope.configuration()'s Configuration.executorProvider().

Parameters:

transactional - The transactional code

Throws:

ConfigurationException - If this is run with a ThreadLocalTransactionProvider.

transactionResultAsync
```
<T> java.util.concurrent.CompletionStage<T> transactionResultAsync(java.util.concurrent.Executor executor,
                                                                   TransactionalCallable<T> transactional)
                                                            throws ConfigurationException
```
Run a TransactionalCallable asynchronously.
The TransactionCallable is run in the context of this DSLContext's underlying Scope.configuration()'s Configuration.transactionProvider(), and returns the transactional's outcome in a new CompletionStage that is asynchronously completed by a task run by a given Executor.

Parameters:

transactional - The transactional code

Returns:

The transactional outcome

Throws:

ConfigurationException - If this is run with a ThreadLocalTransactionProvider.

transactionAsync
```
java.util.concurrent.CompletionStage<java.lang.Void> transactionAsync(java.util.concurrent.Executor executor,
                                                                      TransactionalRunnable transactional)
                                                               throws ConfigurationException
```
Run a TransactionalRunnable asynchronously.
The TransactionRunnable is run in the context of this DSLContext's underlying Scope.configuration()'s Configuration.transactionProvider(), and returns the transactional's outcome in a new CompletionStage that is asynchronously completed by a task run by a given Executor.

Parameters:

transactional - The transactional code

Throws:

ConfigurationException - If this is run with a ThreadLocalTransactionProvider.

connectionResult
```
<T> T connectionResult(ConnectionCallable<T> callable)
```
Run a ConnectionCallable in the context of this DSLContext's underlying Scope.configuration()'s Configuration.connectionProvider().

Parameters:

callable - The code running statements against the connection.

Returns:

The outcome of the callable

connection
```
void connection(ConnectionRunnable runnable)
```
Run a ConnectionRunnable in the context of this DSLContext's underlying Scope.configuration()'s Configuration.connectionProvider().

Parameters:

runnable - The code running statements against the connection.

mockResult
```
<T> T mockResult(MockDataProvider provider,
                 MockCallable<T> mockable)
```
Run a MockRunnable in the context of this DSLContext 's underlying Scope.configuration()'s, and of a MockDataProvider and return the mockable's outcome.

mock
```
void mock(MockDataProvider provider,
          MockRunnable mockable)
```
Run a MockRunnable in the context of this DSLContext 's underlying Scope.configuration()'s, and of a MockDataProvider.

renderContext
```
@Deprecated
RenderContext renderContext()
```
Deprecated. - [#6280] - 3.10 - Do not reuse this method. It will be completely internal with jOOQ 4.0
Get a new RenderContext for the context of this DSLContext.
This will return an initialised render context as such:
- RenderContext.castMode() == DEFAULT
- Context.declareFields() == false
- Context.declareTables() == false
- RenderContext.format() == false
- RenderContext.paramType() == ParamType.INDEXED
- RenderContext.qualify() == true
- Context.subquery() == false

render
```
java.lang.String render(QueryPart part)
```
Render a QueryPart in the context of this DSLContext.
This is the same as calling renderContext().render(part)

Parameters:

part - The QueryPart to be rendered

Returns:

The rendered SQL

renderNamedParams
```
java.lang.String renderNamedParams(QueryPart part)
```
Render a QueryPart in the context of this DSLContext, rendering bind variables as named parameters.
This is the same as calling renderContext().paramType(NAMED).render(part)

Parameters:

part - The QueryPart to be rendered

Returns:

The rendered SQL

renderNamedOrInlinedParams
```
java.lang.String renderNamedOrInlinedParams(QueryPart part)
```
Render a QueryPart in the context of this DSLContext, rendering bind variables as named parameters, or inlined parameters if they have no name.
This is the same as calling renderContext().paramType(NAMED_OR_INLINED).render(part)

Parameters:

part - The QueryPart to be rendered

Returns:

The rendered SQL

renderInlined
```
java.lang.String renderInlined(QueryPart part)
```
Render a QueryPart in the context of this DSLContext, inlining all bind variables.
This is the same as calling renderContext().inline(true).render(part)

Parameters:

part - The QueryPart to be rendered

Returns:

The rendered SQL

extractBindValues
```
java.util.List<java.lang.Object> extractBindValues(QueryPart part)
```
Retrieve the bind values that will be bound by a given QueryPart.
The returned List is immutable. To modify bind values, use extractParams(QueryPart) instead.
Unlike extractParams(QueryPart), which returns also inlined parameters, this returns only actual bind values that will render an actual bind value as a question mark "?"

extractParams
```
java.util.Map<java.lang.String,Param<?>> extractParams(QueryPart part)
```
Get a Map of named parameters.
The Map itself is immutable, but the Param elements allow for modifying bind values on an existing Query (or any other QueryPart).
Bind values created with DSL.val(Object) will have their bind index as name.

See Also:

Param, DSL.param(String, Object)

extractParam
```
Param<?> extractParam(QueryPart part,
                      java.lang.String name)
```
Get a named parameter from a QueryPart, provided its name.
Bind values created with DSL.val(Object) will have their bind index as name.

See Also:

Param, DSL.param(String, Object)

bindContext
```
@Deprecated
BindContext bindContext(java.sql.PreparedStatement stmt)
```
Deprecated. - [#6280] - 3.10 - Do not reuse this method. It will be completely internal with jOOQ 4.0
Get a new BindContext for the context of this DSLContext.
This will return an initialised bind context as such:
- Context.declareFields() == false
- Context.declareTables() == false
BindContext for JOOQ INTERNAL USE only. Avoid referencing it directly

bind
```
@Deprecated
int bind(QueryPart part,
                      java.sql.PreparedStatement stmt)
```
Deprecated. - [#2662] - 3.2.0 - Do not reuse this method. It will be removed with jOOQ 4.0

attach
```
void attach(Attachable... attachables)
```
Attach this DSLContext's underlying Scope.configuration() to some attachables.

attach
```
void attach(java.util.Collection<? extends Attachable> attachables)
```
Attach this DSLContext's underlying Scope.configuration() to some attachables.

loadInto

@Support
<R extends Record> LoaderOptionsStep<R> loadInto(Table<R> table)

Create a new Loader object to load data from a CSV or XML source.

queries
```
@Support
Queries queries(Query... queries)
```
Wrap a collection of queries.

See Also:

DSL.queries(Query...)

queries

@Support
Queries queries(java.util.Collection<? extends Query> queries)

Wrap a collection of queries.

See Also:: DSL.queries(Collection)

query
```
@Support
 @PlainSQL
Query query(SQL sql)
```
Create a new query holding plain SQL. There must not be any binding variables contained in the SQL.
Example:
```
 String sql = "SET SCHEMA 'abc'";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

A query wrapping the plain SQL

See Also:

SQL

query
```
@Support
 @PlainSQL
Query query(java.lang.String sql)
```
Create a new query holding plain SQL. There must not be any binding variables contained in the SQL.
Example:
```
 String sql = "SET SCHEMA 'abc'";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

A query wrapping the plain SQL

See Also:

SQL

query
```
@Support
 @PlainSQL
Query query(java.lang.String sql,
                                  java.lang.Object... bindings)
```
Create a new query holding plain SQL. There must be as many bind variables contained in the SQL, as passed in the bindings parameter.
Example:
```
 String sql = "SET SCHEMA 'abc'";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

bindings - The bindings

Returns:

A query wrapping the plain SQL

See Also:

SQL, DSL.sql(String, Object...)

query
```
@Support
 @PlainSQL
Query query(java.lang.String sql,
                                  QueryPart... parts)
```
Create a new query holding plain SQL.
Unlike query(String, Object...), the SQL passed to this method should not contain any bind variables. Instead, you can pass QueryPart objects to the method which will be rendered at indexed locations of your SQL string as such:
```
 // The following query
 query("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));

 // Will render this SQL on an Oracle database with RenderNameStyle.QUOTED:
 select ?, 'test' from "DUAL"
 
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses! One way to escape literals is to use DSL.name(String...) and similar methods
Parameters:

sql - The SQL clause, containing {numbered placeholders} where query parts can be injected

parts - The QueryPart objects that are rendered at the {numbered placeholder} locations

Returns:

A query wrapping the plain SQL

See Also:

SQL, DSL.sql(String, QueryPart...)

fetch
```
@Support
 @PlainSQL
Result<Record> fetch(SQL sql)
                                    throws DataAccessException
```
Execute a new query holding plain SQL.
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The results from the executed query. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL

fetch
```
@Support
 @PlainSQL
Result<Record> fetch(java.lang.String sql)
                                    throws DataAccessException
```
Execute a new query holding plain SQL.
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The results from the executed query. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL

fetch
```
@Support
 @PlainSQL
Result<Record> fetch(java.lang.String sql,
                                           java.lang.Object... bindings)
                                    throws DataAccessException
```
Execute a new query holding plain SQL.
There must be as many bind variables contained in the SQL, as passed in the bindings parameter
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

bindings - The bindings

Returns:

The results from the executed query. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL, DSL.sql(String, Object...)

fetch
```
@Support
 @PlainSQL
Result<Record> fetch(java.lang.String sql,
                                           QueryPart... parts)
                                    throws DataAccessException
```
Execute a new query holding plain SQL.
Unlike fetch(String, Object...), the SQL passed to this method should not contain any bind variables. Instead, you can pass QueryPart objects to the method which will be rendered at indexed locations of your SQL string as such:
```
 // The following query
 fetch("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));

 // Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
 select ?, 'test' from "DUAL"
 
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses! One way to escape literals is to use DSL.name(String...) and similar methods
Parameters:

sql - The SQL clause, containing {numbered placeholders} where query parts can be injected

parts - The QueryPart objects that are rendered at the {numbered placeholder} locations

Returns:

The results from the executed query. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL, DSL.sql(String, QueryPart...)

fetchLazy
```
@Support
 @PlainSQL
Cursor<Record> fetchLazy(SQL sql)
                                        throws DataAccessException
```
Execute a new query holding plain SQL and "lazily" return the generated result.
The returned Cursor holds a reference to the executed PreparedStatement and the associated ResultSet. Data can be fetched (or iterated over) lazily, fetching records from the ResultSet one by one.
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The cursor. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL

fetchLazy
```
@Support
 @PlainSQL
Cursor<Record> fetchLazy(java.lang.String sql)
                                        throws DataAccessException
```
Execute a new query holding plain SQL and "lazily" return the generated result.
The returned Cursor holds a reference to the executed PreparedStatement and the associated ResultSet. Data can be fetched (or iterated over) lazily, fetching records from the ResultSet one by one.
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The cursor. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL

fetchLazy
```
@Support
 @PlainSQL
Cursor<Record> fetchLazy(java.lang.String sql,
                                               java.lang.Object... bindings)
                                        throws DataAccessException
```
Execute a new query holding plain SQL and "lazily" return the generated result.
There must be as many bind variables contained in the SQL, as passed in the bindings parameter
The returned Cursor holds a reference to the executed PreparedStatement and the associated ResultSet. Data can be fetched (or iterated over) lazily, fetching records from the ResultSet one by one.
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

bindings - The bindings

Returns:

The cursor. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL, DSL.sql(String, Object...)

fetchLazy
```
@Support
 @PlainSQL
Cursor<Record> fetchLazy(java.lang.String sql,
                                               QueryPart... parts)
                                        throws DataAccessException
```
Execute a new query holding plain SQL and "lazily" return the generated result.
The returned Cursor holds a reference to the executed PreparedStatement and the associated ResultSet. Data can be fetched (or iterated over) lazily, fetching records from the ResultSet one by one.
Unlike fetchLazy(String, Object...), the SQL passed to this method should not contain any bind variables. Instead, you can pass QueryPart objects to the method which will be rendered at indexed locations of your SQL string as such:
```
 // The following query
 fetchLazy("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));

 // Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
 select ?, 'test' from "DUAL"
 
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses! One way to escape literals is to use DSL.name(String...) and similar methods
Parameters:

sql - The SQL clause, containing {numbered placeholders} where query parts can be injected

parts - The QueryPart objects that are rendered at the {numbered placeholder} locations

Returns:

The cursor. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL, DSL.sql(String, QueryPart...)

fetchAsync
```
@Support
 @PlainSQL
java.util.concurrent.CompletionStage<Result<Record>> fetchAsync(SQL sql)
```
Fetch results in a new CompletionStage.
The result is asynchronously completed by a task running in an Executor provided by the Scope.configuration()'s Configuration.executorProvider().
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The completion stage. The completed result will never be null.

See Also:

SQL

fetchAsync
```
@Support
 @PlainSQL
java.util.concurrent.CompletionStage<Result<Record>> fetchAsync(java.lang.String sql)
```
Fetch results in a new CompletionStage.
The result is asynchronously completed by a task running in an Executor provided by the Scope.configuration()'s Configuration.executorProvider().
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The completion stage. The completed result will never be null.

See Also:

SQL

fetchAsync
```
@Support
 @PlainSQL
java.util.concurrent.CompletionStage<Result<Record>> fetchAsync(java.lang.String sql,
                                                                                      java.lang.Object... bindings)
```
Fetch results in a new CompletionStage.
The result is asynchronously completed by a task running in an Executor provided by the Scope.configuration()'s Configuration.executorProvider().
There must be as many bind variables contained in the SQL, as passed in the bindings parameter
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

bindings - The bindings

Returns:

The completion stage. The completed result will never be null.

See Also:

SQL, DSL.sql(String, Object...)

fetchAsync
```
@Support
 @PlainSQL
java.util.concurrent.CompletionStage<Result<Record>> fetchAsync(java.lang.String sql,
                                                                                      QueryPart... parts)
```
Fetch results in a new CompletionStage.
The result is asynchronously completed by a task running in an Executor provided by the Scope.configuration()'s Configuration.executorProvider().
Unlike fetchLazy(String, Object...), the SQL passed to this method should not contain any bind variables. Instead, you can pass QueryPart objects to the method which will be rendered at indexed locations of your SQL string as such:
```
 // The following query
 fetchLazy("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));

 // Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
 select ?, 'test' from "DUAL"
 
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses! One way to escape literals is to use DSL.name(String...) and similar methods
Parameters:

sql - The SQL clause, containing {numbered placeholders} where query parts can be injected

parts - The QueryPart objects that are rendered at the {numbered placeholder} locations

Returns:

The completion stage. The completed result will never be null.

See Also:

SQL, DSL.sql(String, QueryPart...)

fetchAsync
```
@Support
 @PlainSQL
java.util.concurrent.CompletionStage<Result<Record>> fetchAsync(java.util.concurrent.Executor executor,
                                                                                      SQL sql)
```
Fetch results in a new CompletionStage that is asynchronously completed by a task running in the given executor.
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The completion stage. The completed result will never be null.

See Also:

SQL

fetchAsync
```
@Support
 @PlainSQL
java.util.concurrent.CompletionStage<Result<Record>> fetchAsync(java.util.concurrent.Executor executor,
                                                                                      java.lang.String sql)
```
Fetch results in a new CompletionStage that is asynchronously completed by a task running in the given executor.
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The completion stage. The completed result will never be null.

See Also:

SQL

fetchAsync
```
@Support
 @PlainSQL
java.util.concurrent.CompletionStage<Result<Record>> fetchAsync(java.util.concurrent.Executor executor,
                                                                                      java.lang.String sql,
                                                                                      java.lang.Object... bindings)
```
Fetch results in a new CompletionStage that is asynchronously completed by a task running in the given executor.
There must be as many bind variables contained in the SQL, as passed in the bindings parameter
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

bindings - The bindings

Returns:

The completion stage. The completed result will never be null.

See Also:

SQL, DSL.sql(String, Object...)

fetchAsync
```
@Support
 @PlainSQL
java.util.concurrent.CompletionStage<Result<Record>> fetchAsync(java.util.concurrent.Executor executor,
                                                                                      java.lang.String sql,
                                                                                      QueryPart... parts)
```
Fetch results in a new CompletionStage that is asynchronously completed by a task running in the given executor.
Unlike fetchLazy(String, Object...), the SQL passed to this method should not contain any bind variables. Instead, you can pass QueryPart objects to the method which will be rendered at indexed locations of your SQL string as such:
```
 // The following query
 fetchLazy("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));

 // Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
 select ?, 'test' from "DUAL"
 
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses! One way to escape literals is to use DSL.name(String...) and similar methods
Parameters:

sql - The SQL clause, containing {numbered placeholders} where query parts can be injected

parts - The QueryPart objects that are rendered at the {numbered placeholder} locations

Returns:

The completion stage. The completed result will never be null.

See Also:

SQL, DSL.sql(String, QueryPart...)

fetchStream
```
@Support
 @PlainSQL
java.util.stream.Stream<Record> fetchStream(SQL sql)
                                                           throws DataAccessException
```
Execute a new query holding plain SQL and "lazily" return the generated result.
The returned Stream holds a reference to the executed PreparedStatement and the associated ResultSet. Data can be fetched (or iterated over) lazily, fetching records from the ResultSet one by one.
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The results from the executed query. This is never null, even if the database returns no ResultSet

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL

fetchStream
```
@Support
 @PlainSQL
java.util.stream.Stream<Record> fetchStream(java.lang.String sql)
                                                           throws DataAccessException
```
Execute a new query holding plain SQL and "lazily" return the generated result.
The returned Stream holds a reference to the executed PreparedStatement and the associated ResultSet. Data can be fetched (or iterated over) lazily, fetching records from the ResultSet one by one.
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The results from the executed query. This is never null, even if the database returns no ResultSet

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL

fetchStream
```
@Support
 @PlainSQL
java.util.stream.Stream<Record> fetchStream(java.lang.String sql,
                                                                  java.lang.Object... bindings)
                                                           throws DataAccessException
```
Execute a new query holding plain SQL and "lazily" return the generated result.
There must be as many bind variables contained in the SQL, as passed in the bindings parameter
The returned Stream holds a reference to the executed PreparedStatement and the associated ResultSet. Data can be fetched (or iterated over) lazily, fetching records from the ResultSet one by one.
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

bindings - The bindings

Returns:

The results from the executed query. This is never null, even if the database returns no ResultSet

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL, DSL.sql(String, Object...)

fetchStream
```
@Support
 @PlainSQL
java.util.stream.Stream<Record> fetchStream(java.lang.String sql,
                                                                  QueryPart... parts)
                                                           throws DataAccessException
```
Execute a new query holding plain SQL and "lazily" return the generated result.
The returned Stream holds a reference to the executed PreparedStatement and the associated ResultSet. Data can be fetched (or iterated over) lazily, fetching records from the ResultSet one by one.
Unlike fetchStream(String, Object...), the SQL passed to this method should not contain any bind variables. Instead, you can pass QueryPart objects to the method which will be rendered at indexed locations of your SQL string as such:
```
 // The following query
 fetchLazy("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));

 // Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
 select ?, 'test' from "DUAL"
 
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses! One way to escape literals is to use DSL.name(String...) and similar methods
Parameters:

sql - The SQL clause, containing {numbered placeholders} where query parts can be injected

parts - The QueryPart objects that are rendered at the {numbered placeholder} locations

Returns:

The results from the executed query. This is never null, even if the database returns no ResultSet

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL, DSL.sql(String, QueryPart...)

fetchMany
```
@Support
 @PlainSQL
Results fetchMany(SQL sql)
                                 throws DataAccessException
```
Execute a new query holding plain SQL, possibly returning several result sets.
Example (Sybase ASE):
```
 String sql = "sp_help 'my_table'";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The results. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL

fetchMany
```
@Support
 @PlainSQL
Results fetchMany(java.lang.String sql)
                                 throws DataAccessException
```
Execute a new query holding plain SQL, possibly returning several result sets.
Example (Sybase ASE):
```
 String sql = "sp_help 'my_table'";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The results. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL

fetchMany
```
@Support
 @PlainSQL
Results fetchMany(java.lang.String sql,
                                        java.lang.Object... bindings)
                                 throws DataAccessException
```
Execute a new query holding plain SQL, possibly returning several result sets.
There must be as many bind variables contained in the SQL, as passed in the bindings parameter
Example (Sybase ASE):
```
 String sql = "sp_help 'my_table'";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

bindings - The bindings

Returns:

The results. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL, DSL.sql(String, Object...)

fetchMany
```
@Support
 @PlainSQL
Results fetchMany(java.lang.String sql,
                                        QueryPart... parts)
                                 throws DataAccessException
```
Execute a new query holding plain SQL, possibly returning several result sets.
Unlike fetchMany(String, Object...), the SQL passed to this method should not contain any bind variables. Instead, you can pass QueryPart objects to the method which will be rendered at indexed locations of your SQL string as such:
```
 // The following query
 fetchMany("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));

 // Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
 select ?, 'test' from "DUAL"
 
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses! One way to escape literals is to use DSL.name(String...) and similar methods
Parameters:

sql - The SQL clause, containing {numbered placeholders} where query parts can be injected

parts - The QueryPart objects that are rendered at the {numbered placeholder} locations

Returns:

The results. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL, DSL.sql(String, QueryPart...)

fetchOne
```
@Support
 @PlainSQL
Record fetchOne(SQL sql)
                               throws DataAccessException,
                                      TooManyRowsException
```
Execute a new query holding plain SQL.
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The record or null, if no record was found.

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

See Also:

SQL

fetchOne
```
@Support
 @PlainSQL
Record fetchOne(java.lang.String sql)
                               throws DataAccessException,
                                      TooManyRowsException
```
Execute a new query holding plain SQL.
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The record or null, if no record was found.

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

See Also:

SQL

fetchOne
```
@Support
 @PlainSQL
Record fetchOne(java.lang.String sql,
                                      java.lang.Object... bindings)
                               throws DataAccessException,
                                      TooManyRowsException
```
Execute a new query holding plain SQL.
There must be as many bind variables contained in the SQL, as passed in the bindings parameter
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

bindings - The bindings

Returns:

The record or null, if no record was found.

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

See Also:

SQL, DSL.sql(String, Object...)

fetchOne
```
@Support
 @PlainSQL
Record fetchOne(java.lang.String sql,
                                      QueryPart... parts)
                               throws DataAccessException,
                                      TooManyRowsException
```
Execute a new query holding plain SQL.
Unlike fetchOne(String, Object...), the SQL passed to this method should not contain any bind variables. Instead, you can pass QueryPart objects to the method which will be rendered at indexed locations of your SQL string as such:
```
 // The following query
 fetchOne("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));

 // Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
 select ?, 'test' from "DUAL"
 
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses! One way to escape literals is to use DSL.name(String...) and similar methods
Parameters:

sql - The SQL clause, containing {numbered placeholders} where query parts can be injected

parts - The QueryPart objects that are rendered at the {numbered placeholder} locations

Returns:

The record or null, if no record was found.

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

See Also:

SQL, DSL.sql(String, QueryPart...)

fetchSingle
```
@Support
 @PlainSQL
Record fetchSingle(SQL sql)
                                  throws DataAccessException,
                                         NoDataFoundException,
                                         TooManyRowsException
```
Execute a new query holding plain SQL.
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The record. This is never null.

Throws:

DataAccessException - if something went wrong executing the query

NoDataFoundException - if the query returned no rows

TooManyRowsException - if the query returned more than one record

See Also:

SQL

fetchSingle
```
@Support
 @PlainSQL
Record fetchSingle(java.lang.String sql)
                                  throws DataAccessException,
                                         NoDataFoundException,
                                         TooManyRowsException
```
Execute a new query holding plain SQL.
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The record. This is never null.

Throws:

DataAccessException - if something went wrong executing the query

NoDataFoundException - if the query returned no rows

TooManyRowsException - if the query returned more than one record

See Also:

SQL

fetchSingle
```
@Support
 @PlainSQL
Record fetchSingle(java.lang.String sql,
                                         java.lang.Object... bindings)
                                  throws DataAccessException,
                                         NoDataFoundException,
                                         TooManyRowsException
```
Execute a new query holding plain SQL.
There must be as many bind variables contained in the SQL, as passed in the bindings parameter
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

bindings - The bindings

Returns:

The record. This is never null.

Throws:

DataAccessException - if something went wrong executing the query

NoDataFoundException - if the query returned no rows

TooManyRowsException - if the query returned more than one record

See Also:

SQL, DSL.sql(String, Object...)

fetchSingle
```
@Support
 @PlainSQL
Record fetchSingle(java.lang.String sql,
                                         QueryPart... parts)
                                  throws DataAccessException,
                                         NoDataFoundException,
                                         TooManyRowsException
```
Execute a new query holding plain SQL.
Unlike fetchOne(String, Object...), the SQL passed to this method should not contain any bind variables. Instead, you can pass QueryPart objects to the method which will be rendered at indexed locations of your SQL string as such:
```
 // The following query
 fetchOne("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));

 // Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
 select ?, 'test' from "DUAL"
 
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses! One way to escape literals is to use DSL.name(String...) and similar methods
Parameters:

sql - The SQL clause, containing {numbered placeholders} where query parts can be injected

parts - The QueryPart objects that are rendered at the {numbered placeholder} locations

Returns:

The record. This is never null.

Throws:

DataAccessException - if something went wrong executing the query

NoDataFoundException - if the query returned no rows

TooManyRowsException - if the query returned more than one record

See Also:

SQL, DSL.sql(String, QueryPart...)

fetchOptional
```
@Support
 @PlainSQL
java.util.Optional<Record> fetchOptional(SQL sql)
                                                        throws DataAccessException,
                                                               TooManyRowsException
```
Execute a new query holding plain SQL.
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The results from the executed query

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

See Also:

SQL

fetchOptional
```
@Support
 @PlainSQL
java.util.Optional<Record> fetchOptional(java.lang.String sql)
                                                        throws DataAccessException,
                                                               TooManyRowsException
```
Execute a new query holding plain SQL.
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The results from the executed query

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

See Also:

SQL

fetchOptional
```
@Support
 @PlainSQL
java.util.Optional<Record> fetchOptional(java.lang.String sql,
                                                               java.lang.Object... bindings)
                                                        throws DataAccessException,
                                                               TooManyRowsException
```
Execute a new query holding plain SQL.
There must be as many bind variables contained in the SQL, as passed in the bindings parameter
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

bindings - The bindings

Returns:

The results from the executed query

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

See Also:

SQL, DSL.sql(String, Object...)

fetchOptional
```
@Support
 @PlainSQL
java.util.Optional<Record> fetchOptional(java.lang.String sql,
                                                               QueryPart... parts)
                                                        throws DataAccessException,
                                                               TooManyRowsException
```
Execute a new query holding plain SQL.
Unlike fetchOne(String, Object...), the SQL passed to this method should not contain any bind variables. Instead, you can pass QueryPart objects to the method which will be rendered at indexed locations of your SQL string as such:
```
 // The following query
 fetchOne("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));

 // Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
 select ?, 'test' from "DUAL"
 
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses! One way to escape literals is to use DSL.name(String...) and similar methods
Parameters:

sql - The SQL clause, containing {numbered placeholders} where query parts can be injected

parts - The QueryPart objects that are rendered at the {numbered placeholder} locations

Returns:

The results from the executed query

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

See Also:

SQL, DSL.sql(String, QueryPart...)

fetchValue
```
@Support
 @PlainSQL
java.lang.Object fetchValue(SQL sql)
                                           throws DataAccessException,
                                                  TooManyRowsException,
                                                  InvalidResultException
```
Execute a new query holding plain SQL.
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The value or null, if no record was found.

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

InvalidResultException - if the query returned a record with more than one value

See Also:

SQL

fetchValue
```
@Support
 @PlainSQL
java.lang.Object fetchValue(java.lang.String sql)
                                           throws DataAccessException,
                                                  TooManyRowsException,
                                                  InvalidResultException
```
Execute a new query holding plain SQL.
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The value or null, if no record was found.

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

InvalidResultException - if the query returned a record with more than one value

See Also:

SQL

fetchValue
```
@Support
 @PlainSQL
java.lang.Object fetchValue(java.lang.String sql,
                                                  java.lang.Object... bindings)
                                           throws DataAccessException,
                                                  TooManyRowsException,
                                                  InvalidResultException
```
Execute a new query holding plain SQL.
There must be as many bind variables contained in the SQL, as passed in the bindings parameter
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

bindings - The bindings

Returns:

The value or null, if no record was found.

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

InvalidResultException - if the query returned a record with more than one value

See Also:

SQL, DSL.sql(String, Object...)

fetchValue
```
@Support
 @PlainSQL
java.lang.Object fetchValue(java.lang.String sql,
                                                  QueryPart... parts)
                                           throws DataAccessException,
                                                  TooManyRowsException,
                                                  InvalidResultException
```
Execute a new query holding plain SQL.
Unlike fetchValue(String, Object...), the SQL passed to this method should not contain any bind variables. Instead, you can pass QueryPart objects to the method which will be rendered at indexed locations of your SQL string as such:
```
 // The following query
 fetchOne("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));

 // Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
 select ?, 'test' from "DUAL"
 
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses! One way to escape literals is to use DSL.name(String...) and similar methods
Parameters:

sql - The SQL clause, containing {numbered placeholders} where query parts can be injected

parts - The QueryPart objects that are rendered at the {numbered placeholder} locations

Returns:

The value or null, if no record was found.

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

InvalidResultException - if the query returned a record with more than one value

See Also:

SQL, DSL.sql(String, QueryPart...)

fetchOptionalValue
```
@Support
 @PlainSQL
java.util.Optional<?> fetchOptionalValue(SQL sql)
                                                        throws DataAccessException,
                                                               TooManyRowsException,
                                                               InvalidResultException
```
Execute a new query holding plain SQL.
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The result value from the executed query

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

InvalidResultException - if the query returned a record with more than one value

See Also:

SQL

fetchOptionalValue
```
@Support
 @PlainSQL
java.util.Optional<?> fetchOptionalValue(java.lang.String sql)
                                                        throws DataAccessException,
                                                               TooManyRowsException,
                                                               InvalidResultException
```
Execute a new query holding plain SQL.
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The result value from the executed query

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

InvalidResultException - if the query returned a record with more than one value

See Also:

SQL

fetchOptionalValue
```
@Support
 @PlainSQL
java.util.Optional<?> fetchOptionalValue(java.lang.String sql,
                                                               java.lang.Object... bindings)
                                                        throws DataAccessException,
                                                               TooManyRowsException,
                                                               InvalidResultException
```
Execute a new query holding plain SQL.
There must be as many bind variables contained in the SQL, as passed in the bindings parameter
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

bindings - The bindings

Returns:

The results from the executed query

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

InvalidResultException - if the query returned a record with more than one value

See Also:

SQL, DSL.sql(String, Object...)

fetchOptionalValue
```
@Support
 @PlainSQL
java.util.Optional<?> fetchOptionalValue(java.lang.String sql,
                                                               QueryPart... parts)
                                                        throws DataAccessException,
                                                               TooManyRowsException,
                                                               InvalidResultException
```
Execute a new query holding plain SQL.
Unlike fetchValue(String, Object...), the SQL passed to this method should not contain any bind variables. Instead, you can pass QueryPart objects to the method which will be rendered at indexed locations of your SQL string as such:
```
 // The following query
 fetchOne("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));

 // Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
 select ?, 'test' from "DUAL"
 
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses! One way to escape literals is to use DSL.name(String...) and similar methods
Parameters:

sql - The SQL clause, containing {numbered placeholders} where query parts can be injected

parts - The QueryPart objects that are rendered at the {numbered placeholder} locations

Returns:

The results from the executed query

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

InvalidResultException - if the query returned a record with more than one value

See Also:

SQL, DSL.sql(String, QueryPart...)

fetchValues
```
@Support
 @PlainSQL
java.util.List<?> fetchValues(SQL sql)
                                             throws DataAccessException
```
Execute a new query holding plain SQL.
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The values. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL

fetchValues
```
@Support
 @PlainSQL
java.util.List<?> fetchValues(java.lang.String sql)
                                             throws DataAccessException
```
Execute a new query holding plain SQL.
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

Returns:

The values. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL

fetchValues
```
@Support
 @PlainSQL
java.util.List<?> fetchValues(java.lang.String sql,
                                                    java.lang.Object... bindings)
                                             throws DataAccessException
```
Execute a new query holding plain SQL.
There must be as many bind variables contained in the SQL, as passed in the bindings parameter
Example (Postgres):
```
 String sql = "FETCH ALL IN \"\"";
```
Example (SQLite):
```
 String sql = "pragma table_info('my_table')";
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!
Parameters:

sql - The SQL

bindings - The bindings

Returns:

The values. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL, DSL.sql(String, Object...)

fetchValues
```
@Support
 @PlainSQL
java.util.List<?> fetchValues(java.lang.String sql,
                                                    QueryPart... parts)
                                             throws DataAccessException
```
Execute a new query holding plain SQL.
Unlike fetchValue(String, Object...), the SQL passed to this method should not contain any bind variables. Instead, you can pass QueryPart objects to the method which will be rendered at indexed locations of your SQL string as such:
```
 // The following query
 fetchOne("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));

 // Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
 select ?, 'test' from "DUAL"
 
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses! One way to escape literals is to use DSL.name(String...) and similar methods
Parameters:

sql - The SQL clause, containing {numbered placeholders} where query parts can be injected

parts - The QueryPart objects that are rendered at the {numbered placeholder} locations

Returns:

The values. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL, DSL.sql(String, QueryPart...)

execute
```
@Support
 @PlainSQL
int execute(SQL sql)
                           throws DataAccessException
```
Execute a query holding plain SQL.
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!

Parameters:

sql - The SQL

Returns:

The results from the executed query

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL

execute
```
@Support
 @PlainSQL
int execute(java.lang.String sql)
                           throws DataAccessException
```
Execute a query holding plain SQL.
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!

Parameters:

sql - The SQL

Returns:

The results from the executed query

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL

execute
```
@Support
 @PlainSQL
int execute(java.lang.String sql,
                                  java.lang.Object... bindings)
                           throws DataAccessException
```
Execute a new query holding plain SQL.
There must be as many bind variables contained in the SQL, as passed in the bindings parameter
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!

Parameters:

sql - The SQL

bindings - The bindings

Returns:

The results from the executed query

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL, DSL.sql(String, Object...)

execute
```
@Support
 @PlainSQL
int execute(java.lang.String sql,
                                  QueryPart... parts)
                           throws DataAccessException
```
Execute a new query holding plain SQL.
Unlike execute(String, Object...), the SQL passed to this method should not contain any bind variables. Instead, you can pass QueryPart objects to the method which will be rendered at indexed locations of your SQL string as such:
```
 // The following query
 execute("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));

 // Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
 select ?, 'test' from "DUAL"
 
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses! One way to escape literals is to use DSL.name(String...) and similar methods
Parameters:

sql - The SQL clause, containing {numbered placeholders} where query parts can be injected

parts - The QueryPart objects that are rendered at the {numbered placeholder} locations

Returns:

The results from the executed query

Throws:

DataAccessException - if something went wrong executing the query

See Also:

SQL, DSL.sql(String, QueryPart...)

resultQuery

@Support
 @PlainSQL
ResultQuery<Record> resultQuery(SQL sql)

Create a new query holding plain SQL.

There must not be any bind variables contained in the SQL

Use this method, when you want to take advantage of the many ways to fetch results in jOOQ, using ResultQuery. Some examples:

`ResultQuery.fetchLazy()`	Open a cursor and fetch records one by one
`ResultQuery.fetchInto(Class)`	Fetch records into a custom POJO (optionally annotated with JPA annotations)
`ResultQuery.fetchInto(RecordHandler)`	Fetch records into a custom callback (similar to Spring's RowMapper)

Example (Postgres):

 String sql = "FETCH ALL IN \"\"";

Example (SQLite):

 String sql = "pragma table_info('my_table')";

NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses!

Parameters:: sql - The SQL
Returns:: An executable query
See Also:: SQL

resultQuery

@Support
 @PlainSQL
ResultQuery<Record> resultQuery(java.lang.String sql)

Create a new query holding plain SQL.

There must not be any bind variables contained in the SQL

Use this method, when you want to take advantage of the many ways to fetch results in jOOQ, using ResultQuery. Some examples:

`ResultQuery.fetchLazy()`	Open a cursor and fetch records one by one
`ResultQuery.fetchInto(Class)`	Fetch records into a custom POJO (optionally annotated with JPA annotations)
`ResultQuery.fetchInto(RecordHandler)`	Fetch records into a custom callback (similar to Spring's RowMapper)

Example (Postgres):

 String sql = "FETCH ALL IN \"\"";

Example (SQLite):

 String sql = "pragma table_info('my_table')";

Parameters:: sql - The SQL
Returns:: An executable query
See Also:: SQL

resultQuery

@Support
 @PlainSQL
ResultQuery<Record> resultQuery(java.lang.String sql,
                                                      java.lang.Object... bindings)

Create a new query holding plain SQL.

There must be as many bind variables contained in the SQL, as passed in the bindings parameter

Use this method, when you want to take advantage of the many ways to fetch results in jOOQ, using ResultQuery. Some examples:

`ResultQuery.fetchLazy()`	Open a cursor and fetch records one by one
`ResultQuery.fetchInto(Class)`	Fetch records into a custom POJO (optionally annotated with JPA annotations)
`ResultQuery.fetchInto(RecordHandler)`	Fetch records into a custom callback (similar to Spring's RowMapper)

Example (Postgres):

 String sql = "FETCH ALL IN \"\"";

Example (SQLite):

 String sql = "pragma table_info('my_table')";

Parameters:: sql - The SQL; bindings - The bindings
Returns:: A query wrapping the plain SQL
See Also:: SQL, DSL.sql(String, Object...)

resultQuery
```
@Support
 @PlainSQL
ResultQuery<Record> resultQuery(java.lang.String sql,
                                                      QueryPart... parts)
```
Create a new query holding plain SQL.
Unlike resultQuery(String, Object...), the SQL passed to this method should not contain any bind variables. Instead, you can pass QueryPart objects to the method which will be rendered at indexed locations of your SQL string as such:
```
 // The following query
 resultQuery("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));

 // Will render this SQL on an Oracle database with RenderNameStyle.QUOTED:
 select ?, 'test' from "DUAL"
 
```
NOTE: When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. You may also create the possibility of malicious SQL injection. Be sure to properly use bind variables and/or escape literals when concatenated into SQL clauses! One way to escape literals is to use DSL.name(String...) and similar methods
Parameters:

sql - The SQL clause, containing {numbered placeholders} where query parts can be injected

parts - The QueryPart objects that are rendered at the {numbered placeholder} locations

Returns:

A query wrapping the plain SQL

See Also:

SQL, DSL.sql(String, QueryPart...)

fetch
```
@Support
Result<Record> fetch(java.sql.ResultSet rs)
                        throws DataAccessException
```
Fetch all data from a JDBC ResultSet and transform it to a jOOQ Result.
After fetching all data, the JDBC ResultSet will be closed.
Use fetchLazy(ResultSet), to fetch one Record at a time, instead of load the entire ResultSet into a jOOQ Result at once.

Parameters:

rs - The JDBC ResultSet to fetch data from

Returns:

The resulting jOOQ Result. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

fetch
```
@Support
Result<Record> fetch(java.sql.ResultSet rs,
                               Field<?>... fields)
                        throws DataAccessException
```
Fetch all data from a JDBC ResultSet and transform it to a jOOQ Result.
After fetching all data, the JDBC ResultSet will be closed.
Use fetchLazy(ResultSet), to fetch one Record at a time, instead of load the entire ResultSet into a jOOQ Result at once.
The additional fields argument is used by jOOQ to coerce field names and data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

fields - The fields to use in the desired output

Returns:

The resulting jOOQ Result. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

fetch
```
@Support
Result<Record> fetch(java.sql.ResultSet rs,
                               DataType<?>... types)
                        throws DataAccessException
```
Fetch all data from a JDBC ResultSet and transform it to a jOOQ Result.
After fetching all data, the JDBC ResultSet will be closed.
Use fetchLazy(ResultSet), to fetch one Record at a time, instead of load the entire ResultSet into a jOOQ Result at once.
The additional types argument is used by jOOQ to coerce data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

types - The data types to use in the desired output

Returns:

The resulting jOOQ Result. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

fetch
```
@Support
Result<Record> fetch(java.sql.ResultSet rs,
                               java.lang.Class<?>... types)
                        throws DataAccessException
```
Fetch all data from a JDBC ResultSet and transform it to a jOOQ Result.
After fetching all data, the JDBC ResultSet will be closed.
Use fetchLazy(ResultSet), to fetch one Record at a time, instead of load the entire ResultSet into a jOOQ Result at once.
The additional types argument is used by jOOQ to coerce data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

types - The data types to use in the desired output

Returns:

The resulting jOOQ Result. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

fetchOne
```
@Support
Record fetchOne(java.sql.ResultSet rs)
                   throws DataAccessException,
                          TooManyRowsException
```
Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record.
This will internally fetch all records and throw an exception if there was more than one resulting record.

Parameters:

rs - The JDBC ResultSet to fetch data from

Returns:

The record or null, if no record was found.

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

fetchOne
```
@Support
Record fetchOne(java.sql.ResultSet rs,
                          Field<?>... fields)
                   throws DataAccessException,
                          TooManyRowsException
```
Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record.
This will internally fetch all records and throw an exception if there was more than one resulting record.
The additional fields argument is used by jOOQ to coerce field names and data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

fields - The fields to use in the desired output

Returns:

The record or null, if no record was found.

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

fetchOne
```
@Support
Record fetchOne(java.sql.ResultSet rs,
                          DataType<?>... types)
                   throws DataAccessException,
                          TooManyRowsException
```
Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record.
This will internally fetch all records and throw an exception if there was more than one resulting record.
The additional types argument is used by jOOQ to coerce data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

types - The data types to use in the desired output

Returns:

The record or null, if no record was found.

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

fetchOne
```
@Support
Record fetchOne(java.sql.ResultSet rs,
                          java.lang.Class<?>... types)
                   throws DataAccessException,
                          TooManyRowsException
```
Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record.
This will internally fetch all records and throw an exception if there was more than one resulting record.
The additional types argument is used by jOOQ to coerce data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

types - The data types to use in the desired output

Returns:

The record. This is never null.

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

fetchSingle
```
@Support
Record fetchSingle(java.sql.ResultSet rs)
                      throws DataAccessException,
                             TooManyRowsException
```
Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record.
This will internally fetch all records and throw an exception if there was more than one resulting record.

Parameters:

rs - The JDBC ResultSet to fetch data from

Returns:

The record or null, if no record was found.

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

fetchSingle
```
@Support
Record fetchSingle(java.sql.ResultSet rs,
                             Field<?>... fields)
                      throws DataAccessException,
                             NoDataFoundException,
                             TooManyRowsException
```
Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record.
This will internally fetch all records and throw an exception if there was more than one resulting record.
The additional fields argument is used by jOOQ to coerce field names and data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

fields - The fields to use in the desired output

Returns:

The record. This is never null.

Throws:

DataAccessException - if something went wrong executing the query

NoDataFoundException - if the query returned no rows

TooManyRowsException - if the query returned more than one record

fetchSingle
```
@Support
Record fetchSingle(java.sql.ResultSet rs,
                             DataType<?>... types)
                      throws DataAccessException,
                             NoDataFoundException,
                             TooManyRowsException
```
Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record.
This will internally fetch all records and throw an exception if there was more than one resulting record.
The additional types argument is used by jOOQ to coerce data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

types - The data types to use in the desired output

Returns:

The record. This is never null.

Throws:

DataAccessException - if something went wrong executing the query

NoDataFoundException - if the query returned no rows

TooManyRowsException - if the query returned more than one record

fetchSingle
```
@Support
Record fetchSingle(java.sql.ResultSet rs,
                             java.lang.Class<?>... types)
                      throws DataAccessException,
                             NoDataFoundException,
                             TooManyRowsException
```
Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record.
This will internally fetch all records and throw an exception if there was more than one resulting record.
The additional types argument is used by jOOQ to coerce data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

types - The data types to use in the desired output

Returns:

The record. This is never null.

Throws:

DataAccessException - if something went wrong executing the query

NoDataFoundException - if the query returned no rows

TooManyRowsException - if the query returned more than one record

fetchOptional
```
@Support
java.util.Optional<Record> fetchOptional(java.sql.ResultSet rs)
                                            throws DataAccessException,
                                                   NoDataFoundException,
                                                   TooManyRowsException
```
Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record.
This will internally fetch all records and throw an exception if there was more than one resulting record.

Parameters:

rs - The JDBC ResultSet to fetch data from

Returns:

The resulting jOOQ record

Throws:

DataAccessException - if something went wrong executing the query

NoDataFoundException - if the query returned no rows

TooManyRowsException - if the query returned more than one record

fetchOptional
```
@Support
java.util.Optional<Record> fetchOptional(java.sql.ResultSet rs,
                                                   Field<?>... fields)
                                            throws DataAccessException,
                                                   TooManyRowsException
```
Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record.
This will internally fetch all records and throw an exception if there was more than one resulting record.
The additional fields argument is used by jOOQ to coerce field names and data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

fields - The fields to use in the desired output

Returns:

The resulting jOOQ record

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

fetchOptional
```
@Support
java.util.Optional<Record> fetchOptional(java.sql.ResultSet rs,
                                                   DataType<?>... types)
                                            throws DataAccessException,
                                                   TooManyRowsException
```
Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record.
This will internally fetch all records and throw an exception if there was more than one resulting record.
The additional types argument is used by jOOQ to coerce data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

types - The data types to use in the desired output

Returns:

The resulting jOOQ record

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

fetchOptional
```
@Support
java.util.Optional<Record> fetchOptional(java.sql.ResultSet rs,
                                                   java.lang.Class<?>... types)
                                            throws DataAccessException,
                                                   TooManyRowsException
```
Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record.
This will internally fetch all records and throw an exception if there was more than one resulting record.
The additional types argument is used by jOOQ to coerce data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

types - The data types to use in the desired output

Returns:

The resulting jOOQ record

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

fetchValue
```
@Support
java.lang.Object fetchValue(java.sql.ResultSet rs)
                               throws DataAccessException,
                                      TooManyRowsException,
                                      InvalidResultException
```
Fetch a record from a JDBC ResultSet and return the only contained value.
This will internally fetch all records and throw an exception if there was more than one resulting record.

Parameters:

rs - The JDBC ResultSet to fetch data from

Returns:

The value or null, if no record was found.

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

InvalidResultException - if the query returned a record with more than one value

fetchValue
```
@Support
<T> T fetchValue(java.sql.ResultSet rs,
                           Field<T> field)
                    throws DataAccessException,
                           TooManyRowsException,
                           InvalidResultException
```
Fetch a record from a JDBC ResultSet and return the only contained value.
This will internally fetch all records and throw an exception if there was more than one resulting record.
The additional field argument is used by jOOQ to coerce field names and data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

field - The field to use in the desired output

Returns:

The value or null, if no record was found.

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

InvalidResultException - if the query returned a record with more than one value

fetchValue
```
@Support
<T> T fetchValue(java.sql.ResultSet rs,
                           DataType<T> type)
                    throws DataAccessException,
                           TooManyRowsException,
                           InvalidResultException
```
Fetch a record from a JDBC ResultSet and return the only contained value.
This will internally fetch all records and throw an exception if there was more than one resulting record.
The additional type argument is used by jOOQ to coerce data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

type - The data type to use in the desired output

Returns:

The value or null, if no record was found.

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

InvalidResultException - if the query returned a record with more than one value

fetchValue
```
@Support
<T> T fetchValue(java.sql.ResultSet rs,
                           java.lang.Class<T> type)
                    throws DataAccessException,
                           TooManyRowsException,
                           InvalidResultException
```
Fetch a record from a JDBC ResultSet and return the only contained value.
This will internally fetch all records and throw an exception if there was more than one resulting record.
The additional type argument is used by jOOQ to coerce data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

type - The data types to use in the desired output

Returns:

The value or null, if no record was found.

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

InvalidResultException - if the query returned a record with more than one value

fetchOptionalValue
```
@Support
java.util.Optional<?> fetchOptionalValue(java.sql.ResultSet rs)
                                            throws DataAccessException,
                                                   TooManyRowsException,
                                                   InvalidResultException
```
Fetch a record from a JDBC ResultSet and return the only contained value.
This will internally fetch all records and throw an exception if there was more than one resulting record.

Parameters:

rs - The JDBC ResultSet to fetch data from

Returns:

The resulting value

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

InvalidResultException - if the query returned a record with more than one value

fetchOptionalValue
```
@Support
<T> java.util.Optional<T> fetchOptionalValue(java.sql.ResultSet rs,
                                                       Field<T> field)
                                                throws DataAccessException,
                                                       TooManyRowsException,
                                                       InvalidResultException
```
Fetch a record from a JDBC ResultSet and return the only contained value.
This will internally fetch all records and throw an exception if there was more than one resulting record.
The additional field argument is used by jOOQ to coerce field names and data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

field - The field to use in the desired output

Returns:

The resulting value

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

InvalidResultException - if the query returned a record with more than one value

fetchOptionalValue
```
@Support
<T> java.util.Optional<T> fetchOptionalValue(java.sql.ResultSet rs,
                                                       DataType<T> type)
                                                throws DataAccessException,
                                                       TooManyRowsException,
                                                       InvalidResultException
```
Fetch a record from a JDBC ResultSet and return the only contained value.
This will internally fetch all records and throw an exception if there was more than one resulting record.
The additional type argument is used by jOOQ to coerce data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

type - The data type to use in the desired output

Returns:

The resulting value

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

InvalidResultException - if the query returned a record with more than one value

fetchOptionalValue
```
@Support
<T> java.util.Optional<T> fetchOptionalValue(java.sql.ResultSet rs,
                                                       java.lang.Class<T> type)
                                                throws DataAccessException,
                                                       TooManyRowsException,
                                                       InvalidResultException
```
Fetch a record from a JDBC ResultSet and return the only contained value.
This will internally fetch all records and throw an exception if there was more than one resulting record.
The additional type argument is used by jOOQ to coerce data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

type - The data types to use in the desired output

Returns:

The resulting value

Throws:

DataAccessException - if something went wrong executing the query

TooManyRowsException - if the query returned more than one record

InvalidResultException - if the query returned a record with more than one value

fetchValues
```
@Support
java.util.List<?> fetchValues(java.sql.ResultSet rs)
                                 throws DataAccessException
```
Fetch a result from a JDBC ResultSet and return the only contained column's values.

Parameters:

rs - The JDBC ResultSet to fetch data from

Returns:

The values. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

fetchValues
```
@Support
<T> java.util.List<T> fetchValues(java.sql.ResultSet rs,
                                            Field<T> field)
                                     throws DataAccessException
```
Fetch a result from a JDBC ResultSet and return the only contained column's values.
The additional field argument is used by jOOQ to coerce field names and data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

field - The field to use in the desired output

Returns:

The values. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

fetchValues
```
@Support
<T> java.util.List<T> fetchValues(java.sql.ResultSet rs,
                                            DataType<T> type)
                                     throws DataAccessException
```
Fetch a result from a JDBC ResultSet and return the only contained column's values.
The additional type argument is used by jOOQ to coerce data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

type - The data type to use in the desired output

Returns:

The values. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

fetchValues
```
@Support
<T> java.util.List<T> fetchValues(java.sql.ResultSet rs,
                                            java.lang.Class<T> type)
                                     throws DataAccessException
```
Fetch a result from a JDBC ResultSet and return the only contained column's values.
The additional type argument is used by jOOQ to coerce data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

type - The data types to use in the desired output

Returns:

The values. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

fetchLazy
```
@Support
Cursor<Record> fetchLazy(java.sql.ResultSet rs)
                            throws DataAccessException
```
Wrap a JDBC ResultSet into a jOOQ Cursor.
Use fetch(ResultSet), to load the entire ResultSet into a jOOQ Result at once.

Parameters:

rs - The JDBC ResultSet to fetch data from

Returns:

The cursor. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

fetchLazy
```
@Support
Cursor<Record> fetchLazy(java.sql.ResultSet rs,
                                   Field<?>... fields)
                            throws DataAccessException
```
Wrap a JDBC ResultSet into a jOOQ Cursor.
Use fetch(ResultSet), to load the entire ResultSet into a jOOQ Result at once.
The additional fields argument is used by jOOQ to coerce field names and data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

fields - The fields to use in the desired output

Returns:

The cursor. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

fetchLazy
```
@Support
Cursor<Record> fetchLazy(java.sql.ResultSet rs,
                                   DataType<?>... types)
                            throws DataAccessException
```
Wrap a JDBC ResultSet into a jOOQ Cursor.
Use fetch(ResultSet), to load the entire ResultSet into a jOOQ Result at once.
The additional types argument is used by jOOQ to coerce data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

types - The data types to use in the desired output

Returns:

The cursor. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

fetchLazy
```
@Support
Cursor<Record> fetchLazy(java.sql.ResultSet rs,
                                   java.lang.Class<?>... types)
                            throws DataAccessException
```
Wrap a JDBC ResultSet into a jOOQ Cursor.
Use fetch(ResultSet), to load the entire ResultSet into a jOOQ Result at once.
The additional types argument is used by jOOQ to coerce data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

types - The data types to use in the desired output

Returns:

The cursor. This will never be null.

Throws:

DataAccessException - if something went wrong executing the query

fetchAsync
```
@Support
java.util.concurrent.CompletionStage<Result<Record>> fetchAsync(java.sql.ResultSet rs)
```
Fetch results in a new CompletionStage.
The result is asynchronously completed by a task running in an Executor provided by the Scope.configuration()'s Configuration.executorProvider().

Parameters:

rs - The JDBC ResultSet to fetch data from

Returns:

The completion stage. The completed result will never be null.

fetchAsync
```
@Support
java.util.concurrent.CompletionStage<Result<Record>> fetchAsync(java.sql.ResultSet rs,
                                                                          Field<?>... fields)
```
Fetch results in a new CompletionStage.
The result is asynchronously completed by a task running in an Executor provided by the Scope.configuration()'s Configuration.executorProvider().
The additional fields argument is used by jOOQ to coerce field names and data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

fields - The fields to use in the desired output

Returns:

The completion stage. The completed result will never be null.

fetchAsync
```
@Support
java.util.concurrent.CompletionStage<Result<Record>> fetchAsync(java.sql.ResultSet rs,
                                                                          DataType<?>... types)
```
Fetch results in a new CompletionStage.
The result is asynchronously completed by a task running in an Executor provided by the Scope.configuration()'s Configuration.executorProvider().
The additional types argument is used by jOOQ to coerce data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

types - The data types to use in the desired output

Returns:

The completion stage. The completed result will never be null.

fetchAsync
```
@Support
java.util.concurrent.CompletionStage<Result<Record>> fetchAsync(java.sql.ResultSet rs,
                                                                          java.lang.Class<?>... types)
```
Fetch results in a new CompletionStage.
The result is asynchronously completed by a task running in an Executor provided by the Scope.configuration()'s Configuration.executorProvider().
The additional types argument is used by jOOQ to coerce data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

types - The data types to use in the desired output

Returns:

The completion stage. The completed result will never be null.

fetchAsync
```
@Support
java.util.concurrent.CompletionStage<Result<Record>> fetchAsync(java.util.concurrent.Executor executor,
                                                                          java.sql.ResultSet rs)
```
Fetch results in a new CompletionStage that is asynchronously completed by a task running in the given executor.

Parameters:

rs - The JDBC ResultSet to fetch data from

Returns:

The completion stage. The completed result will never be null.

fetchAsync
```
@Support
java.util.concurrent.CompletionStage<Result<Record>> fetchAsync(java.util.concurrent.Executor executor,
                                                                          java.sql.ResultSet rs,
                                                                          Field<?>... fields)
```
Fetch results in a new CompletionStage that is asynchronously completed by a task running in the given executor.
The additional fields argument is used by jOOQ to coerce field names and data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

fields - The fields to use in the desired output

Returns:

The completion stage. The completed result will never be null.

fetchAsync

@Support
java.util.concurrent.CompletionStage<Result<Record>> fetchAsync(java.util.concurrent.Executor executor,
                                                                          java.sql.ResultSet rs,
                                                                          DataType<?>... types)

Fetch results in a new CompletionStage that is asynchronously completed by a task running in the given executor.

The additional types argument is used by jOOQ to coerce data types to the desired output

Parameters:: rs - The JDBC ResultSet to fetch data from; types - The data types to use in the desired output
Returns:: The completion stage. The completed result will never be null.

fetchAsync
```
@Support
java.util.concurrent.CompletionStage<Result<Record>> fetchAsync(java.util.concurrent.Executor executor,
                                                                          java.sql.ResultSet rs,
                                                                          java.lang.Class<?>... types)
```
Fetch results in a new CompletionStage that is asynchronously completed by a task running in the given executor.
The additional types argument is used by jOOQ to coerce data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

types - The data types to use in the desired output

Returns:

The completion stage. The completed result will never be null.

fetchStream
```
@Support
java.util.stream.Stream<Record> fetchStream(java.sql.ResultSet rs)
                                               throws DataAccessException
```
Wrap a JDBC ResultSet into a jOOQ Stream.
Use fetch(ResultSet), to load the entire ResultSet into a jOOQ Result at once.

Parameters:

rs - The JDBC ResultSet to fetch data from

Returns:

The resulting stream

Throws:

DataAccessException - if something went wrong executing the query

fetchStream
```
@Support
java.util.stream.Stream<Record> fetchStream(java.sql.ResultSet rs,
                                                      Field<?>... fields)
                                               throws DataAccessException
```
Wrap a JDBC ResultSet into a jOOQ Stream.
Use fetch(ResultSet), to load the entire ResultSet into a jOOQ Result at once.
The additional fields argument is used by jOOQ to coerce field names and data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

fields - The fields to use in the desired output

Returns:

The resulting stream

Throws:

DataAccessException - if something went wrong executing the query

fetchStream
```
@Support
java.util.stream.Stream<Record> fetchStream(java.sql.ResultSet rs,
                                                      DataType<?>... types)
                                               throws DataAccessException
```
Wrap a JDBC ResultSet into a jOOQ Stream.
Use fetch(ResultSet), to load the entire ResultSet into a jOOQ Result at once.
The additional types argument is used by jOOQ to coerce data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

types - The data types to use in the desired output

Returns:

The resulting stream

Throws:

DataAccessException - if something went wrong executing the query

fetchStream
```
@Support
java.util.stream.Stream<Record> fetchStream(java.sql.ResultSet rs,
                                                      java.lang.Class<?>... types)
                                               throws DataAccessException
```
Wrap a JDBC ResultSet into a jOOQ Stream.
Use fetch(ResultSet), to load the entire ResultSet into a jOOQ Result at once.
The additional types argument is used by jOOQ to coerce data types to the desired output

Parameters:

rs - The JDBC ResultSet to fetch data from

types - The data types to use in the desired output

Returns:

The resulting stream

Throws:

DataAccessException - if something went wrong executing the query

fetchFromTXT
```
@Support
Result<Record> fetchFromTXT(java.lang.String string)
                               throws DataAccessException
```
Fetch all data from a formatted string.
The supplied string is supposed to be formatted in a human-readable way. This is the same as calling fetchFromTXT(string, "{null}")

Parameters:

string - The formatted string

Returns:

The transformed result. This will never be null.

Throws:

DataAccessException - If the supplied string does not adhere to the above format rules.

See Also:

fetchFromTXT(String, String)

fetchFromTXT
```
@Support
Result<Record> fetchFromTXT(java.lang.String string,
                                      java.lang.String nullLiteral)
                               throws DataAccessException
```
Fetch all data from a formatted string.
This method supports parsing results from two types of human-readable formats:
The jOOQ Result.format()

This format is recognised by the fact that the first line starts with a "plus" sign:
```
 +-----+-----+--------------------------+
 |COL1 |COL2 |COL3 containing whitespace|
 +-----+-----+--------------------------+
 |val1 |1    |some text                 |
 |val2 | 2   | more text                |
 +-----+-----+--------------------------+
 
```
This method will decode the above formatted string according to the following rules:
- The number of columns is defined by the number of dash groups in the first line. Groups are separated by exactly one "plus" sign
- The column types are VARCHAR(N) where N = number of dashes per dash group
- The column names are defined by the trimmed text contained in the second row
- The data is defined by the trimmed text contained in the subsequent rows
The H2 database test data format

The supplied string is supposed to be formatted in the following, human-readable way:
```
 COL1  COL2   COL3 containing whitespace
 ----- ----   --------------------------
 val1  1      some text
 val2   2      more text
 
```
This method will decode the above formatted string according to the following rules:
- The number of columns is defined by the number of dash groups in the second line. Groups are separated by space(s)
- The column types are VARCHAR(N) where N = number of dashes per dash group
- The column names are defined by the trimmed text contained in the first row
- The data is defined by the trimmed text contained in the subsequent rows
Both parsing methods

Both parsing methods make no assumption about the resulting data types. Instead, all data is string-based.
Parameters:

string - The formatted string

nullLiteral - The string literal to be used as null value.

Returns:

The transformed result. This will never be null.

Throws:

DataAccessException - If the supplied string does not adhere to the above format rules.

fetchFromHTML
```
@Support
Result<Record> fetchFromHTML(java.lang.String string)
                                throws DataAccessException
```
Convert an HTML table into a jOOQ Result.
This is the inverse operation of Result.formatHTML(). It works according to the following parsing rules:
- The input is expected to be well-formed XML. XHTML conformance is not required - i.e. unknown elements / attributes, or elements / attributes not specified here, such as <caption>, <thead>, <tbody> are simply ignored.
- The surrounding <table> element is optional, but it may appear only once
- A single row containing table headings <th> is allowed. Further rows containing table headings are ignored. Table headings define field names. In the absence of table headings, field names are generated.
- The first row <tr> specifies the number of columns in the table (regardless if it contains table headings or not). Subsequent rows containing less columns will be padded. Subsequent rows containing more columns will be truncated.
- Comments are ignored
- Nested tables are not supported
Ideal input looks like this:
```
 <table>
 <tr><th>COL1</th><th>COL2</th></tr>
 <tr><td>1</td><td>a</td></tr>
 <tr><td>2</td><td>b</td></tr>
 </table>
 
 
```
Parameters:

string - The HTML-formatted string.

Returns:

The transformed result. This will never be null.

Throws:

DataAccessException - If the supplied string does not adhere to the above format rules.

fetchFromCSV
```
@Support
Result<Record> fetchFromCSV(java.lang.String string)
                               throws DataAccessException
```
Fetch all data from a CSV string.
This is the same as calling fetchFromCSV(string, ',') and the inverse of calling Result.formatCSV(). The first row of the CSV data is required to hold field name information. Subsequent rows may contain data, which is interpreted as String. Use the various conversion methods to retrieve other data types from the Result:
Missing values result in null. Empty values result in empty Strings
Parameters:

string - The CSV string

Returns:

The transformed result. This will never be null.

Throws:

DataAccessException - If anything went wrong parsing the CSV file

See Also:

fetchFromCSV(String, char)

fetchFromCSV
```
@Support
Result<Record> fetchFromCSV(java.lang.String string,
                                      char delimiter)
                               throws DataAccessException
```
Fetch all data from a CSV string.
This is inverse of calling Result.formatCSV(char). The first row of the CSV data is required to hold field name information. Subsequent rows may contain data, which is interpreted as String. Use the various conversion methods to retrieve other data types from the Result:
Missing values result in null. Empty values result in empty Strings
Parameters:

string - The CSV string

delimiter - The delimiter to expect between records

Returns:

The transformed result. This will never be null.

Throws:

DataAccessException - If anything went wrong parsing the CSV file

See Also:

fetchFromCSV(String), fetchFromStringData(List)

fetchFromCSV
```
@Support
Result<Record> fetchFromCSV(java.lang.String string,
                                      boolean header)
                               throws DataAccessException
```
Fetch all data from a CSV string.
This is the same as calling fetchFromCSV(string, ',') and the inverse of calling Result.formatCSV(boolean). Rows may contain data, which is interpreted as String. Use the various conversion methods to retrieve other data types from the Result:
Missing values result in null. Empty values result in empty Strings
Parameters:

string - The CSV string

header - Whether to parse the first line as a CSV header line

Returns:

The transformed result. This will never be null.

Throws:

DataAccessException - If anything went wrong parsing the CSV file

See Also:

fetchFromCSV(String, char)

fetchFromCSV
```
@Support
Result<Record> fetchFromCSV(java.lang.String string,
                                      boolean header,
                                      char delimiter)
                               throws DataAccessException
```
Fetch all data from a CSV string.
This is inverse of calling Result.formatCSV(boolean, char). Rows may contain data, which are interpreted as String. Use the various conversion methods to retrieve other data types from the Result:
Missing values result in null. Empty values result in empty Strings
Parameters:

string - The CSV string

header - Whether to parse the first line as a CSV header line

delimiter - The delimiter to expect between records

Returns:

The transformed result. This will never be null.

Throws:

DataAccessException - If anything went wrong parsing the CSV file

See Also:

fetchFromCSV(String), fetchFromStringData(List)

fetchFromJSON
```
@Support
Result<Record> fetchFromJSON(java.lang.String string)
```
Fetch all data from a JSON string.
This is the inverse of calling Result.formatJSON(). Use the various conversion methods to retrieve other data types from the Result:
Missing values result in null. Empty values result in empty Strings
Parameters:

string - The JSON string

Returns:

The transformed result. This will never be null.

Throws:

DataAccessException - If anything went wrong parsing the JSON file

fetchFromStringData
```
Result<Record> fetchFromStringData(java.lang.String[]... data)
```
Fetch all data from a list of strings.
This is used by methods such as
- fetchFromCSV(String)
- fetchFromTXT(String)
The first element of the argument list should contain column names. Subsequent elements contain actual data. The degree of all arrays contained in the argument should be the same, although this is not a requirement. jOOQ will ignore excess data, and fill missing data with null.
Parameters:

data - The data to be transformed into a Result

Returns:

The transformed result. This will never be null.

See Also:

fetchFromStringData(List)

fetchFromStringData
```
Result<Record> fetchFromStringData(java.util.List<java.lang.String[]> data)
```
Fetch all data from a list of strings.
This is used by methods such as
- fetchFromCSV(String)
- fetchFromTXT(String)
The first element of the argument list should contain column names. Subsequent elements contain actual data. The degree of all arrays contained in the argument should be the same, although this is not a requirement. jOOQ will ignore excess data, and fill missing data with null.
Parameters:

data - The data to be transformed into a Result

Returns:

The transformed result. This will never be null.

fetchFromStringData
```
Result<Record> fetchFromStringData(java.util.List<java.lang.String[]> data,
                                   boolean header)
```
Fetch all data from a list of strings.
This is used by methods such as
- fetchFromCSV(String)
- fetchFromTXT(String)
The degree of all arrays contained in the argument should be the same, although this is not a requirement. jOOQ will ignore excess data, and fill missing data with null.
Parameters:

data - The data to be transformed into a Result

header - Whether to interpret the first line as a set of column names.

Returns:

The transformed result. This will never be null.

with
```
@Support(value={DB2,FIREBIRD,HSQLDB,MYSQL_8_0,ORACLE,POSTGRES,SQLSERVER,SYBASE,VERTICA})
WithAsStep with(java.lang.String alias)
```
Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some databases, in case of which it will not be rendered. For optimal database interoperability and readability, however, it is suggested that you use with(String) for strictly non-recursive CTE and withRecursive(String) for strictly recursive CTE.

with
```
@Support(value={DB2,FIREBIRD,HSQLDB,MYSQL_8_0,ORACLE,POSTGRES,SQLSERVER,SYBASE,VERTICA})
WithAsStep with(java.lang.String alias,
                                                                                                          java.lang.String... fieldAliases)
```
Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some databases, in case of which it will not be rendered. For optimal database interoperability and readability, however, it is suggested that you use with(String, String...) for strictly non-recursive CTE and withRecursive(String, String...) for strictly recursive CTE.

with
```
@Support(value={DB2,FIREBIRD,H2,HSQLDB,MYSQL_8_0,ORACLE,POSTGRES,SQLSERVER,SYBASE,VERTICA})
WithAsStep with(Name alias)
```
Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some databases, in case of which it will not be rendered. For optimal database interoperability and readability, however, it is suggested that you use with(Name) for strictly non-recursive CTE and withRecursive(Name) for strictly recursive CTE.

with
```
@Support(value={DB2,FIREBIRD,H2,HSQLDB,MYSQL_8_0,ORACLE,POSTGRES,SQLSERVER,SYBASE,VERTICA})
WithAsStep with(Name alias,
                                                                                                             Name... fieldAliases)
```
Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some databases, in case of which it will not be rendered. For optimal database interoperability and readability, however, it is suggested that you use with(Name, Name...) for strictly non-recursive CTE and withRecursive(Name, Name...) for strictly recursive CTE.

with
```
@Support(value={DB2,FIREBIRD,HSQLDB,MYSQL_8_0,ORACLE,POSTGRES,SQLSERVER,SYBASE,VERTICA})
WithAsStep with(java.lang.String alias,
                                                                                                          java.util.function.Function<? super Field<?>,? extends java.lang.String> fieldNameFunction)
```
Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some databases, in case of which it will not be rendered. For optimal database interoperability and readability, however, it is suggested that you use with(String, String...) for strictly non-recursive CTE and withRecursive(String, String...) for strictly recursive CTE.
This works in a similar way as with(String, String...), except that all column names are produced by a function that receives the CTE's Select columns as input.

with
```
@Support(value={DB2,FIREBIRD,HSQLDB,MYSQL_8_0,ORACLE,POSTGRES,SQLSERVER,SYBASE,VERTICA})
WithAsStep with(java.lang.String alias,
                                                                                                          java.util.function.BiFunction<? super Field<?>,? super java.lang.Integer,? extends java.lang.String> fieldNameFunction)
```
Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some databases, in case of which it will not be rendered. For optimal database interoperability and readability, however, it is suggested that you use with(String, String...) for strictly non-recursive CTE and withRecursive(String, String...) for strictly recursive CTE.
This works in a similar way as with(String, String...), except that all column names are produced by a function that receives the CTE's Select columns and their column indexes as input.

with
```
@Generated(value="This method was generated using jOOQ-tools")
 @Support(value={DB2,FIREBIRD,HSQLDB,ORACLE,POSTGRES,SQLSERVER,SYBASE,VERTICA})
WithAsStep1 with(java.lang.String alias,
                                                                                                                                                                  java.lang.String fieldAlias1)
```
Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some databases, in case of which it will not be rendered. For optimal database interoperability and readability, however, it is suggested that you use with(String, String...) for strictly non-recursive CTE and withRecursive(String, String...) for strictly recursive CTE.