java.lang.Object

org.jooq.impl.DefaultDSLContext

All Implemented Interfaces:: Serializable, DSLContext, Scope

Direct Known Subclasses:: DefaultCloseableDSLContext

public class DefaultDSLContext extends Object implements DSLContext, Serializable

A default implementation for DSLContext.

You may use this as a base implementation for custom DSLContext subtypes preventing potential API breakage when upgrading jOOQ, or to delegate DSL method calls to your custom implementations.

Author:: Lukas Eder
See Also:: Serialized Form

Constructor Summary

Constructors

Constructor

Description

DefaultDSLContext(io.r2dbc.spi.ConnectionFactory connectionFactory, SQLDialect dialect)

DefaultDSLContext(io.r2dbc.spi.ConnectionFactory connectionFactory, SQLDialect dialect, Settings settings)

DefaultDSLContext(Connection connection, SQLDialect dialect)

DefaultDSLContext(Connection connection, SQLDialect dialect, Settings settings)

DefaultDSLContext(DataSource datasource, SQLDialect dialect)

DefaultDSLContext(DataSource datasource, SQLDialect dialect, Settings settings)

DefaultDSLContext(Configuration configuration)

DefaultDSLContext(ConnectionProvider connectionProvider, SQLDialect dialect)

DefaultDSLContext(ConnectionProvider connectionProvider, SQLDialect dialect, Settings settings)

DefaultDSLContext(SQLDialect dialect)

DefaultDSLContext(SQLDialect dialect, Settings settings)
Method Summary

Modifier and Type

Method

Description

AlterDatabaseStep

alterDatabase(String database)

The ALTER DATABASE statement.

AlterDatabaseStep

alterDatabase(Catalog database)

The ALTER DATABASE statement.

AlterDatabaseStep

alterDatabase(Name database)

The ALTER DATABASE statement.

AlterDatabaseStep

alterDatabaseIfExists(String database)

The ALTER DATABASE IF EXISTS statement.

AlterDatabaseStep

alterDatabaseIfExists(Catalog database)

The ALTER DATABASE IF EXISTS statement.

AlterDatabaseStep

alterDatabaseIfExists(Name database)

The ALTER DATABASE IF EXISTS statement.

<T> AlterDomainStep<T>

alterDomain(String domain)

The ALTER DOMAIN statement.

<T> AlterDomainStep<T>

alterDomain(Domain<T> domain)

The ALTER DOMAIN statement.

<T> AlterDomainStep<T>

alterDomain(Name domain)

The ALTER DOMAIN statement.

<T> AlterDomainStep<T>

alterDomainIfExists(String domain)

The ALTER DOMAIN IF EXISTS statement.

<T> AlterDomainStep<T>

alterDomainIfExists(Domain<T> domain)

The ALTER DOMAIN IF EXISTS statement.

<T> AlterDomainStep<T>

alterDomainIfExists(Name domain)

The ALTER DOMAIN IF EXISTS statement.

AlterIndexOnStep

alterIndex(String index)

The ALTER INDEX statement.

AlterIndexOnStep

alterIndex(Index index)

The ALTER INDEX statement.

AlterIndexOnStep

alterIndex(Name index)

The ALTER INDEX statement.

AlterIndexOnStep

alterIndexIfExists(String index)

The ALTER INDEX IF EXISTS statement.

AlterIndexOnStep

alterIndexIfExists(Index index)

The ALTER INDEX IF EXISTS statement.

AlterIndexOnStep

alterIndexIfExists(Name index)

The ALTER INDEX IF EXISTS statement.

AlterSchemaStep

alterSchema(String schema)

The ALTER SCHEMA statement.

AlterSchemaStep

alterSchema(Name schema)

The ALTER SCHEMA statement.

AlterSchemaStep

alterSchema(Schema schema)

The ALTER SCHEMA statement.

AlterSchemaStep

alterSchemaIfExists(String schema)

The ALTER SCHEMA IF EXISTS statement.

AlterSchemaStep

alterSchemaIfExists(Name schema)

The ALTER SCHEMA IF EXISTS statement.

AlterSchemaStep

alterSchemaIfExists(Schema schema)

The ALTER SCHEMA IF EXISTS statement.

AlterSequenceStep<Number>

alterSequence(String sequence)

The ALTER SEQUENCE statement.

AlterSequenceStep<Number>

alterSequence(Name sequence)

The ALTER SEQUENCE statement.

<T extends Number> AlterSequenceStep<T>

alterSequence(Sequence<T> sequence)

The ALTER SEQUENCE statement.

AlterSequenceStep<Number>

alterSequenceIfExists(String sequence)

The ALTER SEQUENCE IF EXISTS statement.

AlterSequenceStep<Number>

alterSequenceIfExists(Name sequence)

The ALTER SEQUENCE IF EXISTS statement.

<T extends Number> AlterSequenceStep<T>

alterSequenceIfExists(Sequence<T> sequence)

The ALTER SEQUENCE IF EXISTS statement.

AlterTableStep

alterTable(String table)

Create a new DSL ALTER TABLE statement.

AlterTableStep

alterTable(Name table)

Create a new DSL ALTER TABLE statement.

AlterTableStep

alterTable(Table<?> table)

Create a new DSL ALTER TABLE statement.

AlterTableStep

alterTableIfExists(String table)

Create a new DSL ALTER TABLE statement.

AlterTableStep

alterTableIfExists(Name table)

Create a new DSL ALTER TABLE statement.

AlterTableStep

alterTableIfExists(Table<?> table)

Create a new DSL ALTER TABLE statement.

AlterTypeStep

alterType(String type)

The ALTER TYPE statement.

AlterTypeStep

alterType(Name type)

The ALTER TYPE statement.

AlterViewStep

alterView(String view)

The ALTER VIEW statement.

AlterViewStep

alterView(Name view)

The ALTER VIEW statement.

AlterViewStep

alterView(Table<?> view)

The ALTER VIEW statement.

AlterViewStep

alterViewIfExists(String view)

The ALTER VIEW IF EXISTS statement.

AlterViewStep

alterViewIfExists(Name view)

The ALTER VIEW IF EXISTS statement.

AlterViewStep

alterViewIfExists(Table<?> view)

The ALTER VIEW IF EXISTS statement.

void

attach(Collection<? extends Attachable> attachables)

Attach this DSLContext's underlying Scope.configuration() to some attachables.

void

attach(Attachable... attachables)

Attach this DSLContext's underlying Scope.configuration() to some attachables.

BatchBindStep

batch(String sql)

Create a batch statement to execute a set of queries in batch mode (with bind values).

Batch

batch(String... queries)

Create a batch statement to execute a set of queries in batch mode (without bind values).

Batch

batch(String sql, Object[]... bindings)

Create a batch statement to execute a set of queries in batch mode (with bind values).

Batch

batch(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).

BatchBindStep

batch(Query query)

Create a batch statement to execute a set of queries in batch mode (with bind values).

Batch

batch(Query... queries)

Create a batch statement to execute a set of queries in batch mode (without bind values).

Batch

batch(Query query, Object[]... bindings)

Create a batch statement to execute a set of queries in batch mode (with bind values).

Batch

batchDelete(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.

void

batched(BatchedRunnable runnable)

Run a BatchedRunnable on a BatchedConnection, delaying execution as long as possible before batching.

<T> T

batchedResult(BatchedCallable<T> callable)

Run a BatchedRunnable on a BatchedConnection, delaying execution as long as possible before batching.

Batch

batchInsert(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

batchMerge(Collection<? extends UpdatableRecord<?>> records)

Create a batch statement to execute a set of MERGE queries in batch mode (with bind values) according to UpdatableRecord.merge() semantics.

Batch

batchMerge(UpdatableRecord<?>... records)

Create a batch statement to execute a set of MERGE queries in batch mode (with bind values) according to UpdatableRecord.merge() semantics.

Batch

batchStore(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(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.

Block

begin(Collection<? extends Statement> statements)

Wrap a collection of statements in an anoymous procedural block.

Block

begin(Statement... statements)

Wrap a collection of statements in an anonymous procedural block.

BindContext

bindContext(PreparedStatement stmt)

Get a new BindContext for the context of this DSLContext.

CallArgsStep

call(String procedure)

The CALL statement.

CallArgsStep

call(Name procedure)

The CALL statement.

CommentOnIsStep

commentOnColumn(String field)

The COMMENT ON COLUMN statement.

CommentOnIsStep

commentOnColumn(Field<?> field)

The COMMENT ON COLUMN statement.

CommentOnIsStep

commentOnColumn(Name field)

The COMMENT ON COLUMN statement.

CommentOnIsStep

commentOnTable(String table)

The COMMENT ON TABLE statement.

CommentOnIsStep

commentOnTable(Name table)

The COMMENT ON TABLE statement.

CommentOnIsStep

commentOnTable(Table<?> table)

The COMMENT ON TABLE statement.

CommentOnIsStep

commentOnView(String view)

The COMMENT ON VIEW statement.

CommentOnIsStep

commentOnView(Name view)

The COMMENT ON VIEW statement.

CommentOnIsStep

commentOnView(Table<?> view)

The COMMENT ON VIEW statement.

Commit

commit(String id)

Initialise a Version.

Commits

commits()

Initialise a Commits graph.

Configuration

configuration()

The configuration of the current scope.

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().

CreateDatabaseFinalStep

createDatabase(String database)

The CREATE DATABASE statement.

CreateDatabaseFinalStep

createDatabase(Catalog database)

The CREATE DATABASE statement.

CreateDatabaseFinalStep

createDatabase(Name database)

The CREATE DATABASE statement.

CreateDatabaseFinalStep

createDatabaseIfNotExists(String database)

The CREATE DATABASE IF NOT EXISTS statement.

CreateDatabaseFinalStep

createDatabaseIfNotExists(Catalog database)

The CREATE DATABASE IF NOT EXISTS statement.

CreateDatabaseFinalStep

createDatabaseIfNotExists(Name database)

The CREATE DATABASE IF NOT EXISTS statement.

CreateDomainAsStep

createDomain(String domain)

The CREATE DOMAIN statement.

CreateDomainAsStep

createDomain(Domain<?> domain)

The CREATE DOMAIN statement.

CreateDomainAsStep

createDomain(Name domain)

The CREATE DOMAIN statement.

CreateDomainAsStep

createDomainIfNotExists(String domain)

The CREATE DOMAIN IF NOT EXISTS statement.

CreateDomainAsStep

createDomainIfNotExists(Domain<?> domain)

The CREATE DOMAIN IF NOT EXISTS statement.

CreateDomainAsStep

createDomainIfNotExists(Name domain)

The CREATE DOMAIN IF NOT EXISTS statement.

CreateFunctionParametersStep

createFunction(String function)

The CREATE FUNCTION statement.

CreateFunctionParametersStep

createFunction(Name function)

The CREATE FUNCTION statement.

CreateTableColumnStep

createGlobalTemporaryTable(String table)

Create a new DSL CREATE GLOBAL TEMPORARY TABLE statement.

CreateTableColumnStep

createGlobalTemporaryTable(Name table)

Create a new DSL CREATE GLOBAL TEMPORARY TABLE statement.

CreateTableColumnStep

createGlobalTemporaryTable(Table<?> table)

Create a new DSL CREATE GLOBAL TEMPORARY TABLE statement.

CreateIndexStep

createIndex()

The CREATE INDEX statement.

CreateIndexStep

createIndex(String index)

The CREATE INDEX statement.

CreateIndexStep

createIndex(Index index)

The CREATE INDEX statement.

CreateIndexStep

createIndex(Name index)

The CREATE INDEX statement.

CreateIndexStep

createIndexIfNotExists()

The CREATE INDEX IF NOT EXISTS statement.

CreateIndexStep

createIndexIfNotExists(String index)

The CREATE INDEX IF NOT EXISTS statement.

CreateIndexStep

createIndexIfNotExists(Index index)

The CREATE INDEX IF NOT EXISTS statement.

CreateIndexStep

createIndexIfNotExists(Name index)

The CREATE INDEX IF NOT EXISTS statement.

CreateFunctionParametersStep

createOrReplaceFunction(String function)

The CREATE OR REPLACE FUNCTION statement.

CreateFunctionParametersStep

createOrReplaceFunction(Name function)

The CREATE OR REPLACE FUNCTION statement.

CreateProcedureParametersStep

createOrReplaceProcedure(String procedure)

The CREATE OR REPLACE PROCEDURE statement.

CreateProcedureParametersStep

createOrReplaceProcedure(Name procedure)

The CREATE OR REPLACE PROCEDURE statement.

CreateTriggerEventStep

createOrReplaceTrigger(String trigger)

The CREATE OR REPLACE TRIGGER statement.

CreateTriggerEventStep

createOrReplaceTrigger(Name trigger)

The CREATE OR REPLACE TRIGGER statement.

CreateViewAsStep<Record>

createOrReplaceView(String view, String... fields)

Create a new DSL CREATE OR REPLACE VIEW statement.

CreateViewAsStep<Record>

createOrReplaceView(String view, BiFunction<? super Field<?>,? super Integer,? extends String> fieldNameFunction)

Create a new DSL CREATE OR REPLACE VIEW statement.

CreateViewAsStep<Record>

createOrReplaceView(String view, Function<? super Field<?>,? extends String> fieldNameFunction)

Create a new DSL CREATE OR REPLACE VIEW statement.

CreateViewAsStep<Record>

createOrReplaceView(Name view, BiFunction<? super Field<?>,? super Integer,? extends Name> fieldNameFunction)

Create a new DSL CREATE OR REPLACE VIEW statement.

CreateViewAsStep<Record>

createOrReplaceView(Name view, Function<? super Field<?>,? extends Name> fieldNameFunction)

Create a new DSL CREATE OR REPLACE VIEW statement.

CreateViewAsStep<Record>

createOrReplaceView(Name view, Name... fields)

Create a new DSL CREATE OR REPLACE VIEW statement.

CreateViewAsStep<Record>

createOrReplaceView(Table<?> view, BiFunction<? super Field<?>,? super Integer,? extends Field<?>> fieldNameFunction)

Create a new DSL CREATE OR REPLACE VIEW statement.

CreateViewAsStep<Record>

createOrReplaceView(Table<?> view, Function<? super Field<?>,? extends Field<?>> fieldNameFunction)

Create a new DSL CREATE OR REPLACE VIEW statement.

CreateViewAsStep<Record>

createOrReplaceView(Table<?> view, Field<?>... fields)

Create a new DSL CREATE OR REPLACE VIEW statement.

CreateProcedureParametersStep

createProcedure(String procedure)

The CREATE PROCEDURE statement.

CreateProcedureParametersStep

createProcedure(Name procedure)

The CREATE PROCEDURE statement.

CreateSchemaFinalStep

createSchema(String schema)

The CREATE SCHEMA statement.

CreateSchemaFinalStep

createSchema(Name schema)

The CREATE SCHEMA statement.

CreateSchemaFinalStep

createSchema(Schema schema)

The CREATE SCHEMA statement.

CreateSchemaFinalStep

createSchemaIfNotExists(String schema)

The CREATE SCHEMA IF NOT EXISTS statement.

CreateSchemaFinalStep

createSchemaIfNotExists(Name schema)

The CREATE SCHEMA IF NOT EXISTS statement.

CreateSchemaFinalStep

createSchemaIfNotExists(Schema schema)

The CREATE SCHEMA IF NOT EXISTS statement.

CreateSequenceFlagsStep

createSequence(String sequence)

The CREATE SEQUENCE statement.

CreateSequenceFlagsStep

createSequence(Name sequence)

The CREATE SEQUENCE statement.

CreateSequenceFlagsStep

createSequence(Sequence<?> sequence)

The CREATE SEQUENCE statement.

CreateSequenceFlagsStep

createSequenceIfNotExists(String sequence)

The CREATE SEQUENCE IF NOT EXISTS statement.

CreateSequenceFlagsStep

createSequenceIfNotExists(Name sequence)

The CREATE SEQUENCE IF NOT EXISTS statement.

CreateSequenceFlagsStep

createSequenceIfNotExists(Sequence<?> sequence)

The CREATE SEQUENCE IF NOT EXISTS statement.

CreateTableColumnStep

createTable(String table)

Create a new DSL CREATE TABLE statement.

CreateTableColumnStep

createTable(Name table)

Create a new DSL CREATE TABLE statement.

CreateTableColumnStep

createTable(Table<?> table)

Create a new DSL CREATE TABLE statement.

CreateTableColumnStep

createTableIfNotExists(String table)

Create a new DSL CREATE TABLE statement.

CreateTableColumnStep

createTableIfNotExists(Name table)

Create a new DSL CREATE TABLE statement.

CreateTableColumnStep

createTableIfNotExists(Table<?> table)

Create a new DSL CREATE TABLE statement.

CreateTableColumnStep

createTemporaryTable(String table)

Create a new DSL CREATE TEMPORARY TABLE statement.

CreateTableColumnStep

createTemporaryTable(Name table)

Create a new DSL CREATE TEMPORARY TABLE statement.

CreateTableColumnStep

createTemporaryTable(Table<?> table)

Create a new DSL CREATE TEMPORARY TABLE statement.

CreateTableColumnStep

createTemporaryTableIfNotExists(String table)

Create a new DSL CREATE TEMPORARY TABLE IF NOT EXISTS statement.

CreateTableColumnStep

createTemporaryTableIfNotExists(Name table)

Create a new DSL CREATE TEMPORARY TABLE IF NOT EXISTS statement.

CreateTableColumnStep

createTemporaryTableIfNotExists(Table<?> table)

Create a new DSL CREATE TEMPORARY TABLE IF NOT EXISTS statement.

CreateTriggerEventStep

createTrigger(String trigger)

The CREATE TRIGGER statement.

CreateTriggerEventStep

createTrigger(Name trigger)

The CREATE TRIGGER statement.

CreateTypeStep

createType(String type)

Create a new DSL CREATE TYPE statement.

CreateTypeStep

createType(Name type)

Create a new DSL CREATE TYPE statement.

CreateIndexStep

createUniqueIndex()

The CREATE UNIQUE INDEX statement.

CreateIndexStep

createUniqueIndex(String index)

The CREATE UNIQUE INDEX statement.

CreateIndexStep

createUniqueIndex(Index index)

The CREATE UNIQUE INDEX statement.

CreateIndexStep

createUniqueIndex(Name index)

The CREATE UNIQUE INDEX statement.

CreateIndexStep

createUniqueIndexIfNotExists()

The CREATE UNIQUE INDEX IF NOT EXISTS statement.

CreateIndexStep

createUniqueIndexIfNotExists(String index)

The CREATE UNIQUE INDEX IF NOT EXISTS statement.

CreateIndexStep

createUniqueIndexIfNotExists(Index index)

The CREATE UNIQUE INDEX IF NOT EXISTS statement.

CreateIndexStep

createUniqueIndexIfNotExists(Name index)

The CREATE UNIQUE INDEX IF NOT EXISTS statement.

CreateViewAsStep<Record>

createView(String view, String... fields)

Create a new DSL CREATE VIEW statement.

CreateViewAsStep<Record>

createView(String view, BiFunction<? super Field<?>,? super Integer,? extends String> fieldNameFunction)

Create a new DSL CREATE VIEW statement.

CreateViewAsStep<Record>

createView(String view, Function<? super Field<?>,? extends String> fieldNameFunction)

Create a new DSL CREATE VIEW statement.

CreateViewAsStep<Record>

createView(Name view, BiFunction<? super Field<?>,? super Integer,? extends Name> fieldNameFunction)

Create a new DSL CREATE VIEW statement.

CreateViewAsStep<Record>

createView(Name view, 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(Table<?> view, BiFunction<? super Field<?>,? super Integer,? extends Field<?>> fieldNameFunction)

Create a new DSL CREATE VIEW statement.

CreateViewAsStep<Record>

createView(Table<?> view, Function<? super Field<?>,? 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>

createViewIfNotExists(String view, String... fields)

Create a new DSL CREATE VIEW statement.

CreateViewAsStep<Record>

createViewIfNotExists(String view, BiFunction<? super Field<?>,? super Integer,? extends String> fieldNameFunction)

Create a new DSL CREATE VIEW statement.

CreateViewAsStep<Record>

createViewIfNotExists(String view, Function<? super Field<?>,? extends String> fieldNameFunction)

Create a new DSL CREATE VIEW statement.

CreateViewAsStep<Record>

createViewIfNotExists(Name view, BiFunction<? super Field<?>,? super Integer,? extends Name> fieldNameFunction)

Create a new DSL CREATE VIEW statement.

CreateViewAsStep<Record>

createViewIfNotExists(Name view, 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(Table<?> view, BiFunction<? super Field<?>,? super Integer,? extends Field<?>> fieldNameFunction)

Create a new DSL CREATE VIEW statement.

CreateViewAsStep<Record>

createViewIfNotExists(Table<?> view, Function<? super Field<?>,? extends Field<?>> fieldNameFunction)

Create a new DSL CREATE VIEW statement.

CreateViewAsStep<Record>

createViewIfNotExists(Table<?> view, Field<?>... fields)

Create a new DSL CREATE VIEW statement.

BigInteger

currval(String sequence)

Convenience method to fetch the CURRVAL for a sequence directly from this DSLContext's underlying JDBC Connection.

BigInteger

currval(Name sequence)

Convenience method to fetch the CURRVAL for a sequence directly from this DSLContext's underlying JDBC Connection.

<T extends Number> T

currval(Sequence<T> sequence)

Convenience method to fetch the CURRVAL for a sequence directly from this DSLContext's underlying JDBC Connection.

Map<Object,Object>

data()

Get all custom data from this Scope.

Object

data(Object key)

Get some custom data from this Scope.

Object

data(Object key, Object value)

Set some custom data to this Scope.

Queries

ddl(Collection<? extends Table<?>> tables)

Convenience method for Meta.ddl().

Queries

ddl(Collection<? extends Table<?>> tables, DDLExportConfiguration exportConfiguration)

Convenience method for Meta.ddl(DDLExportConfiguration).

Queries

ddl(Collection<? extends Table<?>> tables, DDLFlag... flags)

Convenience method for Meta.ddl(DDLExportConfiguration).

Queries

ddl(Catalog catalog)

Convenience method for Meta.ddl().

Queries

ddl(Catalog catalog, DDLExportConfiguration exportConfiguration)

Convenience method for Meta.ddl(DDLExportConfiguration).

Queries

ddl(Catalog catalog, DDLFlag... flags)

Convenience method for Meta.ddl(DDLExportConfiguration).

Queries

ddl(Schema schema)

Convenience method for Meta.ddl().

Queries

ddl(Schema schema, DDLExportConfiguration exportConfiguration)

Convenience method for Meta.ddl(DDLExportConfiguration).

Queries

ddl(Schema schema, DDLFlag... flags)

Convenience method for Meta.ddl(DDLExportConfiguration).

Queries

ddl(Table... tables)

Convenience method for Meta.ddl().

Queries

ddl(Table[] tables, DDLExportConfiguration exportConfiguration)

Convenience method for Meta.ddl(DDLExportConfiguration).

Queries

ddl(Table[] tables, DDLFlag... flags)

Convenience method for Meta.ddl(DDLExportConfiguration).

Queries

ddl(Table<?> table)

Convenience method for Meta.ddl().

Queries

ddl(Table<?> table, DDLExportConfiguration exportConfiguration)

Convenience method for Meta.ddl(DDLExportConfiguration).

Queries

ddl(Table<?> table, DDLFlag... flags)

Convenience method for Meta.ddl(DDLExportConfiguration).

<R extends Record> DeleteUsingStep<R>

delete(Table<R> table)

Create a new DSL delete statement.

<R extends Record> DeleteUsingStep<R>

deleteFrom(Table<R> table)

Create a new DSL delete statement.

<R extends Record> DeleteQuery<R>

deleteQuery(Table<R> table)

Create a new DeleteQuery

Connection

diagnosticsConnection()

A JDBC connection that proxies the underlying connection to run the jOOQ Diagnostics Pack on executed queries.

DataSource

diagnosticsDataSource()

A JDBC connection that proxies the underlying connection to run the jOOQ Diagnostics Pack on executed queries.

SQLDialect

dialect()

The SQLDialect wrapped by this context.

DropDatabaseFinalStep

dropDatabase(String database)

The DROP DATABASE statement.

DropDatabaseFinalStep

dropDatabase(Catalog database)

The DROP DATABASE statement.

DropDatabaseFinalStep

dropDatabase(Name database)

The DROP DATABASE statement.

DropDatabaseFinalStep

dropDatabaseIfExists(String database)

The DROP DATABASE IF EXISTS statement.

DropDatabaseFinalStep

dropDatabaseIfExists(Catalog database)

The DROP DATABASE IF EXISTS statement.

DropDatabaseFinalStep

dropDatabaseIfExists(Name database)

The DROP DATABASE IF EXISTS statement.

DropDomainCascadeStep

dropDomain(String domain)

The DROP DOMAIN statement.

DropDomainCascadeStep

dropDomain(Domain<?> domain)

The DROP DOMAIN statement.

DropDomainCascadeStep

dropDomain(Name domain)

The DROP DOMAIN statement.

DropDomainCascadeStep

dropDomainIfExists(String domain)

The DROP DOMAIN IF EXISTS statement.

DropDomainCascadeStep

dropDomainIfExists(Domain<?> domain)

The DROP DOMAIN IF EXISTS statement.

DropDomainCascadeStep

dropDomainIfExists(Name domain)

The DROP DOMAIN IF EXISTS statement.

DDLQuery

dropFunction(String function)

The DROP FUNCTION statement.

DDLQuery

dropFunction(Name function)

The DROP FUNCTION statement.

DDLQuery

dropFunctionIfExists(String function)

The DROP FUNCTION IF EXISTS statement.

DDLQuery

dropFunctionIfExists(Name function)

The DROP FUNCTION IF EXISTS statement.

DropIndexOnStep

dropIndex(String index)

The DROP INDEX statement.

DropIndexOnStep

dropIndex(Index index)

The DROP INDEX statement.

DropIndexOnStep

dropIndex(Name index)

The DROP INDEX statement.

DropIndexOnStep

dropIndexIfExists(String index)

The DROP INDEX IF EXISTS statement.

DropIndexOnStep

dropIndexIfExists(Index index)

The DROP INDEX IF EXISTS statement.

DropIndexOnStep

dropIndexIfExists(Name index)

The DROP INDEX IF EXISTS statement.

DDLQuery

dropProcedure(String procedure)

The DROP PROCEDURE statement.

DDLQuery

dropProcedure(Name procedure)

The DROP PROCEDURE statement.

DDLQuery

dropProcedureIfExists(String procedure)

The DROP PROCEDURE IF EXISTS statement.

DDLQuery

dropProcedureIfExists(Name procedure)

The DROP PROCEDURE IF EXISTS statement.

DropSchemaStep

dropSchema(String schema)

The DROP SCHEMA statement.

DropSchemaStep

dropSchema(Name schema)

The DROP SCHEMA statement.

DropSchemaStep

dropSchema(Schema schema)

The DROP SCHEMA statement.

DropSchemaStep

dropSchemaIfExists(String schema)

The DROP SCHEMA IF EXISTS statement.

DropSchemaStep

dropSchemaIfExists(Name schema)

The DROP SCHEMA IF EXISTS statement.

DropSchemaStep

dropSchemaIfExists(Schema schema)

The DROP SCHEMA IF EXISTS statement.

DropSequenceFinalStep

dropSequence(String sequence)

The DROP SEQUENCE statement.

DropSequenceFinalStep

dropSequence(Name sequence)

The DROP SEQUENCE statement.

DropSequenceFinalStep

dropSequence(Sequence<?> sequence)

The DROP SEQUENCE statement.

DropSequenceFinalStep

dropSequenceIfExists(String sequence)

The DROP SEQUENCE IF EXISTS statement.

DropSequenceFinalStep

dropSequenceIfExists(Name sequence)

The DROP SEQUENCE IF EXISTS statement.

DropSequenceFinalStep

dropSequenceIfExists(Sequence<?> sequence)

The DROP SEQUENCE IF EXISTS statement.

DropTableStep

dropTable(String table)

The DROP TABLE statement.

DropTableStep

dropTable(Name table)

The DROP TABLE statement.

DropTableStep

dropTable(Table<?> table)

The DROP TABLE statement.

DropTableStep

dropTableIfExists(String table)

The DROP TABLE IF EXISTS statement.

DropTableStep

dropTableIfExists(Name table)

The DROP TABLE IF EXISTS statement.

DropTableStep

dropTableIfExists(Table<?> table)

The DROP TABLE IF EXISTS statement.

DropTableStep

dropTemporaryTable(String table)

The DROP TEMPORARY TABLE statement.

DropTableStep

dropTemporaryTable(Name table)

The DROP TEMPORARY TABLE statement.

DropTableStep

dropTemporaryTable(Table<?> table)

The DROP TEMPORARY TABLE statement.

DropTableStep

dropTemporaryTableIfExists(String table)

The DROP TEMPORARY TABLE IF EXISTS statement.

DropTableStep

dropTemporaryTableIfExists(Name table)

The DROP TEMPORARY TABLE IF EXISTS statement.

DropTableStep

dropTemporaryTableIfExists(Table<?> table)

The DROP TEMPORARY TABLE IF EXISTS statement.

DDLQuery

dropTrigger(String trigger)

The DROP TRIGGER statement.

DDLQuery

dropTrigger(Name trigger)

The DROP TRIGGER statement.

DDLQuery

dropTriggerIfExists(String trigger)

The DROP TRIGGER IF EXISTS statement.

DDLQuery

dropTriggerIfExists(Name trigger)

The DROP TRIGGER IF EXISTS statement.

DropTypeStep

dropType(String type)

Create a new DSL DROP TYPE statement.

DropTypeStep

dropType(String... type)

Create a new DSL DROP TYPE statement.

DropTypeStep

dropType(Collection<?> type)

Create a new DSL DROP TYPE statement.

DropTypeStep

dropType(Name type)

Create a new DSL DROP TYPE statement.

DropTypeStep

dropType(Name... type)

Create a new DSL DROP TYPE statement.

DropTypeStep

dropTypeIfExists(String type)

Create a new DSL DROP TYPE statement.

DropTypeStep

dropTypeIfExists(String... type)

Create a new DSL DROP TYPE statement.

DropTypeStep

dropTypeIfExists(Collection<?> type)

Create a new DSL DROP TYPE statement.

DropTypeStep

dropTypeIfExists(Name type)

Create a new DSL DROP TYPE statement.

DropTypeStep

dropTypeIfExists(Name... type)

Create a new DSL DROP TYPE statement.

DropViewFinalStep

dropView(String view)

The DROP VIEW statement.

DropViewFinalStep

dropView(Name view)

The DROP VIEW statement.

DropViewFinalStep

dropView(Table<?> view)

The DROP VIEW statement.

DropViewFinalStep

dropViewIfExists(String view)

The DROP VIEW IF EXISTS statement.

DropViewFinalStep

dropViewIfExists(Name view)

The DROP VIEW IF EXISTS statement.

DropViewFinalStep

dropViewIfExists(Table<?> view)

The DROP VIEW IF EXISTS statement.

DSLContext

dsl()

Wrap the Scope.configuration() in a DSLContext, providing access to the configuration-contextual DSL to construct executable queries.

int

execute(String sql)

Execute a query holding plain SQL.

int

execute(String sql, Object... bindings)

Execute a new query holding plain SQL.

int

execute(String sql, QueryPart... parts)

Execute a new query holding plain SQL.

int

execute(Query query)

Execute a Query in the context of this DSLContext.

int

execute(SQL sql)

Execute a query holding plain SQL.

int

executeDelete(TableRecord<?> record, Condition condition)

Delete a record from a table.

int

executeDelete(UpdatableRecord<?> record)

Delete a record from a table.

int

executeInsert(TableRecord<?> record)

Insert one record.

int

executeUpdate(TableRecord<?> record, Condition condition)

Update a table.

int

executeUpdate(UpdatableRecord<?> record)

Update a table.

Explain

explain(Query query)

Run an EXPLAIN statement in the database to estimate the cardinality of the query.

List<Object>

extractBindValues(QueryPart part)

Retrieve the bind values that will be bound by a given QueryPart.

Param<?>

extractParam(QueryPart part, String name)

Get a named parameter from a QueryPart, provided its name.

Map<String,Param<?>>

extractParams(QueryPart part)

Get a Map of named parameters.

SQLDialect

family()

The SQLDialect.family() wrapped by this context.

Result<Record>

fetch(String sql)

Execute a new query holding plain SQL.

Result<Record>

fetch(String sql, Object... bindings)

Execute a new query holding plain SQL.

Result<Record>

fetch(String sql, QueryPart... parts)

Execute a new query holding plain SQL.

Result<Record>

fetch(ResultSet rs)

Fetch all data from a JDBC ResultSet and transform it to a jOOQ Result.

Result<Record>

fetch(ResultSet rs, Class<?>... types)

Fetch all data from a JDBC ResultSet and transform it to a jOOQ Result.

Result<Record>

fetch(ResultSet rs, DataType<?>... types)

Fetch all data from a JDBC ResultSet and transform it to a jOOQ Result.

Result<Record>

fetch(ResultSet rs, Field<?>... fields)

Fetch all data from a JDBC ResultSet and transform it to a jOOQ Result.

<R extends Record> Result<R>

fetch(ResultQuery<R> query)

Execute a ResultQuery in the context of this DSLContext and return results.

Result<Record>

fetch(SQL sql)

Execute a new query holding plain SQL.

<R extends Record> Result<R>

fetch(Table<R> table)

Execute and return all records for
<R extends Record> Result<R> fetch(Table<R> table, Collection<? extends Condition> conditions) Execute and return all records for <R extends Record> Result<R> fetch(Table<R> table, Condition condition) Execute and return all records for <R extends Record> Result<R> fetch(Table<R> table, Condition... conditions) Execute and return all records for <R extends Record> R fetchAny(Table<R> table) Execute and return zero or one record for <R extends Record> R fetchAny(Table<R> table, Collection<? extends Condition> conditions) Execute and return zero or one record for <R extends Record> R fetchAny(Table<R> table, Condition condition) Execute and return zero or one record for <R extends Record> R fetchAny(Table<R> table, Condition... conditions) Execute and return zero or on e record for CompletionStage<Result<Record>> fetchAsync(String sql) Fetch results in a new CompletionStage. CompletionStage<Result<Record>> fetchAsync(String sql, Object... bindings) Fetch results in a new CompletionStage. CompletionStage<Result<Record>> fetchAsync(String sql, QueryPart... parts) Fetch results in a new CompletionStage. CompletionStage<Result<Record>> fetchAsync(ResultSet rs) Fetch results in a new CompletionStage. CompletionStage<Result<Record>> fetchAsync(ResultSet rs, Class<?>... types) Fetch results in a new CompletionStage. CompletionStage<Result<Record>> fetchAsync(ResultSet rs, DataType<?>... types) Fetch results in a new CompletionStage. CompletionStage<Result<Record>> fetchAsync(ResultSet rs, Field<?>... fields) Fetch results in a new CompletionStage. CompletionStage<Result<Record>> fetchAsync(Executor executor, String sql) Fetch results in a new CompletionStage that is asynchronously completed by a task running in the given executor. CompletionStage<Result<Record>> fetchAsync(Executor executor, String sql, Object... bindings) Fetch results in a new CompletionStage that is asynchronously completed by a task running in the given executor. CompletionStage<Result<Record>> fetchAsync(Executor executor, String sql, QueryPart... parts) Fetch results in a new CompletionStage that is asynchronously completed by a task running in the given executor. CompletionStage<Result<Record>> fetchAsync(Executor executor, ResultSet rs) Fetch results in a new CompletionStage that is asynchronously completed by a task running in the given executor. CompletionStage<Result<Record>> fetchAsync(Executor executor, ResultSet rs, Class<?>... types) Fetch results in a new CompletionStage that is asynchronously completed by a task running in the given executor. CompletionStage<Result<Record>> fetchAsync(Executor executor, ResultSet rs, DataType<?>... types) Fetch results in a new CompletionStage that is asynchronously completed by a task running in the given executor. CompletionStage<Result<Record>> fetchAsync(Executor executor, ResultSet rs, Field<?>... fields) Fetch results in a new CompletionStage that is asynchronously completed by a task running in the given executor. <R extends Record> CompletionStage<Result<R>> fetchAsync(Executor executor, ResultQuery<R> query) Fetch results in a new CompletionStage that is asynchronously completed by a task running in the given executor. CompletionStage<Result<Record>> fetchAsync(Executor executor, SQL sql) Fetch results in a new CompletionStage that is asynchronously completed by a task running in the given executor. <R extends Record> CompletionStage<Result<R>> fetchAsync(Executor executor, Table<R> table) Execute and return all records asynchronously for <R extends Record> CompletionStage<Result<R>> fetchAsync(Executor executor, Table<R> table, Collection<? extends Condition> conditions) Execute and return all records asynchronously for <R extends Record> CompletionStage<Result<R>> fetchAsync(Executor executor, Table<R> table, Condition condition) Execute and return all records asynchronously for <R extends Record> CompletionStage<Result<R>> fetchAsync(Executor executor, Table<R> table, Condition... conditions) Execute and return all records asynchronously for <R extends Record> CompletionStage<Result<R>> fetchAsync(ResultQuery<R> query) Fetch results in a new CompletionStage. CompletionStage<Result<Record>> fetchAsync(SQL sql) Fetch results in a new CompletionStage. <R extends Record> CompletionStage<Result<R>> fetchAsync(Table<R> table) Execute and return all records asynchronously for <R extends Record> CompletionStage<Result<R>> fetchAsync(Table<R> table, Collection<? extends Condition> conditions) Execute and return all records asynchronously for <R extends Record> CompletionStage<Result<R>> fetchAsync(Table<R> table, Condition condition) Execute and return all records asynchronously for <R extends Record> CompletionStage<Result<R>> fetchAsync(Table<R> table, Condition... conditions) Execute and return all records asynchronously for <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, Collection<? extends Condition> conditions) Count the number of records in a table that satisfy a condition. int fetchCount(Table<?> table, Condition condition) Count the number of records in a table that satisfy a condition. int fetchCount(Table<?> table, Condition... conditions) 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, Collection<? extends Condition> conditions) Check if a table has any records that satisfy a condition. boolean fetchExists(Table<?> table, Condition condition) Check if a table has any records that satisfy a condition. boolean fetchExists(Table<?> table, Condition... conditions) Check if a table has any records that satisfy a condition. Result<Record> fetchFromCSV(String string) Fetch all data from a CSV string. Result<Record> fetchFromCSV(String string, boolean header) Fetch all data from a CSV string. Result<Record> fetchFromCSV(String string, boolean header, char delimiter) Fetch all data from a CSV string. Result<Record> fetchFromCSV(String string, char delimiter) Fetch all data from a CSV string. Result<Record> fetchFromHTML(String string) Convert an HTML table into a jOOQ Result. Result<Record> fetchFromJSON(String string) Fetch all data from a JSON string. Result<Record> fetchFromStringData(String[]... strings) Fetch all data from a list of strings. Result<Record> fetchFromStringData(List<String[]> strings) Fetch all data from a list of strings. Result<Record> fetchFromStringData(List<String[]> strings, boolean header) Fetch all data from a list of strings. Result<Record> fetchFromTXT(String string) Fetch all data from a formatted string. Result<Record> fetchFromTXT(String string, String nullLiteral) Fetch all data from a formatted string. Result<Record> fetchFromXML(String string) Fetch all data from an XML string. Cursor<Record> fetchLazy(String sql) Execute a new query holding plain SQL and "lazily" return the generated result. Cursor<Record> fetchLazy(String sql, Object... bindings) Execute a new query holding plain SQL and "lazily" return the generated result. Cursor<Record> fetchLazy(String sql, QueryPart... parts) Execute a new query holding plain SQL and "lazily" return the generated result. Cursor<Record> fetchLazy(ResultSet rs) Wrap a JDBC ResultSet into a jOOQ Cursor. Cursor<Record> fetchLazy(ResultSet rs, Class<?>... types) Wrap a JDBC ResultSet into a jOOQ Cursor. Cursor<Record> fetchLazy(ResultSet rs, DataType<?>... types) Wrap a JDBC ResultSet into a jOOQ Cursor. Cursor<Record> fetchLazy(ResultSet rs, Field<?>... fields) Wrap a JDBC ResultSet into a jOOQ Cursor. <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(SQL sql) 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 <R extends Record> Cursor<R> fetchLazy(Table<R> table, Collection<? extends Condition> conditions) Execute and return all records lazily for <R extends Record> Cursor<R> fetchLazy(Table<R> table, Condition condition) Execute and return all records lazily for <R extends Record> Cursor<R> fetchLazy(Table<R> table, Condition... conditions) Execute and return all records lazily for Results fetchMany(String sql) Execute a new query holding plain SQL, possibly returning several result sets. Results fetchMany(String sql, Object... bindings) Execute a new query holding plain SQL, possibly returning several result sets. Results fetchMany(String sql, QueryPart... parts) Execute a new query holding plain SQL, possibly returning several result sets. <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. Record fetchOne(String sql) Execute a new query holding plain SQL. Record fetchOne(String sql, Object... bindings) Execute a new query holding plain SQL. Record fetchOne(String sql, QueryPart... parts) Execute a new query holding plain SQL. Record fetchOne(ResultSet rs) Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record. Record fetchOne(ResultSet rs, Class<?>... types) Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record. Record fetchOne(ResultSet rs, DataType<?>... types) Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record. Record fetchOne(ResultSet rs, Field<?>... fields) Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record. <R extends Record> R fetchOne(ResultQuery<R> query) Execute a ResultQuery in the context of this DSLContext and return a record. Record fetchOne(SQL sql) Execute a new query holding plain SQL. <R extends Record> R fetchOne(Table<R> table) Execute and return zero or one record for <R extends Record> R fetchOne(Table<R> table, Collection<? extends Condition> conditions) Execute and return zero or one record for <R extends Record> R fetchOne(Table<R> table, Condition condition) Execute and return zero or one record for <R extends Record> R fetchOne(Table<R> table, Condition... conditions) Execute and return zero or one record for Optional<Record> fetchOptional(String sql) Execute a new query holding plain SQL. Optional<Record> fetchOptional(String sql, Object... bindings) Execute a new query holding plain SQL. Optional<Record> fetchOptional(String sql, QueryPart... parts) Execute a new query holding plain SQL. Optional<Record> fetchOptional(ResultSet rs) Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record. Optional<Record> fetchOptional(ResultSet rs, Class<?>... types) Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record. Optional<Record> fetchOptional(ResultSet rs, DataType<?>... types) Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record. Optional<Record> fetchOptional(ResultSet rs, Field<?>... fields) Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record. <R extends Record> Optional<R> fetchOptional(ResultQuery<R> query) Execute a ResultQuery in the context of this DSLContext and return a record. Optional<Record> fetchOptional(SQL sql) Execute a new query holding plain SQL. <R extends Record> Optional<R> fetchOptional(Table<R> table) Execute and return zero or one record for <R extends Record> Optional<R> fetchOptional(Table<R> table, Collection<? extends Condition> conditions) Execute and return zero or one record for <R extends Record> Optional<R> fetchOptional(Table<R> table, Condition condition) Execute and return zero or one record for <R extends Record> Optional<R> fetchOptional(Table<R> table, Condition... conditions) Execute and return zero or one record for Optional<?> fetchOptionalValue(String sql) Execute a new query holding plain SQL. Optional<?> fetchOptionalValue(String sql, Object... bindings) Execute a new query holding plain SQL. Optional<?> fetchOptionalValue(String sql, QueryPart... parts) Execute a new query holding plain SQL. Optional<?> fetchOptionalValue(ResultSet rs) Fetch a record from a JDBC ResultSet and return the only contained value. <T> Optional<T> fetchOptionalValue(ResultSet rs, Class<T> type) Fetch a record from a JDBC ResultSet and return the only contained value. <T> Optional<T> fetchOptionalValue(ResultSet rs, DataType<T> type) Fetch a record from a JDBC ResultSet and return the only contained value. <T> Optional<T> fetchOptionalValue(ResultSet rs, Field<T> field) Fetch a record from a JDBC ResultSet and return the only contained value. <T, R extends Record1<T>> Optional<T> fetchOptionalValue(ResultQuery<R> query) Execute a ResultQuery in the context of this DSLContext and return a single value. Optional<?> fetchOptionalValue(SQL sql) Execute a new query holding plain SQL. <T> Optional<T> fetchOptionalValue(TableField<?,T> field) Execute a ResultQuery in the context of this DSLContext and return a single value. Record fetchSingle(String sql) Execute a new query holding plain SQL. Record fetchSingle(String sql, Object... bindings) Execute a new query holding plain SQL. Record fetchSingle(String sql, QueryPart... parts) Execute a new query holding plain SQL. Record fetchSingle(ResultSet rs) Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record. Record fetchSingle(ResultSet rs, Class<?>... types) Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record. Record fetchSingle(ResultSet rs, DataType<?>... types) Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record. Record fetchSingle(ResultSet rs, Field<?>... fields) Fetch a record from a JDBC ResultSet and transform it to a jOOQ Record. Record fetchSingle(Collection<? extends SelectField<?>> fields) Execute and return exactly one record for <R extends Record> R fetchSingle(ResultQuery<R> query) Execute a ResultQuery in the context of this DSLContext and return a record. Record fetchSingle(SelectField<?>... fields) Execute and return exactly one record for <T1> Record1<T1> fetchSingle(SelectField<T1> field1) Execute and return exactly one record for <T1, T2> Record2<T1,T2> fetchSingle(SelectField<T1> field1, SelectField<T2> field2) Execute and return exactly one record for <T1, T2, T3> Record3<T1,T2,T3> fetchSingle(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3) Execute and return exactly one record for <T1, T2, T3, T4> Record4<T1,T2,T3,T4> fetchSingle(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4) Execute and return exactly one record for <T1, T2, T3, T4, T5> Record5<T1,T2,T3,T4,T5> fetchSingle(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5) Execute and return exactly one record for <T1, T2, T3, T4, T5, T6> Record6<T1,T2,T3,T4,T5,T6> fetchSingle(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6) Execute and return exactly one record for <T1, T2, T3, T4, T5, T6, T7> Record7<T1,T2,T3,T4,T5,T6,T7> fetchSingle(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7) Execute and return exactly one record for <T1, T2, T3, T4, T5, T6, T7, T8> Record8<T1,T2,T3,T4,T5,T6,T7,T8> fetchSingle(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8) Execute and return exactly one record for <T1, T2, T3, T4, T5, T6, T7, T8, T9> Record9<T1,T2,T3,T4,T5,T6,T7,T8,T9> fetchSingle(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) Execute and return exactly one record for <T1, T2, T3, T4, T5, T6, T7, T8, T9, T10> Record10<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10> fetchSingle(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) Execute and return exactly one record for <T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11> Record11<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11> fetchSingle(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) Execute and return exactly one record for <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> fetchSingle(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) Execute and return exactly one record for <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> fetchSingle(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) Execute and return exactly one record for <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> fetchSingle(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) Execute and return exactly one record for <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> fetchSingle(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) Execute and return exactly one record for <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> fetchSingle(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) Execute and return exactly one record for <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> fetchSingle(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) Execute and return exactly one record for <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> fetchSingle(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) Execute and return exactly one record for <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> fetchSingle(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) Execute and return exactly one record for <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> fetchSingle(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) Execute and return exactly one record for <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> fetchSingle(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) Execute and return exactly one record for <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> fetchSingle(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) Execute and return exactly one record for Record fetchSingle(SQL sql) Execute a new query holding plain SQL. <R extends Record> R fetchSingle(Table<R> table) Execute and return exactly one record for <R extends Record> R fetchSingle(Table<R> table, Collection<? extends Condition> conditions) Execute and return exactly one record for <R extends Record> R fetchSingle(Table<R> table, Condition condition) Execute and return exactly one record for <R extends Record> R fetchSingle(Table<R> table, Condition... conditions) Execute and return exactly one record for Stream<Record> fetchStream(String sql) Execute a new query holding plain SQL and "lazily" return the generated result. Stream<Record> fetchStream(String sql, Object... bindings) Execute a new query holding plain SQL and "lazily" return the generated result. Stream<Record> fetchStream(String sql, QueryPart... parts) Execute a new query holding plain SQL and "lazily" return the generated result. Stream<Record> fetchStream(ResultSet rs) Wrap a JDBC ResultSet into a jOOQ Stream. Stream<Record> fetchStream(ResultSet rs, Class<?>... types) Wrap a JDBC ResultSet into a jOOQ Stream. Stream<Record> fetchStream(ResultSet rs, DataType<?>... types) Wrap a JDBC ResultSet into a jOOQ Stream. Stream<Record> fetchStream(ResultSet rs, Field<?>... fields) Wrap a JDBC ResultSet into a jOOQ Stream. <R extends Record> Stream<R> fetchStream(ResultQuery<R> query) Execute a ResultQuery in the context of this DSLContext and return a stream. Stream<Record> fetchStream(SQL sql) Execute a new query holding plain SQL and "lazily" return the generated result. <R extends Record> Stream<R> fetchStream(Table<R> table) Execute and return all records lazily for <R extends Record> Stream<R> fetchStream(Table<R> table, Collection<? extends Condition> conditions) Execute and return all records lazily for <R extends Record> Stream<R> fetchStream(Table<R> table, Condition condition) Execute and return all records lazily for <R extends Record> Stream<R> fetchStream(Table<R> table, Condition... conditions) Execute and return all records lazily for Object fetchValue(String sql) Execute a new query holding plain SQL. Object fetchValue(String sql, Object... bindings) Execute a new query holding plain SQL. Object fetchValue(String sql, QueryPart... parts) Execute a new query holding plain SQL. Object fetchValue(ResultSet rs) Fetch a record from a JDBC ResultSet and return the only contained value. <T> T fetchValue(ResultSet rs, Class<T> type) Fetch a record from a JDBC ResultSet and return the only contained value. <T> T fetchValue(ResultSet rs, DataType<T> type) Fetch a record from a JDBC ResultSet and return the only contained value. <T> T fetchValue(ResultSet rs, Field<T> field) Fetch a record from a JDBC ResultSet and return the only contained value. <T, R extends Record1<T>> T fetchValue(ResultQuery<R> query) Execute a ResultQuery in the context of this DSLContext and return a single value. <T> T fetchValue(SelectField<T> field) Execute a ResultQuery in the context of this DSLContext and return a single value. Object fetchValue(SQL sql) Execute a new query holding plain SQL. <T> T fetchValue(Table<? extends Record1<T>> table) Fetch a single value from a single column table. <T> T fetchValue(TableField<?,T> field) Execute a ResultQuery in the context of this DSLContext and return a single value. List<?> fetchValues(String sql) Execute a new query holding plain SQL. List<?> fetchValues(String sql, Object... bindings) Execute a new query holding plain SQL. List<?> fetchValues(String sql, QueryPart... parts) Execute a new query holding plain SQL. List<?> fetchValues(ResultSet rs) Fetch a result from a JDBC ResultSet and return the only contained column's values. <T> List<T> fetchValues(ResultSet rs, Class<T> type) Fetch a result from a JDBC ResultSet and return the only contained column's values. <T> List<T> fetchValues(ResultSet rs, DataType<T> type) Fetch a result from a JDBC ResultSet and return the only contained column's values. <T> List<T> fetchValues(ResultSet rs, Field<T> field) Fetch a result from a JDBC ResultSet and return the only contained column's values. <T, R extends Record1<T>> List<T> fetchValues(ResultQuery<R> query) Execute a ResultQuery in the context of this DSLContext and return all values for the only column. List<?> fetchValues(SQL sql) Execute a new query holding plain SQL. <T> List<T> fetchValues(Table<? extends Record1<T>> table) Fetch all values from a single column table. <T> List<T> fetchValues(TableField<?,T> field) Fetch all values in a given Table's TableField. GrantOnStep grant(Collection<? extends Privilege> privileges) The GRANT statement. GrantOnStep grant(Privilege privileges) The GRANT statement. GrantOnStep grant(Privilege... privileges) The GRANT statement. InformationSchema informationSchema(Catalog catalog) Convenience method for Meta.informationSchema(). InformationSchema informationSchema(Catalog... catalogs) Convenience method for Meta.informationSchema(). InformationSchema informationSchema(Schema schema) Convenience method for Meta.informationSchema(). InformationSchema informationSchema(Schema... schemas) Convenience method for Meta.informationSchema(). InformationSchema informationSchema(Table<?> table) Convenience method for Meta.informationSchema(). InformationSchema informationSchema(Table<?>... tables) Convenience method for Meta.informationSchema(). <R extends Record> InsertSetStep<R> insertInto(Table<R> into) Create a new DSL insert statement. <R extends Record> InsertValuesStepN<R> insertInto(Table<R> into, 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 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, 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) Deprecated, for removal: This API element is subject to removal in a future version. - [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table) <R extends Record, T1, T2> MergeKeyStep2<R,T1,T2> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2) Deprecated, for removal: This API element is subject to removal in a future version. - [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table) <R extends Record, T1, T2, T3> MergeKeyStep3<R,T1,T2,T3> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3) Deprecated, for removal: This API element is subject to removal in a future version. - [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table) <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) Deprecated, for removal: This API element is subject to removal in a future version. - [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table) <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) Deprecated, for removal: This API element is subject to removal in a future version. - [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table) <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) Deprecated, for removal: This API element is subject to removal in a future version. - [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table) <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) Deprecated, for removal: This API element is subject to removal in a future version. - [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table) <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) Deprecated, for removal: This API element is subject to removal in a future version. - [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table) <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) Deprecated, for removal: This API element is subject to removal in a future version. - [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table) <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) Deprecated, for removal: This API element is subject to removal in a future version. - [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table) <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) Deprecated, for removal: This API element is subject to removal in a future version. - [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table) <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) Deprecated, for removal: This API element is subject to removal in a future version. - [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table) <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) Deprecated, for removal: This API element is subject to removal in a future version. - [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table) <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) Deprecated, for removal: This API element is subject to removal in a future version. - [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table) <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) Deprecated, for removal: This API element is subject to removal in a future version. - [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table) <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) Deprecated, for removal: This API element is subject to removal in a future version. - [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table) <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) Deprecated, for removal: This API element is subject to removal in a future version. - [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table) <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) Deprecated, for removal: This API element is subject to removal in a future version. - [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table) <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) Deprecated, for removal: This API element is subject to removal in a future version. - [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table) <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) Deprecated, for removal: This API element is subject to removal in a future version. - [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table) <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) Deprecated, for removal: This API element is subject to removal in a future version. - [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table) <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) Deprecated, for removal: This API element is subject to removal in a future version. - [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table) Meta meta() Access the database meta data. Meta meta(String... sources) Create meta data from a set of sources. Meta meta(DatabaseMetaData meta) Access the database meta data from an explicit JDBC DatabaseMetaData. Meta meta(Catalog... catalogs) Access the database meta data from explicit catalog information. Meta meta(Query... queries) Create meta data from a set of DDL queries. Meta meta(Schema... schemas) Access the database meta data from explicit schema information. Meta meta(Source... sources) Create meta data from a set of sources. Meta meta(Table<?>... tables) Access the database meta data from explicit table information. Meta meta(InformationSchema schema) Access the database meta data from an explicit JAXB-annotated meta model. Migration migrateTo(Commit to) Create a migration from the currently installed version to a new version. 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(Collection<? extends Field<?>> fields) Create a new empty Record. 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, 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(Collection<? extends Field<?>> fields) Create a new empty Record. 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. BigInteger nextval(String sequence) Convenience method to fetch the NEXTVAL for a sequence directly from this DSLContext's underlying JDBC Connection. BigInteger nextval(Name sequence) Convenience method to fetch the NEXTVAL for a sequence directly from this DSLContext's underlying JDBC Connection. <T extends Number> T nextval(Sequence<T> sequence) Convenience method to fetch the NEXTVAL for a sequence directly from this DSLContext's underlying JDBC Connection. <T extends Number> List<T> nextvals(Sequence<T> sequence, int size) Convenience method to fetch several NEXTVAL for a sequence directly from this DSLContext's underlying JDBC Connection. Parser parser() Access the parser API. Connection parsingConnection() A JDBC connection that runs each statement through the DSLContext.parser() first, prior to re-generating and running the SQL. io.r2dbc.spi.ConnectionFactory parsingConnectionFactory() An R2DBC ConnectionFactory that runs each statement through the DSLContext.parser() first, prior to re-generating and running the SQL. DataSource parsingDataSource() A JDBC data source that runs each statement through the DSLContext.parser() first, prior to re-generating and running the SQL. Queries queries(Collection<? extends Query> queries) Wrap a collection of queries. Queries queries(Query... queries) Wrap a collection of queries. RowCountQuery query(String sql) Create a new query holding plain SQL. RowCountQuery query(String sql, Object... bindings) Create a new query holding plain SQL. RowCountQuery query(String sql, QueryPart... parts) Create a new query holding plain SQL. RowCountQuery query(SQL sql) Create a new query holding plain SQL. String render(QueryPart part) Render a QueryPart in the context of this DSLContext. RenderContext renderContext() Get a new RenderContext for the context of this DSLContext. String renderInlined(QueryPart part) Render a QueryPart in the context of this DSLContext, inlining all bind variables. 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. String renderNamedParams(QueryPart part) Render a QueryPart in the context of this DSLContext, rendering bind variables as named parameters. ResultQuery<Record> resultQuery(String sql) Create a new query holding plain SQL. ResultQuery<Record> resultQuery(String sql, Object... bindings) Create a new query holding plain SQL. ResultQuery<Record> resultQuery(String sql, QueryPart... parts) Create a new query holding plain SQL. ResultQuery<Record> resultQuery(SQL sql) Create a new query holding plain SQL. RevokeOnStep revoke(Collection<? extends Privilege> privileges) The REVOKE statement. RevokeOnStep revoke(Privilege privileges) The REVOKE statement. RevokeOnStep revoke(Privilege... privileges) The REVOKE statement. RevokeOnStep revokeGrantOptionFor(Collection<? extends Privilege> privileges) The REVOKE GRANT OPTION FOR statement. RevokeOnStep revokeGrantOptionFor(Privilege privileges) The REVOKE GRANT OPTION FOR statement. RevokeOnStep revokeGrantOptionFor(Privilege... privileges) The REVOKE GRANT OPTION FOR statement. SelectSelectStep<Record> select(Collection<? extends SelectFieldOrAsterisk> 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<Record> select(SelectFieldOrAsterisk... fields) Create a new DSL select statement. SelectSelectStep<Record1<Integer>> selectCount() Create a new DSL select statement for COUNT(*). SelectSelectStep<Record> selectDistinct(Collection<? extends SelectFieldOrAsterisk> 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. SelectSelectStep<Record> selectDistinct(SelectFieldOrAsterisk... fields) Create a new DSL select statement. SelectWhereStep<Record> selectFrom(String sql) Create a new DSL select statement, projecting *. SelectWhereStep<Record> selectFrom(String sql, Object... bindings) Create a new DSL select statement, projecting *. SelectWhereStep<Record> selectFrom(String sql, QueryPart... parts) Create a new DSL select statement, projecting *. SelectWhereStep<Record> selectFrom(Name table) Create a new DSL select statement, projecting *. SelectWhereStep<Record> selectFrom(SQL sql) Create a new DSL select statement, projecting *. <R extends Record> SelectWhereStep<R> selectFrom(Table<R> table) Create a new DSL select statement, projecting the known columns from a table. SelectSelectStep<Record1<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<Integer>> selectZero() Create a new DSL select statement for a constant 0 literal. RowCountQuery set(Name name, Param<?> value) The SET statement. RowCountQuery setCatalog(String catalog) The SET CATALOG statement. RowCountQuery setCatalog(Catalog catalog) The SET CATALOG statement. RowCountQuery setCatalog(Name catalog) The SET CATALOG statement. RowCountQuery setLocal(Name name, Param<?> value) The SET LOCAL statement. RowCountQuery setSchema(String schema) The SET SCHEMA statement. RowCountQuery setSchema(Name schema) The SET SCHEMA statement. RowCountQuery setSchema(Schema schema) The SET SCHEMA statement. Settings settings() The settings wrapped by this context. Block statements(Collection<? extends Statement> statements) Wrap a collection of statements in an anonymous procedural block that does not wrap in BEGIN .. Block statements(Statement... statements) Wrap a collection of statements in an anonymous procedural block that does not wrap in BEGIN .. String toString() 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(). CompletionStage<Void> transactionAsync(Executor executor, TransactionalRunnable transactional) Run a TransactionalRunnable asynchronously. CompletionStage<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> CompletionStage<T> transactionResultAsync(Executor executor, TransactionalCallable<T> transactional) Run a TransactionalCallable asynchronously. <T> CompletionStage<T> transactionResultAsync(TransactionalCallable<T> transactional) Run a TransactionalCallable asynchronously. TruncateIdentityStep<Record> truncate(String table) The TRUNCATE statement. TruncateIdentityStep<Record> truncate(Name table) The TRUNCATE statement. <R extends Record> TruncateIdentityStep<R> truncate(Table<R> table) The TRUNCATE statement. TruncateIdentityStep<Record> truncateTable(String table) The TRUNCATE TABLE statement. TruncateIdentityStep<Record> truncateTable(Name table) The TRUNCATE TABLE statement. <R extends Record> TruncateIdentityStep<R> truncateTable(Table<R> table) The TRUNCATE TABLE 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 Version version(String id) Initialise a Version. Versions versions() Initialise a Versions graph. WithAsStep with(String alias) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep1 with(String alias, String fieldAlias1) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep with(String alias, String... fieldAliases) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep2 with(String alias, String fieldAlias1, String fieldAlias2) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep3 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep4 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep5 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep6 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep7 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep8 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep9 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep10 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep11 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep12 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11, String fieldAlias12) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep13 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11, String fieldAlias12, String fieldAlias13) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep14 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11, String fieldAlias12, String fieldAlias13, String fieldAlias14) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep15 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11, String fieldAlias12, String fieldAlias13, String fieldAlias14, String fieldAlias15) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep16 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11, String fieldAlias12, String fieldAlias13, String fieldAlias14, String fieldAlias15, String fieldAlias16) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep17 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11, String fieldAlias12, String fieldAlias13, String fieldAlias14, String fieldAlias15, String fieldAlias16, String fieldAlias17) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep18 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11, String fieldAlias12, String fieldAlias13, String fieldAlias14, String fieldAlias15, String fieldAlias16, String fieldAlias17, String fieldAlias18) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep19 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11, String fieldAlias12, String fieldAlias13, String fieldAlias14, String fieldAlias15, String fieldAlias16, String fieldAlias17, String fieldAlias18, String fieldAlias19) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep20 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11, String fieldAlias12, String fieldAlias13, String fieldAlias14, String fieldAlias15, String fieldAlias16, String fieldAlias17, String fieldAlias18, String fieldAlias19, String fieldAlias20) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep21 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11, String fieldAlias12, String fieldAlias13, String fieldAlias14, String fieldAlias15, String fieldAlias16, String fieldAlias17, String fieldAlias18, String fieldAlias19, String fieldAlias20, String fieldAlias21) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep22 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11, String fieldAlias12, String fieldAlias13, String fieldAlias14, String fieldAlias15, String fieldAlias16, String fieldAlias17, String fieldAlias18, String fieldAlias19, String fieldAlias20, String fieldAlias21, String fieldAlias22) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep with(String alias, Collection<String> fieldAliases) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep with(String alias, BiFunction<? super Field<?>,? super Integer,? extends String> fieldNameFunction) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep with(String alias, Function<? super Field<?>,? extends String> fieldNameFunction) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithStep with(Collection<? extends CommonTableExpression<?>> tables) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithStep with(CommonTableExpression<?>... tables) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep with(Name alias) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep with(Name alias, Collection<? extends Name> fieldAliases) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep1 with(Name alias, Name fieldAlias1) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep with(Name alias, Name... fieldAliases) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep2 with(Name alias, Name fieldAlias1, Name fieldAlias2) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. WithAsStep withRecursive(String alias) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep1 withRecursive(String alias, String fieldAlias1) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep withRecursive(String alias, String... fieldAliases) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep2 withRecursive(String alias, String fieldAlias1, String fieldAlias2) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep3 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep4 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep5 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep6 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep7 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep8 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep9 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep10 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep11 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep12 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11, String fieldAlias12) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep13 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11, String fieldAlias12, String fieldAlias13) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep14 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11, String fieldAlias12, String fieldAlias13, String fieldAlias14) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep15 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11, String fieldAlias12, String fieldAlias13, String fieldAlias14, String fieldAlias15) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep16 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11, String fieldAlias12, String fieldAlias13, String fieldAlias14, String fieldAlias15, String fieldAlias16) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep17 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11, String fieldAlias12, String fieldAlias13, String fieldAlias14, String fieldAlias15, String fieldAlias16, String fieldAlias17) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep18 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11, String fieldAlias12, String fieldAlias13, String fieldAlias14, String fieldAlias15, String fieldAlias16, String fieldAlias17, String fieldAlias18) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep19 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11, String fieldAlias12, String fieldAlias13, String fieldAlias14, String fieldAlias15, String fieldAlias16, String fieldAlias17, String fieldAlias18, String fieldAlias19) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep20 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11, String fieldAlias12, String fieldAlias13, String fieldAlias14, String fieldAlias15, String fieldAlias16, String fieldAlias17, String fieldAlias18, String fieldAlias19, String fieldAlias20) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep21 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11, String fieldAlias12, String fieldAlias13, String fieldAlias14, String fieldAlias15, String fieldAlias16, String fieldAlias17, String fieldAlias18, String fieldAlias19, String fieldAlias20, String fieldAlias21) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep22 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10, String fieldAlias11, String fieldAlias12, String fieldAlias13, String fieldAlias14, String fieldAlias15, String fieldAlias16, String fieldAlias17, String fieldAlias18, String fieldAlias19, String fieldAlias20, String fieldAlias21, String fieldAlias22) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep withRecursive(String alias, Collection<String> fieldAliases) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep withRecursive(String alias, BiFunction<? super Field<?>,? super Integer,? extends String> fieldNameFunction) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep withRecursive(String alias, Function<? super Field<?>,? extends String> fieldNameFunction) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithStep withRecursive(Collection<? extends CommonTableExpression<?>> tables) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithStep withRecursive(CommonTableExpression<?>... tables) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep withRecursive(Name alias) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep withRecursive(Name alias, Collection<? extends Name> fieldAliases) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep1 withRecursive(Name alias, Name fieldAlias1) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep withRecursive(Name alias, Name... fieldAliases) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. WithAsStep2 withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2) Create a WITH clause to supply subsequent SELECT, UPDATE, INSERT, DELETE, and MERGE statements with CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions. 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 CommonTableExpressions.
Methods inherited from class java.lang.Object clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait Methods inherited from interface org.jooq.Scope configuration, data, data, data, dialect, dsl, family, settings







Constructor Details



DefaultDSLContext
public DefaultDSLContext(SQLDialect dialect)




DefaultDSLContext
public DefaultDSLContext(SQLDialect dialect,
 Settings settings)




DefaultDSLContext
public DefaultDSLContext(Connection connection,
 SQLDialect dialect)




DefaultDSLContext
public DefaultDSLContext(Connection connection,
 SQLDialect dialect,
 Settings settings)




DefaultDSLContext
public DefaultDSLContext(DataSource datasource,
 SQLDialect dialect)




DefaultDSLContext
public DefaultDSLContext(DataSource datasource,
 SQLDialect dialect,
 Settings settings)




DefaultDSLContext
public DefaultDSLContext(ConnectionProvider connectionProvider,
 SQLDialect dialect)




DefaultDSLContext
public DefaultDSLContext(ConnectionProvider connectionProvider,
 SQLDialect dialect,
 Settings settings)




DefaultDSLContext
public DefaultDSLContext(io.r2dbc.spi.ConnectionFactory connectionFactory,
 SQLDialect dialect)




DefaultDSLContext
public DefaultDSLContext(io.r2dbc.spi.ConnectionFactory connectionFactory,
 SQLDialect dialect,
 Settings settings)




DefaultDSLContext
public DefaultDSLContext(Configuration configuration)








Method Details



map
public Schema map(Schema schema)
Description copied from interface: DSLContext
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.

Specified by:
map in interface DSLContext
Parameters:
schema - A schema
Returns:
The mapped schema





map
public <R extends Record> Table<R> map(Table<R> table)
Description copied from interface: DSLContext
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.

Specified by:
map in interface DSLContext
Parameters:
table - A table
Returns:
The mapped table





parser
public Parser parser()
Description copied from interface: DSLContext
Access the parser API.

Specified by:
parser in interface DSLContext





parsingConnection
public Connection parsingConnection()
Description copied from interface: DSLContext
A JDBC connection that runs each statement through the DSLContext.parser()
 first, prior to re-generating and running the SQL.
 
 Static statements are translated eagerly upon execution, e.g. of
 Statement.executeQuery(String). Prepared statements are
 prepared lazily once all bind variables are available, because the
 specific bind value and type may influence the generated SQL. As such, a
 PreparedStatement created from a parsing connection does not yet
 allocate any server side resources until it is executed for the first
 time.
 

 The Configuration.cacheProvider() is called for
 CacheType#CACHE_PARSING_CONNECTION to provide a translation cache
 to avoid the overhead of re-parsing and re-generating the same SQL string
 all the time. By default, this is an LRU cache.
 

 The resulting Connection wraps an underlying JDBC connection that
 has been obtained from ConnectionProvider.acquire() and must be
 released by calling Connection.close(), which calls
 ConnectionProvider.release(Connection).

Specified by:
parsingConnection in interface DSLContext





parsingDataSource
public DataSource parsingDataSource()
Description copied from interface: DSLContext
A JDBC data source that runs each statement through the DSLContext.parser()
 first, prior to re-generating and running the SQL.
 
 This simply wraps the DSLContext.parsingConnection() in a
 DataSource.

Specified by:
parsingDataSource in interface DSLContext





parsingConnectionFactory
public io.r2dbc.spi.ConnectionFactory parsingConnectionFactory()
Description copied from interface: DSLContext
An R2DBC ConnectionFactory that runs each statement through the
 DSLContext.parser() first, prior to re-generating and running the SQL.

Specified by:
parsingConnectionFactory in interface DSLContext





diagnosticsConnection
public Connection diagnosticsConnection()
Description copied from interface: DSLContext
A JDBC connection that proxies the underlying connection to run the jOOQ
 Diagnostics Pack on executed queries.
 
 This is experimental functionality.

Specified by:
diagnosticsConnection in interface DSLContext





diagnosticsDataSource
public DataSource diagnosticsDataSource()
Description copied from interface: DSLContext
A JDBC connection that proxies the underlying connection to run the jOOQ
 Diagnostics Pack on executed queries.
 
 This simply wraps the DSLContext.diagnosticsConnection() in a DataSource.

Specified by:
diagnosticsDataSource in interface DSLContext





version
public Version version(String id)
Description copied from interface: DSLContext
Initialise a Version.
 
 This is EXPERIMENTAL functionality and subject to change in future jOOQ
 versions.

Specified by:
version in interface DSLContext





versions
public Versions versions()
Description copied from interface: DSLContext
Initialise a Versions graph.
 
 This is EXPERIMENTAL functionality and subject to change in future jOOQ
 versions.

Specified by:
versions in interface DSLContext





commit
public Commit commit(String id)
Description copied from interface: DSLContext
Initialise a Version.
 
 This is EXPERIMENTAL functionality and subject to change in future jOOQ
 versions.

Specified by:
commit in interface DSLContext





commits
public Commits commits()
Description copied from interface: DSLContext
Initialise a Commits graph.
 
 This is EXPERIMENTAL functionality and subject to change in future jOOQ
 versions.

Specified by:
commits in interface DSLContext





migrateTo
public Migration migrateTo(Commit to)
Description copied from interface: DSLContext
Create a migration from the currently installed version to a new version.
 
 This is EXPERIMENTAL functionality and subject to change in future jOOQ
 versions.

Specified by:
migrateTo in interface DSLContext





meta
public Meta meta()
Description copied from interface: DSLContext
Access the database meta data.
 
 This method returns meta information provided by
 Configuration.metaProvider(), which defaults to a wrapper type
 that gives access to your JDBC connection's DatabaseMetaData as
 obtained from your ConnectionProvider.

Specified by:
meta in interface DSLContext
See Also:
DSLContext.meta(DatabaseMetaData)





meta
public Meta meta(DatabaseMetaData meta)
Description copied from interface: DSLContext
Access the database meta data from an explicit JDBC
 DatabaseMetaData.

Specified by:
meta in interface DSLContext





meta
public Meta meta(Catalog... catalogs)
Description copied from interface: DSLContext
Access the database meta data from explicit catalog information.
 
 This will not connect to your database to get live meta information,
 unlike DSLContext.meta() and DSLContext.meta(DatabaseMetaData).

Specified by:
meta in interface DSLContext





meta
public Meta meta(Schema... schemas)
Description copied from interface: DSLContext
Access the database meta data from explicit schema information.
 
 This will not connect to your database to get live meta information,
 unlike DSLContext.meta() and DSLContext.meta(DatabaseMetaData).

Specified by:
meta in interface DSLContext





meta
public Meta meta(Table<?>... tables)
Description copied from interface: DSLContext
Access the database meta data from explicit table information.
 
 This will not connect to your database to get live meta information,
 unlike DSLContext.meta() and DSLContext.meta(DatabaseMetaData).

Specified by:
meta in interface DSLContext





meta
public Meta meta(InformationSchema schema)
Description copied from interface: DSLContext
Access the database meta data from an explicit JAXB-annotated meta model.
 
 This will not connect to your database to get live meta information,
 unlike DSLContext.meta() and DSLContext.meta(DatabaseMetaData).

Specified by:
meta in interface DSLContext





meta
public Meta meta(String... sources)
Description copied from interface: DSLContext
Create meta data from a set of sources.
 
 This is convenience for wrapping all argument Strings in
 Source. The same set of content types are supported as in
 DSLContext.meta(Source...).

Specified by:
meta in interface DSLContext





meta
public Meta meta(Source... sources)
Description copied from interface: DSLContext
Create meta data from a set of sources.
 
 This method creates a Meta representation from a set of source
 content, which can be any of:
 

 A set of DDL scripts, which will be parsed using
 DSLContext.parser().
 A set of XML files, which will be unmarshalled into
 InformationSchema objects.
 
 
 This will not connect to your database to get live meta information,
 unlike DSLContext.meta() and DSLContext.meta(DatabaseMetaData).

Specified by:
meta in interface DSLContext





meta
public Meta meta(Query... queries)
Description copied from interface: DSLContext
Create meta data from a set of DDL queries.
 
 This works the same way as DSLContext.meta(Source...), without the need of
 parsing the DDL scripts.

Specified by:
meta in interface DSLContext





informationSchema
public InformationSchema informationSchema(Catalog catalog)
Description copied from interface: DSLContext
Convenience method for Meta.informationSchema().

Specified by:
informationSchema in interface DSLContext
See Also:
DSLContext.meta(Catalog...), 
Meta.informationSchema()





informationSchema
public InformationSchema informationSchema(Catalog... catalogs)
Description copied from interface: DSLContext
Convenience method for Meta.informationSchema().

Specified by:
informationSchema in interface DSLContext
See Also:
DSLContext.meta(Catalog...), 
Meta.informationSchema()





informationSchema
public InformationSchema informationSchema(Schema schema)
Description copied from interface: DSLContext
Convenience method for Meta.informationSchema().

Specified by:
informationSchema in interface DSLContext
See Also:
DSLContext.meta(Schema...), 
Meta.informationSchema()





informationSchema
public InformationSchema informationSchema(Schema... schemas)
Description copied from interface: DSLContext
Convenience method for Meta.informationSchema().

Specified by:
informationSchema in interface DSLContext
See Also:
DSLContext.meta(Schema...), 
Meta.informationSchema()





informationSchema
public InformationSchema informationSchema(Table<?> table)
Description copied from interface: DSLContext
Convenience method for Meta.informationSchema().

Specified by:
informationSchema in interface DSLContext
See Also:
DSLContext.meta(Table...), 
Meta.informationSchema()





informationSchema
public InformationSchema informationSchema(Table<?>... tables)
Description copied from interface: DSLContext
Convenience method for Meta.informationSchema().

Specified by:
informationSchema in interface DSLContext
See Also:
DSLContext.meta(Table...), 
Meta.informationSchema()





explain
public Explain explain(Query query)
Description copied from interface: DSLContext
Run an EXPLAIN statement in the database to estimate the
 cardinality of the query.

Specified by:
explain in interface DSLContext





transactionResult
public <T> T transactionResult(ContextTransactionalCallable<T> transactional)
Description copied from interface: DSLContext
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.

Specified by:
transactionResult in interface DSLContext
Parameters:
transactional - The transactional code
Returns:
The transactional outcome





transactionResult
public <T> T transactionResult(TransactionalCallable<T> transactional)
Description copied from interface: DSLContext
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.

Specified by:
transactionResult in interface DSLContext
Parameters:
transactional - The transactional code
Returns:
The transactional outcome





transaction
public void transaction(ContextTransactionalRunnable transactional)
Description copied from interface: DSLContext
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.

Specified by:
transaction in interface DSLContext
Parameters:
transactional - The transactional code





transaction
public void transaction(TransactionalRunnable transactional)
Description copied from interface: DSLContext
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.

Specified by:
transaction in interface DSLContext
Parameters:
transactional - The transactional code





transactionAsync
public CompletionStage<Void> transactionAsync(TransactionalRunnable transactional)
Description copied from interface: DSLContext
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().

Specified by:
transactionAsync in interface DSLContext
Parameters:
transactional - The transactional code





transactionAsync
public CompletionStage<Void> transactionAsync(Executor executor,
 TransactionalRunnable transactional)
Description copied from interface: DSLContext
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.

Specified by:
transactionAsync in interface DSLContext
transactional - The transactional code





transactionResultAsync
public <T> CompletionStage<T> transactionResultAsync(TransactionalCallable<T> transactional)
Description copied from interface: DSLContext
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().

Specified by:
transactionResultAsync in interface DSLContext
Parameters:
transactional - The transactional code
Returns:
The transactional outcome





transactionResultAsync
public <T> CompletionStage<T> transactionResultAsync(Executor executor,
 TransactionalCallable<T> transactional)
Description copied from interface: DSLContext
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.

Specified by:
transactionResultAsync in interface DSLContext
transactional - The transactional code
Returns:
The transactional outcome





connectionResult
public <T> T connectionResult(ConnectionCallable<T> callable)
Description copied from interface: DSLContext
Run a ConnectionCallable in the context of this
 DSLContext's underlying Scope.configuration()'s
 Configuration.connectionProvider().

Specified by:
connectionResult in interface DSLContext
Parameters:
callable - The code running statements against the
            connection.
Returns:
The outcome of the callable





connection
public void connection(ConnectionRunnable runnable)
Description copied from interface: DSLContext
Run a ConnectionRunnable in the context of this
 DSLContext's underlying Scope.configuration()'s
 Configuration.connectionProvider().

Specified by:
connection in interface DSLContext
Parameters:
runnable - The code running statements against the
            connection.





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

Specified by:
mockResult in interface DSLContext





mock
public void mock(MockDataProvider provider,
 MockRunnable mockable)
Description copied from interface: DSLContext
Run a MockRunnable in the context of this DSLContext
 's underlying Scope.configuration()'s, and of a
 MockDataProvider.

Specified by:
mock in interface DSLContext





renderContext
public RenderContext renderContext()
Description copied from interface: DSLContext
Get a new RenderContext for the context of this DSLContext.
 
 This will return an initialised render context as such:
 

 
 Context.castMode() == DEFAULT
 
  Context.declareFields() == false
  Context.declareTables() == false
  Context.format() == false
  Context.paramType() == ParamType.INDEXED
  Context.qualify() == true
  Context.subquery() == false
 

Specified by:
renderContext in interface DSLContext





render
public String render(QueryPart part)
Description copied from interface: DSLContext
Render a QueryPart in the context of this DSLContext.
 
 This is the same as calling renderContext().render(part)

Specified by:
render in interface DSLContext
Parameters:
part - The QueryPart to be rendered
Returns:
The rendered SQL





renderNamedParams
public String renderNamedParams(QueryPart part)
Description copied from interface: DSLContext
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)

Specified by:
renderNamedParams in interface DSLContext
Parameters:
part - The QueryPart to be rendered
Returns:
The rendered SQL





renderNamedOrInlinedParams
public String renderNamedOrInlinedParams(QueryPart part)
Description copied from interface: DSLContext
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)

Specified by:
renderNamedOrInlinedParams in interface DSLContext
Parameters:
part - The QueryPart to be rendered
Returns:
The rendered SQL





renderInlined
public String renderInlined(QueryPart part)
Description copied from interface: DSLContext
Render a QueryPart in the context of this DSLContext, inlining all bind
 variables.
 
 This is the same as calling
 renderContext().inline(true).render(part)

Specified by:
renderInlined in interface DSLContext
Parameters:
part - The QueryPart to be rendered
Returns:
The rendered SQL





extractBindValues
public List<Object> extractBindValues(QueryPart part)
Description copied from interface: DSLContext
Retrieve the bind values that will be bound by a given
 QueryPart.
 
 The returned List is immutable. To modify bind values, use
 DSLContext.extractParams(QueryPart) instead.
 

 Unlike DSLContext.extractParams(QueryPart), which returns also inlined
 parameters, this returns only actual bind values that will render an
 actual bind value as a question mark "?"

Specified by:
extractBindValues in interface DSLContext





extractParams
public Map<String,Param<?>> extractParams(QueryPart part)
Description copied from interface: DSLContext
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.

Specified by:
extractParams in interface DSLContext
See Also:
Param, 
DSL.param(String, Object)





extractParam
public Param<?> extractParam(QueryPart part,
 String name)
Description copied from interface: DSLContext
Get a named parameter from a QueryPart, provided its name.
 
 Bind values created with DSL.val(Object) will have their bind
 index as name.

Specified by:
extractParam in interface DSLContext
See Also:
Param, 
DSL.param(String, Object)





bindContext
public BindContext bindContext(PreparedStatement stmt)
Description copied from interface: DSLContext
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

Specified by:
bindContext in interface DSLContext





attach
public void attach(Attachable... attachables)
Description copied from interface: DSLContext
Attach this DSLContext's underlying Scope.configuration()
 to some attachables.

Specified by:
attach in interface DSLContext





attach
public void attach(Collection<? extends Attachable> attachables)
Description copied from interface: DSLContext
Attach this DSLContext's underlying Scope.configuration()
 to some attachables.

Specified by:
attach in interface DSLContext





loadInto
public <R extends Record> LoaderOptionsStep<R> loadInto(Table<R> table)
Description copied from interface: DSLContext
Create a new Loader object to load data from a CSV or XML
 source.

Specified by:
loadInto in interface DSLContext





queries
public Queries queries(Query... queries)
Description copied from interface: DSLContext
Wrap a collection of queries.

Specified by:
queries in interface DSLContext
See Also:
DSL.queries(Query...)





queries
public Queries queries(Collection<? extends Query> queries)
Description copied from interface: DSLContext
Wrap a collection of queries.

Specified by:
queries in interface DSLContext
See Also:
DSL.queries(Collection)





begin
public Block begin(Statement... statements)
Description copied from interface: DSLContext
Wrap a collection of statements in an anonymous procedural block.

Specified by:
begin in interface DSLContext
See Also:
DSL.begin(Statement...)





begin
public Block begin(Collection<? extends Statement> statements)
Description copied from interface: DSLContext
Wrap a collection of statements in an anoymous procedural block.

Specified by:
begin in interface DSLContext
See Also:
DSL.begin(Collection)





statements
@Pro
public Block statements(Statement... statements)
Description copied from interface: DSLContext
Wrap a collection of statements in an anonymous procedural block that
 does not wrap in BEGIN .. END;, unless explicitly needed.

Specified by:
statements in interface DSLContext
See Also:
DSL.statements(Statement...)





statements
@Pro
public Block statements(Collection<? extends Statement> statements)
Description copied from interface: DSLContext
Wrap a collection of statements in an anonymous procedural block that
 does not wrap in BEGIN .. END;, unless explicitly needed.

Specified by:
statements in interface DSLContext
See Also:
DSL.statements(Collection)





query
public RowCountQuery query(SQL sql)
Description copied from interface: DSLContext
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!

Specified by:
query in interface DSLContext
Parameters:
sql - The SQL
Returns:
A query wrapping the plain SQL
See Also:
SQL





query
public RowCountQuery query(String sql)
Description copied from interface: DSLContext
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!

Specified by:
query in interface DSLContext
Parameters:
sql - The SQL
Returns:
A query wrapping the plain SQL
See Also:
SQL





query
public RowCountQuery query(String sql,
 Object... bindings)
Description copied from interface: DSLContext
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!

Specified by:
query in interface DSLContext
Parameters:
sql - The SQL
bindings - The bindings
Returns:
A query wrapping the plain SQL
See Also:
SQL, 
DSL.sql(String, Object...)





query
public RowCountQuery query(String sql,
 QueryPart... parts)
Description copied from interface: DSLContext
Create a new query holding plain SQL.
 
 Unlike DSLContext.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 by default, using SQLDialect.ORACLE:
 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

Specified by:
query in interface DSLContext
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
public Result<Record> fetch(SQL sql)
Description copied from interface: DSLContext
Execute a new query holding plain SQL.
 
 Example (Postgres):
 

 
 String sql = "FETCH ALL IN \"<unnamed cursor 1>\""; 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!

Specified by:
fetch in interface DSLContext
Parameters:
sql - The SQL
Returns:
The results from the executed query. This will never be
         null.
See Also:
SQL





fetch
public Result<Record> fetch(String sql)
Description copied from interface: DSLContext
Execute a new query holding plain SQL.
 
 Example (Postgres):
 

 
 String sql = "FETCH ALL IN \"<unnamed cursor 1>\""; 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!

Specified by:
fetch in interface DSLContext
Parameters:
sql - The SQL
Returns:
The results from the executed query. This will never be
         null.
See Also:
SQL





fetch
public Result<Record> fetch(String sql,
 Object... bindings)
Description copied from interface: DSLContext
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 \"<unnamed cursor 1>\""; 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!

Specified by:
fetch in interface DSLContext
Parameters:
sql - The SQL
bindings - The bindings
Returns:
The results from the executed query. This will never be null.
See Also:
SQL, 
DSL.sql(String, Object...)





fetch
public Result<Record> fetch(String sql,
 QueryPart... parts)
Description copied from interface: DSLContext
Execute a new query holding plain SQL.
 
 Unlike DSLContext.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 by default, using SQLDialect.ORACLE:
 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

Specified by:
fetch in interface DSLContext
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.
See Also:
SQL, 
DSL.sql(String, QueryPart...)





fetchLazy
public Cursor<Record> fetchLazy(SQL sql)
Description copied from interface: DSLContext
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 \"<unnamed cursor 1>\""; 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!
 

 Depending on your JDBC driver's default behaviour, this may load the
 whole database result into the driver's memory. In order to indicate to
 the driver that you may not want to fetch all records at once, use
 ResultQuery.fetchSize(int) and run
 ResultQuery.fetchLazy() instead, or specify
 Settings.setFetchSize(Integer) prior to calling this method.
 

 Client code is responsible for closing the cursor after use.

Specified by:
fetchLazy in interface DSLContext
Parameters:
sql - The SQL
Returns:
The cursor. This will never be null.
See Also:
SQL





fetchLazy
public Cursor<Record> fetchLazy(String sql)
Description copied from interface: DSLContext
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 \"<unnamed cursor 1>\""; 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!
 

 Depending on your JDBC driver's default behaviour, this may load the
 whole database result into the driver's memory. In order to indicate to
 the driver that you may not want to fetch all records at once, use
 ResultQuery.fetchSize(int) and run
 ResultQuery.fetchLazy() instead, or specify
 Settings.setFetchSize(Integer) prior to calling this method.
 

 Client code is responsible for closing the cursor after use.

Specified by:
fetchLazy in interface DSLContext
Parameters:
sql - The SQL
Returns:
The cursor. This will never be null.
See Also:
SQL





fetchLazy
public Cursor<Record> fetchLazy(String sql,
 Object... bindings)
Description copied from interface: DSLContext
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 \"<unnamed cursor 1>\""; 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!
 

 Depending on your JDBC driver's default behaviour, this may load the
 whole database result into the driver's memory. In order to indicate to
 the driver that you may not want to fetch all records at once, use
 ResultQuery.fetchSize(int) and run
 ResultQuery.fetchLazy() instead, or specify
 Settings.setFetchSize(Integer) prior to calling this method.
 

 Client code is responsible for closing the cursor after use.

Specified by:
fetchLazy in interface DSLContext
Parameters:
sql - The SQL
bindings - The bindings
Returns:
The cursor. This will never be null.
See Also:
SQL, 
DSL.sql(String, Object...)





fetchLazy
public Cursor<Record> fetchLazy(String sql,
 QueryPart... parts)
Description copied from interface: DSLContext
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 DSLContext.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 by default, using SQLDialect.ORACLE:
 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
 

 Depending on your JDBC driver's default behaviour, this may load the
 whole database result into the driver's memory. In order to indicate to
 the driver that you may not want to fetch all records at once, use
 ResultQuery.fetchSize(int) and run
 ResultQuery.fetchLazy() instead, or specify
 Settings.setFetchSize(Integer) prior to calling this method.
 

 Client code is responsible for closing the cursor after use.

Specified by:
fetchLazy in interface DSLContext
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.
See Also:
SQL, 
DSL.sql(String, QueryPart...)





fetchAsync
public CompletionStage<Result<Record>> fetchAsync(SQL sql)
Description copied from interface: DSLContext
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 \"<unnamed cursor 1>\""; 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!

Specified by:
fetchAsync in interface DSLContext
Parameters:
sql - The SQL
Returns:
The completion stage. The completed result will never be
         null.
See Also:
SQL





fetchAsync
public CompletionStage<Result<Record>> fetchAsync(String sql)
Description copied from interface: DSLContext
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 \"<unnamed cursor 1>\""; 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!

Specified by:
fetchAsync in interface DSLContext
Parameters:
sql - The SQL
Returns:
The completion stage. The completed result will never be
         null.
See Also:
SQL





fetchAsync
public CompletionStage<Result<Record>> fetchAsync(String sql,
 Object... bindings)
Description copied from interface: DSLContext
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 \"<unnamed cursor 1>\""; 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!

Specified by:
fetchAsync in interface DSLContext
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
public CompletionStage<Result<Record>> fetchAsync(String sql,
 QueryPart... parts)
Description copied from interface: DSLContext
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 DSLContext.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 by default, using SQLDialect.ORACLE:
 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

Specified by:
fetchAsync in interface DSLContext
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
public CompletionStage<Result<Record>> fetchAsync(Executor executor,
 SQL sql)
Description copied from interface: DSLContext
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 \"<unnamed cursor 1>\""; 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!

Specified by:
fetchAsync in interface DSLContext
sql - The SQL
Returns:
The completion stage. The completed result will never be
         null.
See Also:
SQL





fetchAsync
public CompletionStage<Result<Record>> fetchAsync(Executor executor,
 String sql)
Description copied from interface: DSLContext
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 \"<unnamed cursor 1>\""; 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!

Specified by:
fetchAsync in interface DSLContext
sql - The SQL
Returns:
The completion stage. The completed result will never be
         null.
See Also:
SQL





fetchAsync
public CompletionStage<Result<Record>> fetchAsync(Executor executor,
 String sql,
 Object... bindings)
Description copied from interface: DSLContext
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 \"<unnamed cursor 1>\""; 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!

Specified by:
fetchAsync in interface DSLContext
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
public CompletionStage<Result<Record>> fetchAsync(Executor executor,
 String sql,
 QueryPart... parts)
Description copied from interface: DSLContext
Fetch results in a new CompletionStage that is asynchronously
 completed by a task running in the given executor.
 
 Unlike DSLContext.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 by default, using SQLDialect.ORACLE:
 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

Specified by:
fetchAsync in interface DSLContext
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
public Stream<Record> fetchStream(SQL sql)
Description copied from interface: DSLContext
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 \"<unnamed cursor 1>\""; 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!
 

 Depending on your JDBC driver's default behaviour, this may load the
 whole database result into the driver's memory. In order to indicate to
 the driver that you may not want to fetch all records at once, use
 ResultQuery.fetchSize(int) and run
 ResultQuery.fetchStream() instead, or specify
 Settings.setFetchSize(Integer) prior to calling this method.
 

 Client code is responsible for closing the stream after use.

Specified by:
fetchStream in interface DSLContext
Parameters:
sql - The SQL
Returns:
The results from the executed query. This is never
         null, even if the database returns no
         ResultSet
See Also:
SQL





fetchStream
public Stream<Record> fetchStream(String sql)
Description copied from interface: DSLContext
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 \"<unnamed cursor 1>\""; 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!
 

 Depending on your JDBC driver's default behaviour, this may load the
 whole database result into the driver's memory. In order to indicate to
 the driver that you may not want to fetch all records at once, use
 ResultQuery.fetchSize(int) and run
 ResultQuery.fetchStream() instead, or specify
 Settings.setFetchSize(Integer) prior to calling this method.
 

 Client code is responsible for closing the stream after use.

Specified by:
fetchStream in interface DSLContext
Parameters:
sql - The SQL
Returns:
The results from the executed query. This is never
         null, even if the database returns no
         ResultSet
See Also:
SQL





fetchStream
public Stream<Record> fetchStream(String sql,
 Object... bindings)
Description copied from interface: DSLContext
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 \"<unnamed cursor 1>\""; 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!
 

 Depending on your JDBC driver's default behaviour, this may load the
 whole database result into the driver's memory. In order to indicate to
 the driver that you may not want to fetch all records at once, use
 ResultQuery.fetchSize(int) and run
 ResultQuery.fetchStream() instead, or specify
 Settings.setFetchSize(Integer) prior to calling this method.
 

 Client code is responsible for closing the stream after use.

Specified by:
fetchStream in interface DSLContext
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
See Also:
SQL, 
DSL.sql(String, Object...)





fetchStream
public Stream<Record> fetchStream(String sql,
 QueryPart... parts)
Description copied from interface: DSLContext
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 DSLContext.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 by default, using SQLDialect.ORACLE:
 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
 

 Depending on your JDBC driver's default behaviour, this may load the
 whole database result into the driver's memory. In order to indicate to
 the driver that you may not want to fetch all records at once, use
 ResultQuery.fetchSize(int) and run
 ResultQuery.fetchStream() instead, or specify
 Settings.setFetchSize(Integer) prior to calling this method.
 

 Client code is responsible for closing the stream after use.

Specified by:
fetchStream in interface DSLContext
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
See Also:
SQL, 
DSL.sql(String, QueryPart...)





fetchMany
public Results fetchMany(SQL sql)
Description copied from interface: DSLContext
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!

Specified by:
fetchMany in interface DSLContext
Parameters:
sql - The SQL
Returns:
The results. This will never be null.
See Also:
SQL





fetchMany
public Results fetchMany(String sql)
Description copied from interface: DSLContext
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!

Specified by:
fetchMany in interface DSLContext
Parameters:
sql - The SQL
Returns:
The results. This will never be null.
See Also:
SQL





fetchMany
public Results fetchMany(String sql,
 Object... bindings)
Description copied from interface: DSLContext
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!

Specified by:
fetchMany in interface DSLContext
Parameters:
sql - The SQL
bindings - The bindings
Returns:
The results. This will never be null.
See Also:
SQL, 
DSL.sql(String, Object...)





fetchMany
public Results fetchMany(String sql,
 QueryPart... parts)
Description copied from interface: DSLContext
Execute a new query holding plain SQL, possibly returning several result
 sets.
 
 Unlike DSLContext.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 by default, using SQLDialect.ORACLE:
 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

Specified by:
fetchMany in interface DSLContext
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.
See Also:
SQL, 
DSL.sql(String, QueryPart...)





fetchOne
public Record fetchOne(SQL sql)
Description copied from interface: DSLContext
Execute a new query holding plain SQL.
 
 Example (Postgres):
 

 
 String sql = "FETCH ALL IN \"<unnamed cursor 1>\""; 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!

Specified by:
fetchOne in interface DSLContext
Parameters:
sql - The SQL
Returns:
The record or null, if no record was found.
See Also:
SQL





fetchOne
public Record fetchOne(String sql)
Description copied from interface: DSLContext
Execute a new query holding plain SQL.
 
 Example (Postgres):
 

 
 String sql = "FETCH ALL IN \"<unnamed cursor 1>\""; 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!

Specified by:
fetchOne in interface DSLContext
Parameters:
sql - The SQL
Returns:
The record or null, if no record was found.
See Also:
SQL





fetchOne
public Record fetchOne(String sql,
 Object... bindings)
Description copied from interface: DSLContext
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 \"<unnamed cursor 1>\""; 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!

Specified by:
fetchOne in interface DSLContext
Parameters:
sql - The SQL
bindings - The bindings
Returns:
The record or null, if no record was found.
See Also:
SQL, 
DSL.sql(String, Object...)





fetchOne
public Record fetchOne(String sql,
 QueryPart... parts)
Description copied from interface: DSLContext
Execute a new query holding plain SQL.
 
 Unlike DSLContext.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 by default, using SQLDialect.ORACLE:
 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

Specified by:
fetchOne in interface DSLContext
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.
See Also:
SQL, 
DSL.sql(String, QueryPart...)





fetchSingle
public Record fetchSingle(SQL sql)
Description copied from interface: DSLContext
Execute a new query holding plain SQL.
 
 Example (Postgres):
 

 
 String sql = "FETCH ALL IN \"<unnamed cursor 1>\""; 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!

Specified by:
fetchSingle in interface DSLContext
Parameters:
sql - The SQL
Returns:
The record. This is never null.
See Also:
SQL





fetchSingle
public Record fetchSingle(String sql)
Description copied from interface: DSLContext
Execute a new query holding plain SQL.
 
 Example (Postgres):
 

 
 String sql = "FETCH ALL IN \"<unnamed cursor 1>\""; 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!

Specified by:
fetchSingle in interface DSLContext
Parameters:
sql - The SQL
Returns:
The record. This is never null.
See Also:
SQL





fetchSingle
public Record fetchSingle(String sql,
 Object... bindings)
Description copied from interface: DSLContext
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 \"<unnamed cursor 1>\""; 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!

Specified by:
fetchSingle in interface DSLContext
Parameters:
sql - The SQL
bindings - The bindings
Returns:
The record. This is never null.
See Also:
SQL, 
DSL.sql(String, Object...)





fetchSingle
public Record fetchSingle(String sql,
 QueryPart... parts)
Description copied from interface: DSLContext
Execute a new query holding plain SQL.
 
 Unlike DSLContext.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 by default, using SQLDialect.ORACLE:
 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

Specified by:
fetchSingle in interface DSLContext
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.
See Also:
SQL, 
DSL.sql(String, QueryPart...)





fetchOptional
public Optional<Record> fetchOptional(SQL sql)
Description copied from interface: DSLContext
Execute a new query holding plain SQL.
 
 Example (Postgres):
 

 
 String sql = "FETCH ALL IN \"<unnamed cursor 1>\""; 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!

Specified by:
fetchOptional in interface DSLContext
Parameters:
sql - The SQL
Returns:
The results from the executed query
See Also:
SQL





fetchOptional
public Optional<Record> fetchOptional(String sql)
Description copied from interface: DSLContext
Execute a new query holding plain SQL.
 
 Example (Postgres):
 

 
 String sql = "FETCH ALL IN \"<unnamed cursor 1>\""; 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!

Specified by:
fetchOptional in interface DSLContext
Parameters:
sql - The SQL
Returns:
The results from the executed query
See Also:
SQL





fetchOptional
public Optional<Record> fetchOptional(String sql,
 Object... bindings)
Description copied from interface: DSLContext
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 \"<unnamed cursor 1>\""; 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!

Specified by:
fetchOptional in interface DSLContext
Parameters:
sql - The SQL
bindings - The bindings
Returns:
The results from the executed query
See Also:
SQL, 
DSL.sql(String, Object...)





fetchOptional
public Optional<Record> fetchOptional(String sql,
 QueryPart... parts)
Description copied from interface: DSLContext
Execute a new query holding plain SQL.
 
 Unlike DSLContext.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 by default, using SQLDialect.ORACLE:
 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

Specified by:
fetchOptional in interface DSLContext
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
See Also:
SQL, 
DSL.sql(String, QueryPart...)





fetchValue
public Object fetchValue(SQL sql)
Description copied from interface: DSLContext
Execute a new query holding plain SQL.
 
 Example (Postgres):
 

 
 String sql = "FETCH ALL IN \"<unnamed cursor 1>\""; 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!

Specified by:
fetchValue in interface DSLContext
Parameters:
sql - The SQL
Returns:
The value or null, if no record was found.
See Also:
SQL





fetchValue
public Object fetchValue(String sql)
Description copied from interface: DSLContext
Execute a new query holding plain SQL.
 
 Example (Postgres):
 

 
 String sql = "FETCH ALL IN \"<unnamed cursor 1>\""; 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!

Specified by:
fetchValue in interface DSLContext
Parameters:
sql - The SQL
Returns:
The value or null, if no record was found.
See Also:
SQL





fetchValue
public Object fetchValue(String sql,
 Object... bindings)
Description copied from interface: DSLContext
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 \"<unnamed cursor 1>\""; 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!

Specified by:
fetchValue in interface DSLContext
Parameters:
sql - The SQL
bindings - The bindings
Returns:
The value or null, if no record was found.
See Also:
SQL, 
DSL.sql(String, Object...)





fetchValue
public Object fetchValue(String sql,
 QueryPart... parts)
Description copied from interface: DSLContext
Execute a new query holding plain SQL.
 
 Unlike DSLContext.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 by default, using SQLDialect.ORACLE:
 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

Specified by:
fetchValue in interface DSLContext
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.
See Also:
SQL, 
DSL.sql(String, QueryPart...)





fetchOptionalValue
public Optional<?> fetchOptionalValue(SQL sql)
Description copied from interface: DSLContext
Execute a new query holding plain SQL.
 
 Example (Postgres):
 

 
 String sql = "FETCH ALL IN \"<unnamed cursor 1>\""; 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!

Specified by:
fetchOptionalValue in interface DSLContext
Parameters:
sql - The SQL
Returns:
The result value from the executed query
See Also:
SQL





fetchOptionalValue
public Optional<?> fetchOptionalValue(String sql)
Description copied from interface: DSLContext
Execute a new query holding plain SQL.
 
 Example (Postgres):
 

 
 String sql = "FETCH ALL IN \"<unnamed cursor 1>\""; 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!

Specified by:
fetchOptionalValue in interface DSLContext
Parameters:
sql - The SQL
Returns:
The result value from the executed query
See Also:
SQL





fetchOptionalValue
public Optional<?> fetchOptionalValue(String sql,
 Object... bindings)
Description copied from interface: DSLContext
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 \"<unnamed cursor 1>\""; 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!

Specified by:
fetchOptionalValue in interface DSLContext
Parameters:
sql - The SQL
bindings - The bindings
Returns:
The results from the executed query
See Also:
SQL, 
DSL.sql(String, Object...)





fetchOptionalValue
public Optional<?> fetchOptionalValue(String sql,
 QueryPart... parts)
Description copied from interface: DSLContext
Execute a new query holding plain SQL.
 
 Unlike DSLContext.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 by default, using SQLDialect.ORACLE:
 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

Specified by:
fetchOptionalValue in interface DSLContext
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
See Also:
SQL, 
DSL.sql(String, QueryPart...)





fetchValues
public List<?> fetchValues(SQL sql)
Description copied from interface: DSLContext
Execute a new query holding plain SQL.
 
 Example (Postgres):
 

 
 String sql = "FETCH ALL IN \"<unnamed cursor 1>\""; 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!

Specified by:
fetchValues in interface DSLContext
Parameters:
sql - The SQL
Returns:
The values. This will never be null.
See Also:
SQL





fetchValues
public List<?> fetchValues(String sql)
Description copied from interface: DSLContext
Execute a new query holding plain SQL.
 
 Example (Postgres):
 

 
 String sql = "FETCH ALL IN \"<unnamed cursor 1>\""; 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!

Specified by:
fetchValues in interface DSLContext
Parameters:
sql - The SQL
Returns:
The values. This will never be null.
See Also:
SQL





fetchValues
public List<?> fetchValues(String sql,
 Object... bindings)
Description copied from interface: DSLContext
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 \"<unnamed cursor 1>\""; 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!

Specified by:
fetchValues in interface DSLContext
Parameters:
sql - The SQL
bindings - The bindings
Returns:
The values. This will never be null.
See Also:
SQL, 
DSL.sql(String, Object...)





fetchValues
public List<?> fetchValues(String sql,
 QueryPart... parts)
Description copied from interface: DSLContext
Execute a new query holding plain SQL.
 
 Unlike DSLContext.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 by default, using SQLDialect.ORACLE:
 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

Specified by:
fetchValues in interface DSLContext
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.
See Also:
SQL, 
DSL.sql(String, QueryPart...)





execute
public int execute(SQL sql)
Description copied from interface: DSLContext
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!

Specified by:
execute in interface DSLContext
Parameters:
sql - The SQL
Returns:
The results from the executed query
See Also:
SQL





execute
public int execute(String sql)
Description copied from interface: DSLContext
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!

Specified by:
execute in interface DSLContext
Parameters:
sql - The SQL
Returns:
The results from the executed query
See Also:
SQL





execute
public int execute(String sql,
 Object... bindings)
Description copied from interface: DSLContext
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!

Specified by:
execute in interface DSLContext
Parameters:
sql - The SQL
bindings - The bindings
Returns:
The results from the executed query
See Also:
SQL, 
DSL.sql(String, Object...)





execute
public int execute(String sql,
 QueryPart... parts)
Description copied from interface: DSLContext
Execute a new query holding plain SQL.
 
 Unlike DSLContext.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 by default, using SQLDialect.ORACLE:
 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

Specified by:
execute in interface DSLContext
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
See Also:
SQL, 
DSL.sql(String, QueryPart...)





resultQuery
public ResultQuery<Record> resultQuery(SQL sql)
Description copied from interface: DSLContext
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 \"<unnamed cursor 1>\""; 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!

Specified by:
resultQuery in interface DSLContext
Parameters:
sql - The SQL
Returns:
An executable query
See Also:
SQL





resultQuery
public ResultQuery<Record> resultQuery(String sql)
Description copied from interface: DSLContext
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 \"<unnamed cursor 1>\""; 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!

Specified by:
resultQuery in interface DSLContext
Parameters:
sql - The SQL
Returns:
An executable query
See Also:
SQL





resultQuery
public ResultQuery<Record> resultQuery(String sql,
 Object... bindings)
Description copied from interface: DSLContext
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 \"<unnamed cursor 1>\""; 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!

Specified by:
resultQuery in interface DSLContext
Parameters:
sql - The SQL
bindings - The bindings
Returns:
A query wrapping the plain SQL
See Also:
SQL, 
DSL.sql(String, Object...)





resultQuery
public ResultQuery<Record> resultQuery(String sql,
 QueryPart... parts)
Description copied from interface: DSLContext
Create a new query holding plain SQL.
 
 Unlike DSLContext.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 by default, using SQLDialect.ORACLE:
 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

Specified by:
resultQuery in interface DSLContext
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
public Result<Record> fetch(ResultSet rs)
Description copied from interface: DSLContext
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 DSLContext.fetchLazy(ResultSet), to fetch one Record at a
 time, instead of load the entire ResultSet into a jOOQ
 Result at once.

Specified by:
fetch in interface DSLContext
Parameters:
rs - The JDBC ResultSet to fetch data from
Returns:
The resulting jOOQ Result. This will never be null.





fetch
public Result<Record> fetch(ResultSet rs,
 Field<?>... fields)
Description copied from interface: DSLContext
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 DSLContext.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

Specified by:
fetch in interface DSLContext
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.





fetch
public Result<Record> fetch(ResultSet rs,
 DataType<?>... types)
Description copied from interface: DSLContext
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 DSLContext.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

Specified by:
fetch in interface DSLContext
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.





fetch
public Result<Record> fetch(ResultSet rs,
 Class<?>... types)
Description copied from interface: DSLContext
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 DSLContext.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

Specified by:
fetch in interface DSLContext
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.





fetchOne
public Record fetchOne(ResultSet rs)
Description copied from interface: DSLContext
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.

Specified by:
fetchOne in interface DSLContext
Parameters:
rs - The JDBC ResultSet to fetch data from
Returns:
The record or null, if no record was found.





fetchOne
public Record fetchOne(ResultSet rs,
 Field<?>... fields)
Description copied from interface: DSLContext
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

Specified by:
fetchOne in interface DSLContext
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.





fetchOne
public Record fetchOne(ResultSet rs,
 DataType<?>... types)
Description copied from interface: DSLContext
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

Specified by:
fetchOne in interface DSLContext
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.





fetchOne
public Record fetchOne(ResultSet rs,
 Class<?>... types)
Description copied from interface: DSLContext
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

Specified by:
fetchOne in interface DSLContext
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.





fetchSingle
public Record fetchSingle(ResultSet rs)
Description copied from interface: DSLContext
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.

Specified by:
fetchSingle in interface DSLContext
Parameters:
rs - The JDBC ResultSet to fetch data from
Returns:
The record or null, if no record was found.





fetchSingle
public Record fetchSingle(ResultSet rs,
 Field<?>... fields)
Description copied from interface: DSLContext
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

Specified by:
fetchSingle in interface DSLContext
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.





fetchSingle
public Record fetchSingle(ResultSet rs,
 DataType<?>... types)
Description copied from interface: DSLContext
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

Specified by:
fetchSingle in interface DSLContext
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.





fetchSingle
public Record fetchSingle(ResultSet rs,
 Class<?>... types)
Description copied from interface: DSLContext
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

Specified by:
fetchSingle in interface DSLContext
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.





fetchOptional
public Optional<Record> fetchOptional(ResultSet rs)
Description copied from interface: DSLContext
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.

Specified by:
fetchOptional in interface DSLContext
Parameters:
rs - The JDBC ResultSet to fetch data from
Returns:
The resulting jOOQ record





fetchOptional
public Optional<Record> fetchOptional(ResultSet rs,
 Field<?>... fields)
Description copied from interface: DSLContext
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

Specified by:
fetchOptional in interface DSLContext
Parameters:
rs - The JDBC ResultSet to fetch data from
fields - The fields to use in the desired output
Returns:
The resulting jOOQ record





fetchOptional
public Optional<Record> fetchOptional(ResultSet rs,
 DataType<?>... types)
Description copied from interface: DSLContext
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

Specified by:
fetchOptional in interface DSLContext
Parameters:
rs - The JDBC ResultSet to fetch data from
types - The data types to use in the desired output
Returns:
The resulting jOOQ record





fetchOptional
public Optional<Record> fetchOptional(ResultSet rs,
 Class<?>... types)
Description copied from interface: DSLContext
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

Specified by:
fetchOptional in interface DSLContext
Parameters:
rs - The JDBC ResultSet to fetch data from
types - The data types to use in the desired output
Returns:
The resulting jOOQ record





fetchValue
public Object fetchValue(ResultSet rs)
Description copied from interface: DSLContext
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.

Specified by:
fetchValue in interface DSLContext
Parameters:
rs - The JDBC ResultSet to fetch data from
Returns:
The value or null, if no record was found.





fetchValue
public <T> T fetchValue(ResultSet rs,
 Field<T> field)
Description copied from interface: DSLContext
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

Specified by:
fetchValue in interface DSLContext
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.





fetchValue
public <T> T fetchValue(ResultSet rs,
 DataType<T> type)
Description copied from interface: DSLContext
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

Specified by:
fetchValue in interface DSLContext
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.





fetchValue
public <T> T fetchValue(ResultSet rs,
 Class<T> type)
Description copied from interface: DSLContext
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

Specified by:
fetchValue in interface DSLContext
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.





fetchOptionalValue
public Optional<?> fetchOptionalValue(ResultSet rs)
Description copied from interface: DSLContext
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.

Specified by:
fetchOptionalValue in interface DSLContext
Parameters:
rs - The JDBC ResultSet to fetch data from
Returns:
The resulting value





fetchOptionalValue
public <T> Optional<T> fetchOptionalValue(ResultSet rs,
 Field<T> field)
Description copied from interface: DSLContext
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

Specified by:
fetchOptionalValue in interface DSLContext
Parameters:
rs - The JDBC ResultSet to fetch data from
field - The field to use in the desired output
Returns:
The resulting value





fetchOptionalValue
public <T> Optional<T> fetchOptionalValue(ResultSet rs,
 DataType<T> type)
Description copied from interface: DSLContext
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

Specified by:
fetchOptionalValue in interface DSLContext
Parameters:
rs - The JDBC ResultSet to fetch data from
type - The data type to use in the desired output
Returns:
The resulting value





fetchOptionalValue
public <T> Optional<T> fetchOptionalValue(ResultSet rs,
 Class<T> type)
Description copied from interface: DSLContext
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

Specified by:
fetchOptionalValue in interface DSLContext
Parameters:
rs - The JDBC ResultSet to fetch data from
type - The data types to use in the desired output
Returns:
The resulting value





fetchValues
public List<?> fetchValues(ResultSet rs)
Description copied from interface: DSLContext
Fetch a result from a JDBC ResultSet and return the only
 contained column's values.

Specified by:
fetchValues in interface DSLContext
Parameters:
rs - The JDBC ResultSet to fetch data from
Returns:
The values. This will never be null.





fetchValues
public <T> List<T> fetchValues(ResultSet rs,
 Field<T> field)
Description copied from interface: DSLContext
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

Specified by:
fetchValues in interface DSLContext
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.





fetchValues
public <T> List<T> fetchValues(ResultSet rs,
 DataType<T> type)
Description copied from interface: DSLContext
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

Specified by:
fetchValues in interface DSLContext
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.





fetchValues
public <T> List<T> fetchValues(ResultSet rs,
 Class<T> type)
Description copied from interface: DSLContext
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

Specified by:
fetchValues in interface DSLContext
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.





fetchLazy
public Cursor<Record> fetchLazy(ResultSet rs)
Description copied from interface: DSLContext
Wrap a JDBC ResultSet into a jOOQ Cursor.
 
 Use DSLContext.fetch(ResultSet), to load the entire ResultSet
 into a jOOQ Result at once.

Specified by:
fetchLazy in interface DSLContext
Parameters:
rs - The JDBC ResultSet to fetch data from
Returns:
The cursor. This will never be null.





fetchLazy
public Cursor<Record> fetchLazy(ResultSet rs,
 Field<?>... fields)
Description copied from interface: DSLContext
Wrap a JDBC ResultSet into a jOOQ Cursor.
 
 Use DSLContext.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

Specified by:
fetchLazy in interface DSLContext
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.





fetchLazy
public Cursor<Record> fetchLazy(ResultSet rs,
 DataType<?>... types)
Description copied from interface: DSLContext
Wrap a JDBC ResultSet into a jOOQ Cursor.
 
 Use DSLContext.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

Specified by:
fetchLazy in interface DSLContext
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.





fetchLazy
public Cursor<Record> fetchLazy(ResultSet rs,
 Class<?>... types)
Description copied from interface: DSLContext
Wrap a JDBC ResultSet into a jOOQ Cursor.
 
 Use DSLContext.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

Specified by:
fetchLazy in interface DSLContext
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.





fetchAsync
public CompletionStage<Result<Record>> fetchAsync(ResultSet rs)
Description copied from interface: DSLContext
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().

Specified by:
fetchAsync in interface DSLContext
Parameters:
rs - The JDBC ResultSet to fetch data from
Returns:
The completion stage. The completed result will never be
         null.





fetchAsync
public CompletionStage<Result<Record>> fetchAsync(ResultSet rs,
 Field<?>... fields)
Description copied from interface: DSLContext
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

Specified by:
fetchAsync in interface DSLContext
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
public CompletionStage<Result<Record>> fetchAsync(ResultSet rs,
 DataType<?>... types)
Description copied from interface: DSLContext
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

Specified by:
fetchAsync in interface DSLContext
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
public CompletionStage<Result<Record>> fetchAsync(ResultSet rs,
 Class<?>... types)
Description copied from interface: DSLContext
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

Specified by:
fetchAsync in interface DSLContext
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
public CompletionStage<Result<Record>> fetchAsync(Executor executor,
 ResultSet rs)
Description copied from interface: DSLContext
Fetch results in a new CompletionStage that is asynchronously
 completed by a task running in the given executor.

Specified by:
fetchAsync in interface DSLContext
rs - The JDBC ResultSet to fetch data from
Returns:
The completion stage. The completed result will never be
         null.





fetchAsync
public CompletionStage<Result<Record>> fetchAsync(Executor executor,
 ResultSet rs,
 Field<?>... fields)
Description copied from interface: DSLContext
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

Specified by:
fetchAsync in interface DSLContext
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
public CompletionStage<Result<Record>> fetchAsync(Executor executor,
 ResultSet rs,
 DataType<?>... types)
Description copied from interface: DSLContext
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

Specified by:
fetchAsync in interface DSLContext
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
public CompletionStage<Result<Record>> fetchAsync(Executor executor,
 ResultSet rs,
 Class<?>... types)
Description copied from interface: DSLContext
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

Specified by:
fetchAsync in interface DSLContext
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
public Stream<Record> fetchStream(ResultSet rs)
Description copied from interface: DSLContext
Wrap a JDBC ResultSet into a jOOQ Stream.
 
 Use DSLContext.fetch(ResultSet), to load the entire ResultSet
 into a jOOQ Result at once.

Specified by:
fetchStream in interface DSLContext
Parameters:
rs - The JDBC ResultSet to fetch data from
Returns:
The resulting stream





fetchStream
public Stream<Record> fetchStream(ResultSet rs,
 Field<?>... fields)
Description copied from interface: DSLContext
Wrap a JDBC ResultSet into a jOOQ Stream.
 
 Use DSLContext.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

Specified by:
fetchStream in interface DSLContext
Parameters:
rs - The JDBC ResultSet to fetch data from
fields - The fields to use in the desired output
Returns:
The resulting stream





fetchStream
public Stream<Record> fetchStream(ResultSet rs,
 DataType<?>... types)
Description copied from interface: DSLContext
Wrap a JDBC ResultSet into a jOOQ Stream.
 
 Use DSLContext.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

Specified by:
fetchStream in interface DSLContext
Parameters:
rs - The JDBC ResultSet to fetch data from
types - The data types to use in the desired output
Returns:
The resulting stream





fetchStream
public Stream<Record> fetchStream(ResultSet rs,
 Class<?>... types)
Description copied from interface: DSLContext
Wrap a JDBC ResultSet into a jOOQ Stream.
 
 Use DSLContext.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

Specified by:
fetchStream in interface DSLContext
Parameters:
rs - The JDBC ResultSet to fetch data from
types - The data types to use in the desired output
Returns:
The resulting stream





fetchFromTXT
public Result<Record> fetchFromTXT(String string)
Description copied from interface: DSLContext
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}")

Specified by:
fetchFromTXT in interface DSLContext
Parameters:
string - The formatted string
Returns:
The transformed result. This will never be null.
See Also:
DSLContext.fetchFromTXT(String, String)





fetchFromTXT
public Result<Record> fetchFromTXT(String string,
 String nullLiteral)
Description copied from interface: DSLContext
Fetch all data from a formatted string.
 
 This method supports parsing results from two types of human-readable
 formats:
 
The jOOQ Formattable.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.

Specified by:
fetchFromTXT in interface DSLContext
Parameters:
string - The formatted string
nullLiteral - The string literal to be used as null
            value.
Returns:
The transformed result. This will never be null.





fetchFromHTML
public Result<Record> fetchFromHTML(String string)
Description copied from interface: DSLContext
Convert an HTML table into a jOOQ Result.
 
 This is the inverse operation of Formattable.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>
 
 

Specified by:
fetchFromHTML in interface DSLContext
Parameters:
string - The HTML-formatted string.
Returns:
The transformed result. This will never be null.





fetchFromCSV
public Result<Record> fetchFromCSV(String string)
Description copied from interface: DSLContext
Fetch all data from a CSV string.
 
 This is the same as calling fetchFromCSV(string, ',') and
 the inverse of calling Formattable.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:
 

 Result.getValues(Field, Class)
 Result.getValues(int, Class)
 Result.getValues(String, Class)
 Result.getValues(Field, Converter)
 Result.getValues(int, Converter)
 Result.getValues(String, Converter)
 
 
 Missing values result in null. Empty values result in empty
 Strings

Specified by:
fetchFromCSV in interface DSLContext
Parameters:
string - The CSV string
Returns:
The transformed result. This will never be null.
See Also:
DSLContext.fetchFromCSV(String, char)





fetchFromCSV
public Result<Record> fetchFromCSV(String string,
 char delimiter)
Description copied from interface: DSLContext
Fetch all data from a CSV string.
 
 This is inverse of calling Formattable.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:
 

 Result.getValues(Field, Class)
 Result.getValues(int, Class)
 Result.getValues(String, Class)
 Result.getValues(Field, Converter)
 Result.getValues(int, Converter)
 Result.getValues(String, Converter)
 
 
 Missing values result in null. Empty values result in empty
 Strings

Specified by:
fetchFromCSV in interface DSLContext
Parameters:
string - The CSV string
delimiter - The delimiter to expect between records
Returns:
The transformed result. This will never be null.
See Also:
DSLContext.fetchFromCSV(String), 
DSLContext.fetchFromStringData(List)





fetchFromCSV
public Result<Record> fetchFromCSV(String string,
 boolean header)
Description copied from interface: DSLContext
Fetch all data from a CSV string.
 
 This is the same as calling fetchFromCSV(string, ',') and
 the inverse of calling Formattable.formatCSV(boolean). Rows may
 contain data, which is interpreted as String. Use the various
 conversion methods to retrieve other data types from the
 Result:
 

 Result.getValues(Field, Class)
 Result.getValues(int, Class)
 Result.getValues(String, Class)
 Result.getValues(Field, Converter)
 Result.getValues(int, Converter)
 Result.getValues(String, Converter)
 
 
 Missing values result in null. Empty values result in empty
 Strings

Specified by:
fetchFromCSV in interface DSLContext
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.
See Also:
DSLContext.fetchFromCSV(String, char)





fetchFromCSV
public Result<Record> fetchFromCSV(String string,
 boolean header,
 char delimiter)
Description copied from interface: DSLContext
Fetch all data from a CSV string.
 
 This is inverse of calling Formattable.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:
 

 Result.getValues(Field, Class)
 Result.getValues(int, Class)
 Result.getValues(String, Class)
 Result.getValues(Field, Converter)
 Result.getValues(int, Converter)
 Result.getValues(String, Converter)
 
 
 Missing values result in null. Empty values result in empty
 Strings

Specified by:
fetchFromCSV in interface DSLContext
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.
See Also:
DSLContext.fetchFromCSV(String), 
DSLContext.fetchFromStringData(List)





fetchFromJSON
public Result<Record> fetchFromJSON(String string)
Description copied from interface: DSLContext
Fetch all data from a JSON string.
 
 This is the inverse of calling Formattable.formatJSON(). Use the
 various conversion methods to retrieve other data types from the
 Result:
 

  Result.getValues(Field, Class)
  Result.getValues(int, Class)
  Result.getValues(String, Class)
  Result.getValues(Field, Converter)
  Result.getValues(int, Converter)
  Result.getValues(String, Converter)
 
 
 Missing values result in null. Empty values result in empty
 Strings

Specified by:
fetchFromJSON in interface DSLContext
Parameters:
string - The JSON string
Returns:
The transformed result. This will never be null.





fetchFromXML
public Result<Record> fetchFromXML(String string)
Description copied from interface: DSLContext
Fetch all data from an XML string.
 
 This is the inverse of calling Formattable.formatXML(). Use the
 various conversion methods to retrieve other data types from the
 Result:
 

  Result.getValues(Field, Class)
  Result.getValues(int, Class)
  Result.getValues(String, Class)
  Result.getValues(Field, Converter)
  Result.getValues(int, Converter)
  Result.getValues(String, Converter)
 
 
 Missing values result in null. Empty values result in empty
 Strings

Specified by:
fetchFromXML in interface DSLContext
Parameters:
string - The XML string
Returns:
The transformed result. This will never be null.





fetchFromStringData
public Result<Record> fetchFromStringData(String[]... strings)
Description copied from interface: DSLContext
Fetch all data from a list of strings.
 
 This is used by methods such as
 

  DSLContext.fetchFromCSV(String)
  DSLContext.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.

Specified by:
fetchFromStringData in interface DSLContext
Parameters:
strings - The data to be transformed into a Result
Returns:
The transformed result. This will never be null.
See Also:
DSLContext.fetchFromStringData(List)





fetchFromStringData
public Result<Record> fetchFromStringData(List<String[]> strings)
Description copied from interface: DSLContext
Fetch all data from a list of strings.
 
 This is used by methods such as
 

  DSLContext.fetchFromCSV(String)
  DSLContext.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.

Specified by:
fetchFromStringData in interface DSLContext
Parameters:
strings - The data to be transformed into a Result
Returns:
The transformed result. This will never be null.





fetchFromStringData
public Result<Record> fetchFromStringData(List<String[]> strings,
 boolean header)
Description copied from interface: DSLContext
Fetch all data from a list of strings.
 
 This is used by methods such as
 

 DSLContext.fetchFromCSV(String)
 DSLContext.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.

Specified by:
fetchFromStringData in interface DSLContext
Parameters:
strings - 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
public WithAsStep with(String alias)
Description copied from interface: DSLContext
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
 DSLContext.with(String) for strictly non-recursive CTE
 and DSLContext.withRecursive(String) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep with(String alias,
 String... fieldAliases)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep with(String alias,
 Collection<String> fieldAliases)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep with(Name alias)
Description copied from interface: DSLContext
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
 DSLContext.with(Name) for strictly non-recursive CTE
 and DSLContext.withRecursive(Name) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep with(Name alias,
 Name... fieldAliases)
Description copied from interface: DSLContext
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
 DSLContext.with(Name, Name...) for strictly non-recursive CTE
 and DSLContext.withRecursive(Name, Name...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep with(Name alias,
 Collection<? extends Name> fieldAliases)
Description copied from interface: DSLContext
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
 DSLContext.with(Name, Name...) for strictly non-recursive CTE
 and DSLContext.withRecursive(Name, Name...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep with(String alias,
 Function<? super Field<?>,? extends String> fieldNameFunction)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE and
 DSLContext.withRecursive(String, String...) for strictly recursive CTE.
 

 This works in a similar way as DSLContext.with(String, String...), except
 that all column names are produced by a function that receives the CTE's
 Select columns as input.

Specified by:
with in interface DSLContext





with
public WithAsStep with(String alias,
 BiFunction<? super Field<?>,? super Integer,? extends String> fieldNameFunction)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE and
 DSLContext.withRecursive(String, String...) for strictly recursive CTE.
 

 This works in a similar way as DSLContext.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.

Specified by:
with in interface DSLContext





with
public WithAsStep1 with(String alias,
 String fieldAlias1)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep2 with(String alias,
 String fieldAlias1,
 String fieldAlias2)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep3 with(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep4 with(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep5 with(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep6 with(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep7 with(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep8 with(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep9 with(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep10 with(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep11 with(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep12 with(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11,
 String fieldAlias12)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep13 with(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11,
 String fieldAlias12,
 String fieldAlias13)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep14 with(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11,
 String fieldAlias12,
 String fieldAlias13,
 String fieldAlias14)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep15 with(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11,
 String fieldAlias12,
 String fieldAlias13,
 String fieldAlias14,
 String fieldAlias15)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep16 with(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11,
 String fieldAlias12,
 String fieldAlias13,
 String fieldAlias14,
 String fieldAlias15,
 String fieldAlias16)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep17 with(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11,
 String fieldAlias12,
 String fieldAlias13,
 String fieldAlias14,
 String fieldAlias15,
 String fieldAlias16,
 String fieldAlias17)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep18 with(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11,
 String fieldAlias12,
 String fieldAlias13,
 String fieldAlias14,
 String fieldAlias15,
 String fieldAlias16,
 String fieldAlias17,
 String fieldAlias18)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep19 with(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11,
 String fieldAlias12,
 String fieldAlias13,
 String fieldAlias14,
 String fieldAlias15,
 String fieldAlias16,
 String fieldAlias17,
 String fieldAlias18,
 String fieldAlias19)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep20 with(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11,
 String fieldAlias12,
 String fieldAlias13,
 String fieldAlias14,
 String fieldAlias15,
 String fieldAlias16,
 String fieldAlias17,
 String fieldAlias18,
 String fieldAlias19,
 String fieldAlias20)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep21 with(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11,
 String fieldAlias12,
 String fieldAlias13,
 String fieldAlias14,
 String fieldAlias15,
 String fieldAlias16,
 String fieldAlias17,
 String fieldAlias18,
 String fieldAlias19,
 String fieldAlias20,
 String fieldAlias21)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep22 with(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11,
 String fieldAlias12,
 String fieldAlias13,
 String fieldAlias14,
 String fieldAlias15,
 String fieldAlias16,
 String fieldAlias17,
 String fieldAlias18,
 String fieldAlias19,
 String fieldAlias20,
 String fieldAlias21,
 String fieldAlias22)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep1 with(Name alias,
 Name fieldAlias1)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep2 with(Name alias,
 Name fieldAlias1,
 Name fieldAlias2)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep3 with(Name alias,
 Name fieldAlias1,
 Name fieldAlias2,
 Name fieldAlias3)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep4 with(Name alias,
 Name fieldAlias1,
 Name fieldAlias2,
 Name fieldAlias3,
 Name fieldAlias4)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep5 with(Name alias,
 Name fieldAlias1,
 Name fieldAlias2,
 Name fieldAlias3,
 Name fieldAlias4,
 Name fieldAlias5)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep6 with(Name alias,
 Name fieldAlias1,
 Name fieldAlias2,
 Name fieldAlias3,
 Name fieldAlias4,
 Name fieldAlias5,
 Name fieldAlias6)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep7 with(Name alias,
 Name fieldAlias1,
 Name fieldAlias2,
 Name fieldAlias3,
 Name fieldAlias4,
 Name fieldAlias5,
 Name fieldAlias6,
 Name fieldAlias7)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep8 with(Name alias,
 Name fieldAlias1,
 Name fieldAlias2,
 Name fieldAlias3,
 Name fieldAlias4,
 Name fieldAlias5,
 Name fieldAlias6,
 Name fieldAlias7,
 Name fieldAlias8)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep9 with(Name alias,
 Name fieldAlias1,
 Name fieldAlias2,
 Name fieldAlias3,
 Name fieldAlias4,
 Name fieldAlias5,
 Name fieldAlias6,
 Name fieldAlias7,
 Name fieldAlias8,
 Name fieldAlias9)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithAsStep10 with(Name alias,
 Name fieldAlias1,
 Name fieldAlias2,
 Name fieldAlias3,
 Name fieldAlias4,
 Name fieldAlias5,
 Name fieldAlias6,
 Name fieldAlias7,
 Name fieldAlias8,
 Name fieldAlias9,
 Name fieldAlias10)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithStep with(CommonTableExpression<?>... tables)
Description copied from interface: DSLContext
Create a WITH clause to supply subsequent
 SELECT, UPDATE, INSERT,
 DELETE, and MERGE statements with
 CommonTableExpressions.
 
 Reusable CommonTableExpression types can be constructed through
 

 DSL.name(String...)
 Name.fields(String...)
 
 DerivedColumnList#as(Select)
 
 
 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
 DSLContext.with(CommonTableExpression...) for strictly non-recursive CTE
 and DSLContext.withRecursive(CommonTableExpression...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





with
public WithStep with(Collection<? extends CommonTableExpression<?>> tables)
Description copied from interface: DSLContext
Create a WITH clause to supply subsequent
 SELECT, UPDATE, INSERT,
 DELETE, and MERGE statements with
 CommonTableExpressions.
 
 Reusable CommonTableExpression types can be constructed through
 

 DSL.name(String...)
 Name.fields(String...)
 
 DerivedColumnList#as(Select)
 
 
 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
 DSLContext.with(CommonTableExpression...) for strictly non-recursive CTE
 and DSLContext.withRecursive(CommonTableExpression...) for strictly
 recursive CTE.

Specified by:
with in interface DSLContext





withRecursive
public WithAsStep withRecursive(String alias)
Description copied from interface: DSLContext
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
 DSLContext.with(String) for strictly non-recursive CTE
 and DSLContext.withRecursive(String) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep withRecursive(String alias,
 String... fieldAliases)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep withRecursive(String alias,
 Collection<String> fieldAliases)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep withRecursive(Name alias)
Description copied from interface: DSLContext
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
 DSLContext.with(Name) for strictly non-recursive CTE
 and DSLContext.withRecursive(Name) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep withRecursive(Name alias,
 Name... fieldAliases)
Description copied from interface: DSLContext
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
 DSLContext.with(Name, Name...) for strictly non-recursive CTE
 and DSLContext.withRecursive(Name, Name...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep withRecursive(Name alias,
 Collection<? extends Name> fieldAliases)
Description copied from interface: DSLContext
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
 DSLContext.with(Name, Name...) for strictly non-recursive CTE
 and DSLContext.withRecursive(Name, Name...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep withRecursive(String alias,
 Function<? super Field<?>,? extends String> fieldNameFunction)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.
 

 This works in a similar way as DSLContext.with(String, String...), except
 that all column names are produced by a function that receives the CTE's
 Select columns as input.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep withRecursive(String alias,
 BiFunction<? super Field<?>,? super Integer,? extends String> fieldNameFunction)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.
 

 This works in a similar way as DSLContext.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.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep1 withRecursive(String alias,
 String fieldAlias1)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep2 withRecursive(String alias,
 String fieldAlias1,
 String fieldAlias2)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep3 withRecursive(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep4 withRecursive(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep5 withRecursive(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep6 withRecursive(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep7 withRecursive(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep8 withRecursive(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep9 withRecursive(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep10 withRecursive(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep11 withRecursive(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep12 withRecursive(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11,
 String fieldAlias12)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep13 withRecursive(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11,
 String fieldAlias12,
 String fieldAlias13)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep14 withRecursive(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11,
 String fieldAlias12,
 String fieldAlias13,
 String fieldAlias14)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep15 withRecursive(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11,
 String fieldAlias12,
 String fieldAlias13,
 String fieldAlias14,
 String fieldAlias15)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep16 withRecursive(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11,
 String fieldAlias12,
 String fieldAlias13,
 String fieldAlias14,
 String fieldAlias15,
 String fieldAlias16)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep17 withRecursive(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11,
 String fieldAlias12,
 String fieldAlias13,
 String fieldAlias14,
 String fieldAlias15,
 String fieldAlias16,
 String fieldAlias17)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep18 withRecursive(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11,
 String fieldAlias12,
 String fieldAlias13,
 String fieldAlias14,
 String fieldAlias15,
 String fieldAlias16,
 String fieldAlias17,
 String fieldAlias18)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep19 withRecursive(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11,
 String fieldAlias12,
 String fieldAlias13,
 String fieldAlias14,
 String fieldAlias15,
 String fieldAlias16,
 String fieldAlias17,
 String fieldAlias18,
 String fieldAlias19)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep20 withRecursive(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11,
 String fieldAlias12,
 String fieldAlias13,
 String fieldAlias14,
 String fieldAlias15,
 String fieldAlias16,
 String fieldAlias17,
 String fieldAlias18,
 String fieldAlias19,
 String fieldAlias20)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep21 withRecursive(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11,
 String fieldAlias12,
 String fieldAlias13,
 String fieldAlias14,
 String fieldAlias15,
 String fieldAlias16,
 String fieldAlias17,
 String fieldAlias18,
 String fieldAlias19,
 String fieldAlias20,
 String fieldAlias21)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep22 withRecursive(String alias,
 String fieldAlias1,
 String fieldAlias2,
 String fieldAlias3,
 String fieldAlias4,
 String fieldAlias5,
 String fieldAlias6,
 String fieldAlias7,
 String fieldAlias8,
 String fieldAlias9,
 String fieldAlias10,
 String fieldAlias11,
 String fieldAlias12,
 String fieldAlias13,
 String fieldAlias14,
 String fieldAlias15,
 String fieldAlias16,
 String fieldAlias17,
 String fieldAlias18,
 String fieldAlias19,
 String fieldAlias20,
 String fieldAlias21,
 String fieldAlias22)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep1 withRecursive(Name alias,
 Name fieldAlias1)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep2 withRecursive(Name alias,
 Name fieldAlias1,
 Name fieldAlias2)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep3 withRecursive(Name alias,
 Name fieldAlias1,
 Name fieldAlias2,
 Name fieldAlias3)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep4 withRecursive(Name alias,
 Name fieldAlias1,
 Name fieldAlias2,
 Name fieldAlias3,
 Name fieldAlias4)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep5 withRecursive(Name alias,
 Name fieldAlias1,
 Name fieldAlias2,
 Name fieldAlias3,
 Name fieldAlias4,
 Name fieldAlias5)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep6 withRecursive(Name alias,
 Name fieldAlias1,
 Name fieldAlias2,
 Name fieldAlias3,
 Name fieldAlias4,
 Name fieldAlias5,
 Name fieldAlias6)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep7 withRecursive(Name alias,
 Name fieldAlias1,
 Name fieldAlias2,
 Name fieldAlias3,
 Name fieldAlias4,
 Name fieldAlias5,
 Name fieldAlias6,
 Name fieldAlias7)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep8 withRecursive(Name alias,
 Name fieldAlias1,
 Name fieldAlias2,
 Name fieldAlias3,
 Name fieldAlias4,
 Name fieldAlias5,
 Name fieldAlias6,
 Name fieldAlias7,
 Name fieldAlias8)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep9 withRecursive(Name alias,
 Name fieldAlias1,
 Name fieldAlias2,
 Name fieldAlias3,
 Name fieldAlias4,
 Name fieldAlias5,
 Name fieldAlias6,
 Name fieldAlias7,
 Name fieldAlias8,
 Name fieldAlias9)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithAsStep10 withRecursive(Name alias,
 Name fieldAlias1,
 Name fieldAlias2,
 Name fieldAlias3,
 Name fieldAlias4,
 Name fieldAlias5,
 Name fieldAlias6,
 Name fieldAlias7,
 Name fieldAlias8,
 Name fieldAlias9,
 Name fieldAlias10)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public 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)
Description copied from interface: DSLContext
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
 DSLContext.with(String, String...) for strictly non-recursive CTE
 and DSLContext.withRecursive(String, String...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithStep withRecursive(CommonTableExpression<?>... tables)
Description copied from interface: DSLContext
Create a WITH clause to supply subsequent
 SELECT, UPDATE, INSERT,
 DELETE, and MERGE statements with
 CommonTableExpressions.
 
 Reusable CommonTableExpression types can be constructed through
 

 DSL.name(String...)
 Name.fields(String...)
 
 DerivedColumnList#as(Select)
 
 
 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
 DSLContext.with(CommonTableExpression...) for strictly non-recursive CTE
 and DSLContext.withRecursive(CommonTableExpression...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





withRecursive
public WithStep withRecursive(Collection<? extends CommonTableExpression<?>> tables)
Description copied from interface: DSLContext
Create a WITH clause to supply subsequent
 SELECT, UPDATE, INSERT,
 DELETE, and MERGE statements with
 CommonTableExpressions.
 
 Reusable CommonTableExpression types can be constructed through
 

 DSL.name(String...)
 Name.fields(String...)
 
 DerivedColumnList#as(Select)
 
 
 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
 DSLContext.with(CommonTableExpression...) for strictly non-recursive CTE
 and DSLContext.withRecursive(CommonTableExpression...) for strictly
 recursive CTE.

Specified by:
withRecursive in interface DSLContext





selectFrom
public <R extends Record> SelectWhereStep<R> selectFrom(Table<R> table)
Description copied from interface: DSLContext
Create a new DSL select statement, projecting the known columns from a
 table.
 
 This will project the known columns from the argument table querying
 Fields.fields(). If no known columns are available (e.g. because
 the table has been created using DSL.table(String)), then
 SELECT * is projected.
 

 Example:
 

 
 SELECT table.col1, table.col2 FROM table
 

Specified by:
selectFrom in interface DSLContext





selectFrom
public SelectWhereStep<Record> selectFrom(Name table)
Description copied from interface: DSLContext
Create a new DSL select statement, projecting *.
 
 Without knowing any columns from the argument table (see
 DSLContext.selectFrom(Table)), this will project SELECT *.
 

 Example:
 

 
 SELECT * FROM table
 

Specified by:
selectFrom in interface DSLContext
See Also:
DSL.table(Name)





selectFrom
public SelectWhereStep<Record> selectFrom(SQL sql)
Description copied from interface: DSLContext
Create a new DSL select statement, projecting *.
 
 Without knowing any columns from the argument table (see
 DSLContext.selectFrom(Table)), this will project SELECT *.
 

 Example:
 

 
 SELECT * FROM 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!

Specified by:
selectFrom in interface DSLContext
See Also:
DSL.table(SQL), 
SQL





selectFrom
public SelectWhereStep<Record> selectFrom(String sql)
Description copied from interface: DSLContext
Create a new DSL select statement, projecting *.
 
 Without knowing any columns from the argument table (see
 DSLContext.selectFrom(Table)), this will project SELECT *.
 

 Example:
 

 
 SELECT * FROM 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!

Specified by:
selectFrom in interface DSLContext
See Also:
DSL.table(String), 
DSL.sql(String), 
SQL





selectFrom
public SelectWhereStep<Record> selectFrom(String sql,
 Object... bindings)
Description copied from interface: DSLContext
Create a new DSL select statement, projecting *.
 
 Without knowing any columns from the argument table (see
 DSLContext.selectFrom(Table)), this will project SELECT *.
 

 Example:
 

 
 SELECT * FROM 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!

Specified by:
selectFrom in interface DSLContext
See Also:
DSL.table(String, Object...), 
DSL.sql(String, Object...), 
SQL





selectFrom
public SelectWhereStep<Record> selectFrom(String sql,
 QueryPart... parts)
Description copied from interface: DSLContext
Create a new DSL select statement, projecting *.
 
 Without knowing any columns from the argument table (see
 DSLContext.selectFrom(Table)), this will project SELECT *.
 

 Example:
 

 
 SELECT * FROM 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!

Specified by:
selectFrom in interface DSLContext
See Also:
DSL.table(String, QueryPart...), 
DSL.sql(String, QueryPart...), 
SQL





select
public SelectSelectStep<Record> select(Collection<? extends SelectFieldOrAsterisk> fields)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(Collection) instead.
 

 Example: 
 DSLContext create = DSL.using(configuration);

 create.select(fields)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 
 
 Note that passing an empty collection conveniently produces
 SELECT * semantics, i.e. it:
 

 Renders SELECT tab1.col1, tab1.col2, ..., tabN.colN if
 all columns are known
 Renders SELECT * if not all columns are known, e.g. when
 using plain SQL
 

Specified by:
select in interface DSLContext
See Also:
DSL.select(Collection)





select
public SelectSelectStep<Record> select(SelectFieldOrAsterisk... fields)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectFieldOrAsterisk...) instead.
 

 Example: 
 DSLContext create = DSL.using(configuration);

 create.select(field1, field2)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2)
       .execute();
 
 
 Note that passing an empty collection conveniently produces
 SELECT * semantics, i.e. it:
 

 Renders SELECT tab1.col1, tab1.col2, ..., tabN.colN if
 all columns are known
 Renders SELECT * if not all columns are known, e.g. when
 using plain SQL
 

Specified by:
select in interface DSLContext
See Also:
DSL.select(SelectFieldOrAsterisk...)





select
public <T1> SelectSelectStep<Record1<T1>> select(SelectField<T1> field1)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.select(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Field.in(Select), Field.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectField) instead.
 

 Example: 
 using(configuration)
       .select(field1)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
select in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





select
public <T1,
T2> SelectSelectStep<Record2<T1,T2>> select(SelectField<T1> field1,
 SelectField<T2> field2)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.select(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row2.in(Select), Row2.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .select(field1, field2)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
select in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





select
public <T1,
T2,
T3>
SelectSelectStep<Record3<T1,T2,T3>> select(SelectField<T1> field1,
 SelectField<T2> field2,
 SelectField<T3> field3)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.select(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row3.in(Select), Row3.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .select(field1, field2, field3)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
select in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





select
public <T1,
T2,
T3,
T4>
SelectSelectStep<Record4<T1,T2,T3,T4>> select(SelectField<T1> field1,
 SelectField<T2> field2,
 SelectField<T3> field3,
 SelectField<T4> field4)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.select(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row4.in(Select), Row4.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .select(field1, field2, field3, field4)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
select in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





select
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.select(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row5.in(Select), Row5.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .select(field1, field2, field3, field4, field5)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
select in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





select
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.select(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row6.in(Select), Row6.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .select(field1, field2, field3, .., field5, field6)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
select in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





select
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.select(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row7.in(Select), Row7.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .select(field1, field2, field3, .., field6, field7)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
select in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





select
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.select(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row8.in(Select), Row8.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .select(field1, field2, field3, .., field7, field8)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
select in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





select
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.select(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row9.in(Select), Row9.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .select(field1, field2, field3, .., field8, field9)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
select in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





select
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.select(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row10.in(Select), Row10.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .select(field1, field2, field3, .., field9, field10)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
select in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





select
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.select(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row11.in(Select), Row11.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .select(field1, field2, field3, .., field10, field11)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
select in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





select
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.select(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row12.in(Select), Row12.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .select(field1, field2, field3, .., field11, field12)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
select in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





select
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.select(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row13.in(Select), Row13.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .select(field1, field2, field3, .., field12, field13)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
select in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





select
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.select(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row14.in(Select), Row14.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .select(field1, field2, field3, .., field13, field14)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
select in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





select
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.select(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row15.in(Select), Row15.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .select(field1, field2, field3, .., field14, field15)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
select in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





select
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.select(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row16.in(Select), Row16.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .select(field1, field2, field3, .., field15, field16)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
select in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





select
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.select(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row17.in(Select), Row17.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .select(field1, field2, field3, .., field16, field17)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
select in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





select
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.select(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row18.in(Select), Row18.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .select(field1, field2, field3, .., field17, field18)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
select in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





select
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.select(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row19.in(Select), Row19.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .select(field1, field2, field3, .., field18, field19)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
select in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





select
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.select(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row20.in(Select), Row20.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .select(field1, field2, field3, .., field19, field20)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
select in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





select
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.select(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row21.in(Select), Row21.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .select(field1, field2, field3, .., field20, field21)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
select in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





select
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.select(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row22.in(Select), Row22.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .select(field1, field2, field3, .., field21, field22)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
select in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public SelectSelectStep<Record> selectDistinct(Collection<? extends SelectFieldOrAsterisk> fields)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(Collection) instead.
 

 Example: 
 DSLContext create = DSL.using(configuration);

 create.selectDistinct(fields)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 
 
 Note that passing an empty collection conveniently produces
 SELECT DISTINCT * semantics, i.e. it:
 

 Renders SELECT DISTINCT tab1.col1, tab1.col2, ..., tabN.colN if
 all columns are known
 Renders SELECT DISTINCT * if not all columns are known, e.g. when
 using plain SQL
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(Collection)





selectDistinct
public SelectSelectStep<Record> selectDistinct(SelectFieldOrAsterisk... fields)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectFieldOrAsterisk...) instead.
 

 Example: 
 DSLContext create = DSL.using(configuration);

 create.selectDistinct(field1, field2)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 
 
 Note that passing an empty collection conveniently produces
 SELECT DISTINCT * semantics, i.e. it:
 

 Renders SELECT DISTINCT tab1.col1, tab1.col2, ..., tabN.colN if
 all columns are known
 Renders SELECT DISTINCT * if not all columns are known, e.g. when
 using plain SQL
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public <T1> SelectSelectStep<Record1<T1>> selectDistinct(SelectField<T1> field1)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.selectDistinct(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Field.in(Select), Field.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectField) instead.
 

 Example: 
 using(configuration)
       .selectDistinct(field1)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public <T1,
T2> SelectSelectStep<Record2<T1,T2>> selectDistinct(SelectField<T1> field1,
 SelectField<T2> field2)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.selectDistinct(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row2.in(Select), Row2.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .selectDistinct(field1, field2)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public <T1,
T2,
T3>
SelectSelectStep<Record3<T1,T2,T3>> selectDistinct(SelectField<T1> field1,
 SelectField<T2> field2,
 SelectField<T3> field3)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.selectDistinct(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row3.in(Select), Row3.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .selectDistinct(field1, field2, field3)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public <T1,
T2,
T3,
T4>
SelectSelectStep<Record4<T1,T2,T3,T4>> selectDistinct(SelectField<T1> field1,
 SelectField<T2> field2,
 SelectField<T3> field3,
 SelectField<T4> field4)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.selectDistinct(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row4.in(Select), Row4.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .selectDistinct(field1, field2, field3, field4)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.selectDistinct(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row5.in(Select), Row5.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .selectDistinct(field1, field2, field3, field4, field5)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.selectDistinct(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row6.in(Select), Row6.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .selectDistinct(field1, field2, field3, .., field5, field6)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.selectDistinct(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row7.in(Select), Row7.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .selectDistinct(field1, field2, field3, .., field6, field7)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.selectDistinct(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row8.in(Select), Row8.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .selectDistinct(field1, field2, field3, .., field7, field8)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.selectDistinct(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row9.in(Select), Row9.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .selectDistinct(field1, field2, field3, .., field8, field9)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.selectDistinct(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row10.in(Select), Row10.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .selectDistinct(field1, field2, field3, .., field9, field10)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.selectDistinct(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row11.in(Select), Row11.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .selectDistinct(field1, field2, field3, .., field10, field11)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.selectDistinct(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row12.in(Select), Row12.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .selectDistinct(field1, field2, field3, .., field11, field12)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.selectDistinct(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row13.in(Select), Row13.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .selectDistinct(field1, field2, field3, .., field12, field13)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.selectDistinct(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row14.in(Select), Row14.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .selectDistinct(field1, field2, field3, .., field13, field14)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.selectDistinct(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row15.in(Select), Row15.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .selectDistinct(field1, field2, field3, .., field14, field15)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.selectDistinct(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row16.in(Select), Row16.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .selectDistinct(field1, field2, field3, .., field15, field16)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.selectDistinct(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row17.in(Select), Row17.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .selectDistinct(field1, field2, field3, .., field16, field17)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.selectDistinct(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row18.in(Select), Row18.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .selectDistinct(field1, field2, field3, .., field17, field18)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.selectDistinct(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row19.in(Select), Row19.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .selectDistinct(field1, field2, field3, .., field18, field19)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.selectDistinct(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row20.in(Select), Row20.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .selectDistinct(field1, field2, field3, .., field19, field20)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.selectDistinct(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row21.in(Select), Row21.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .selectDistinct(field1, field2, field3, .., field20, field21)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectDistinct
public <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)
Description copied from interface: DSLContext
Create a new DSL select statement.
 
 This is the same as DSLContext.selectDistinct(SelectFieldOrAsterisk...), except that it
 declares additional record-level typesafety, which is needed by
 Row22.in(Select), Row22.equal(Select) and other predicate
 building methods taking subselect arguments.
 

 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
 

 Example: 
 using(configuration)
       .selectDistinct(field1, field2, field3, .., field21, field22)
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectDistinct in interface DSLContext
See Also:
DSL.selectDistinct(SelectFieldOrAsterisk...), 
DSLContext.selectDistinct(SelectFieldOrAsterisk...)





selectZero
public SelectSelectStep<Record1<Integer>> selectZero()
Description copied from interface: DSLContext
Create a new DSL select statement for a constant 0 literal.
 
 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectZero() instead.
 

 Example: 
 DSLContext create = DSL.using(configuration);

 create.selectZero()
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectZero in interface DSLContext
See Also:
DSL.zero(), 
DSL.selectZero()





selectOne
public SelectSelectStep<Record1<Integer>> selectOne()
Description copied from interface: DSLContext
Create a new DSL select statement for a constant 1 literal.
 
 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectOne() instead.
 

 Example: 
 DSLContext create = DSL.using(configuration);

 create.selectOne()
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectOne in interface DSLContext
See Also:
DSL.one(), 
DSL.selectOne()





selectCount
public SelectSelectStep<Record1<Integer>> selectCount()
Description copied from interface: DSLContext
Create a new DSL select statement for COUNT(*).
 
 This creates an attached, renderable and executable SELECT
 statement from this DSLContext. If you don't need to render or
 execute this SELECT statement (e.g. because you want to
 create a subselect), consider using the static
 DSL.selectCount() instead.
 

 Example: 
 DSLContext create = DSL.using(configuration);

 create.selectCount()
       .from(table1)
       .join(table2).on(field1.equal(field2))
       .where(field1.greaterThan(100))
       .orderBy(field2);
 

Specified by:
selectCount in interface DSLContext
See Also:
DSL.selectCount()





selectQuery
public SelectQuery<Record> selectQuery()
Description copied from interface: DSLContext
Create a new SelectQuery

Specified by:
selectQuery in interface DSLContext





selectQuery
public <R extends Record> SelectQuery<R> selectQuery(TableLike<R> table)
Description copied from interface: DSLContext
Create a new SelectQuery

Specified by:
selectQuery in interface DSLContext
Parameters:
table - The table to select data from
Returns:
The new SelectQuery





insertQuery
public <R extends Record> InsertQuery<R> insertQuery(Table<R> into)
Description copied from interface: DSLContext
Create a new InsertQuery

Specified by:
insertQuery in interface DSLContext
Parameters:
into - The table to insert data into
Returns:
The new InsertQuery





insertInto
public <R extends Record> InsertSetStep<R> insertInto(Table<R> into)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 This type of insert may feel more convenient to some users, as it uses
 the UPDATE statement's SET a = b syntax.
 

 Example: 
 DSLContext create = DSL.using(configuration);

 create.insertInto(table)
       .set(field1, value1)
       .set(field2, value2)
       .newRecord()
       .set(field1, value3)
       .set(field2, value4)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <R extends Record,
T1>
InsertValuesStep1<R,T1> insertInto(Table<R> into,
 Field<T1> field1)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 using(configuration)
       .insertInto(table, field1)
       .values(field1)
       .values(field1)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <R extends Record,
T1,
T2>
InsertValuesStep2<R,T1,T2> insertInto(Table<R> into,
 Field<T1> field1,
 Field<T2> field2)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 using(configuration)
       .insertInto(table, field1, field2)
       .values(field1, field2)
       .values(field1, field2)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <R extends Record,
T1,
T2,
T3>
InsertValuesStep3<R,T1,T2,T3> insertInto(Table<R> into,
 Field<T1> field1,
 Field<T2> field2,
 Field<T3> field3)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 using(configuration)
       .insertInto(table, field1, field2, field3)
       .values(field1, field2, field3)
       .values(field1, field2, field3)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <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)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 using(configuration)
       .insertInto(table, field1, field2, field3, field4)
       .values(field1, field2, field3, field4)
       .values(field1, field2, field3, field4)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <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)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 using(configuration)
       .insertInto(table, field1, field2, field3, field4, field5)
       .values(field1, field2, field3, field4, field5)
       .values(field1, field2, field3, field4, field5)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <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)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 using(configuration)
       .insertInto(table, field1, field2, field3, .., field5, field6)
       .values(valueA1, valueA2, valueA3, .., valueA5, valueA6)
       .values(valueB1, valueB2, valueB3, .., valueB5, valueB6)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <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)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 using(configuration)
       .insertInto(table, field1, field2, field3, .., field6, field7)
       .values(valueA1, valueA2, valueA3, .., valueA6, valueA7)
       .values(valueB1, valueB2, valueB3, .., valueB6, valueB7)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <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)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 using(configuration)
       .insertInto(table, field1, field2, field3, .., field7, field8)
       .values(valueA1, valueA2, valueA3, .., valueA7, valueA8)
       .values(valueB1, valueB2, valueB3, .., valueB7, valueB8)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <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)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 using(configuration)
       .insertInto(table, field1, field2, field3, .., field8, field9)
       .values(valueA1, valueA2, valueA3, .., valueA8, valueA9)
       .values(valueB1, valueB2, valueB3, .., valueB8, valueB9)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <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)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 using(configuration)
       .insertInto(table, field1, field2, field3, .., field9, field10)
       .values(valueA1, valueA2, valueA3, .., valueA9, valueA10)
       .values(valueB1, valueB2, valueB3, .., valueB9, valueB10)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <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)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 using(configuration)
       .insertInto(table, field1, field2, field3, .., field10, field11)
       .values(valueA1, valueA2, valueA3, .., valueA10, valueA11)
       .values(valueB1, valueB2, valueB3, .., valueB10, valueB11)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <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)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 using(configuration)
       .insertInto(table, field1, field2, field3, .., field11, field12)
       .values(valueA1, valueA2, valueA3, .., valueA11, valueA12)
       .values(valueB1, valueB2, valueB3, .., valueB11, valueB12)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <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)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 using(configuration)
       .insertInto(table, field1, field2, field3, .., field12, field13)
       .values(valueA1, valueA2, valueA3, .., valueA12, valueA13)
       .values(valueB1, valueB2, valueB3, .., valueB12, valueB13)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <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)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 using(configuration)
       .insertInto(table, field1, field2, field3, .., field13, field14)
       .values(valueA1, valueA2, valueA3, .., valueA13, valueA14)
       .values(valueB1, valueB2, valueB3, .., valueB13, valueB14)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <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)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 using(configuration)
       .insertInto(table, field1, field2, field3, .., field14, field15)
       .values(valueA1, valueA2, valueA3, .., valueA14, valueA15)
       .values(valueB1, valueB2, valueB3, .., valueB14, valueB15)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <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)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 using(configuration)
       .insertInto(table, field1, field2, field3, .., field15, field16)
       .values(valueA1, valueA2, valueA3, .., valueA15, valueA16)
       .values(valueB1, valueB2, valueB3, .., valueB15, valueB16)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <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)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 using(configuration)
       .insertInto(table, field1, field2, field3, .., field16, field17)
       .values(valueA1, valueA2, valueA3, .., valueA16, valueA17)
       .values(valueB1, valueB2, valueB3, .., valueB16, valueB17)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <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)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 using(configuration)
       .insertInto(table, field1, field2, field3, .., field17, field18)
       .values(valueA1, valueA2, valueA3, .., valueA17, valueA18)
       .values(valueB1, valueB2, valueB3, .., valueB17, valueB18)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <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)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 using(configuration)
       .insertInto(table, field1, field2, field3, .., field18, field19)
       .values(valueA1, valueA2, valueA3, .., valueA18, valueA19)
       .values(valueB1, valueB2, valueB3, .., valueB18, valueB19)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <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)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 using(configuration)
       .insertInto(table, field1, field2, field3, .., field19, field20)
       .values(valueA1, valueA2, valueA3, .., valueA19, valueA20)
       .values(valueB1, valueB2, valueB3, .., valueB19, valueB20)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <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)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 using(configuration)
       .insertInto(table, field1, field2, field3, .., field20, field21)
       .values(valueA1, valueA2, valueA3, .., valueA20, valueA21)
       .values(valueB1, valueB2, valueB3, .., valueB20, valueB21)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <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)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 using(configuration)
       .insertInto(table, field1, field2, field3, .., field21, field22)
       .values(valueA1, valueA2, valueA3, .., valueA21, valueA22)
       .values(valueB1, valueB2, valueB3, .., valueB21, valueB22)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <R extends Record> InsertValuesStepN<R> insertInto(Table<R> into,
 Field<?>... fields)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 DSLContext create = DSL.using(configuration);

 create.insertInto(table, field1, field2)
       .values(value1, value2)
       .values(value3, value4)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





insertInto
public <R extends Record> InsertValuesStepN<R> insertInto(Table<R> into,
 Collection<? extends Field<?>> fields)
Description copied from interface: DSLContext
Create a new DSL insert statement.
 
 Example: 
 DSLContext create = DSL.using(configuration);

 create.insertInto(table, field1, field2)
       .values(value1, value2)
       .values(value3, value4)
       .onDuplicateKeyUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .execute();
 

Specified by:
insertInto in interface DSLContext





updateQuery
public <R extends Record> UpdateQuery<R> updateQuery(Table<R> table)
Description copied from interface: DSLContext
Create a new UpdateQuery

Specified by:
updateQuery in interface DSLContext
Parameters:
table - The table to update data into
Returns:
The new UpdateQuery





update
public <R extends Record> UpdateSetFirstStep<R> update(Table<R> table)
Description copied from interface: DSLContext
Create a new DSL update statement.
 
 Example: 
 DSLContext create = DSL.using(configuration);

 create.update(table)
       .set(field1, value1)
       .set(field2, value2)
       .where(field1.greaterThan(100))
       .execute();
 
 
 Note that some databases support table expressions more complex than
 simple table references. In MySQL, for instance, you can write
 
 create.update(t1.join(t2).on(t1.id.eq(t2.id)))
       .set(t1.value, value1)
       .set(t2.value, value2)
       .where(t1.id.eq(10))
       .execute();
 

Specified by:
update in interface DSLContext





mergeInto
public <R extends Record> MergeUsingStep<R> mergeInto(Table<R> table)
Description copied from interface: DSLContext
Create a new DSL SQL standard MERGE statement.
 
 This statement is available from DSL syntax only. It is known to be
 supported in some way by any of these dialects:
 

 
 dialect
 support type
 documentation
 
 
 DB2
 SQL:2008 standard and major enhancements
 http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com.
 ibm.db2.udb.admin.doc/doc/r0010873.htm
 
 
 HSQLDB
 SQL:2008 standard
 http://hsqldb.org/doc/2.0/guide/dataaccess-chapt.html#N129BA
 
 
 Oracle
 SQL:2008 standard and minor enhancements
 http://download.oracle.com/docs/cd/B28359_01/server.111/b28286/
 statements_9016.htm
 
 
 SQL Server
 Similar to SQL:2008 standard with some major enhancements
 http://msdn.microsoft.com/de-de/library/bb510625.aspx
 
 
 Sybase
 Similar to SQL:2008 standard with some major enhancements
 http://dcx.sybase.com/1100/en/dbreference_en11/merge-statement.html
 
 
 
 Example: 
 DSLContext create = DSL.using(configuration);

 create.mergeInto(table)
       .using(select)
       .on(condition)
       .whenMatchedThenUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .whenNotMatchedThenInsert(field1, field2)
       .values(value1, value2)
       .execute();
 
 
 Note: Using this method, you can also create an H2-specific MERGE
 statement without field specification. See also
 DSLContext.mergeInto(Table, Field...)

Specified by:
mergeInto in interface DSLContext





mergeInto
@Deprecated(forRemoval=true,
            since="3.14")
public <R extends Record,
T1> MergeKeyStep1<R,T1> mergeInto(Table<R> table,
 Field<T1> field1)
Deprecated, for removal: This API element is subject to removal in a future version.
- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table)

Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





mergeInto
@Deprecated(forRemoval=true,
            since="3.14")
public <R extends Record,
T1,
T2>
MergeKeyStep2<R,T1,T2> mergeInto(Table<R> table,
 Field<T1> field1,
 Field<T2> field2)
Deprecated, for removal: This API element is subject to removal in a future version.
- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table)

Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





mergeInto
@Deprecated(forRemoval=true,
            since="3.14")
public <R extends Record,
T1,
T2,
T3>
MergeKeyStep3<R,T1,T2,T3> mergeInto(Table<R> table,
 Field<T1> field1,
 Field<T2> field2,
 Field<T3> field3)
Deprecated, for removal: This API element is subject to removal in a future version.
- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table)

Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





mergeInto
@Deprecated(forRemoval=true,
            since="3.14")
public <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)
Deprecated, for removal: This API element is subject to removal in a future version.
- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table)

Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





mergeInto
@Deprecated(forRemoval=true,
            since="3.14")
public <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)
Deprecated, for removal: This API element is subject to removal in a future version.
- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table)

Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





mergeInto
@Deprecated(forRemoval=true,
            since="3.14")
public <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)
Deprecated, for removal: This API element is subject to removal in a future version.
- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table)

Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





mergeInto
@Deprecated(forRemoval=true,
            since="3.14")
public <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)
Deprecated, for removal: This API element is subject to removal in a future version.
- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table)

Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





mergeInto
@Deprecated(forRemoval=true,
            since="3.14")
public <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)
Deprecated, for removal: This API element is subject to removal in a future version.
- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table)

Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





mergeInto
@Deprecated(forRemoval=true,
            since="3.14")
public <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)
Deprecated, for removal: This API element is subject to removal in a future version.
- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table)

Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





mergeInto
@Deprecated(forRemoval=true,
            since="3.14")
public <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)
Deprecated, for removal: This API element is subject to removal in a future version.
- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table)

Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





mergeInto
@Deprecated(forRemoval=true,
            since="3.14")
public <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)
Deprecated, for removal: This API element is subject to removal in a future version.
- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table)

Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





mergeInto
@Deprecated(forRemoval=true,
            since="3.14")
public <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)
Deprecated, for removal: This API element is subject to removal in a future version.
- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table)

Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





mergeInto
@Deprecated(forRemoval=true,
            since="3.14")
public <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)
Deprecated, for removal: This API element is subject to removal in a future version.
- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table)

Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





mergeInto
@Deprecated(forRemoval=true,
            since="3.14")
public <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)
Deprecated, for removal: This API element is subject to removal in a future version.
- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table)

Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





mergeInto
@Deprecated(forRemoval=true,
            since="3.14")
public <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)
Deprecated, for removal: This API element is subject to removal in a future version.
- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table)

Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





mergeInto
@Deprecated(forRemoval=true,
            since="3.14")
public <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)
Deprecated, for removal: This API element is subject to removal in a future version.
- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table)

Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





mergeInto
@Deprecated(forRemoval=true,
            since="3.14")
public <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)
Deprecated, for removal: This API element is subject to removal in a future version.
- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table)

Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





mergeInto
@Deprecated(forRemoval=true,
            since="3.14")
public <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)
Deprecated, for removal: This API element is subject to removal in a future version.
- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table)

Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





mergeInto
@Deprecated(forRemoval=true,
            since="3.14")
public <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)
Deprecated, for removal: This API element is subject to removal in a future version.
- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table)

Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





mergeInto
@Deprecated(forRemoval=true,
            since="3.14")
public <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)
Deprecated, for removal: This API element is subject to removal in a future version.
- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table)

Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





mergeInto
@Deprecated(forRemoval=true,
            since="3.14")
public <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)
Deprecated, for removal: This API element is subject to removal in a future version.
- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table)

Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





mergeInto
@Deprecated(forRemoval=true,
            since="3.14")
public <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)
Deprecated, for removal: This API element is subject to removal in a future version.
- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via mergeInto(Table)

Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





mergeInto
public <R extends Record> MergeKeyStepN<R> mergeInto(Table<R> table,
 Field<?>... fields)
Description copied from interface: DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
 MERGE) or SQLDialect.HANA UPSERT).
 
 This statement is available from DSL syntax only. It is known to be
 supported in some way by any of these dialects:
 

 
 H2
 H2 natively supports this special syntax
 https://www.h2database.com/html/commands.html#merge_into
 
 
 HANA
 HANA natively supports this syntax
 http://help.sap.com/saphelp_hanaplatform/helpdata/en/20/fc06a7751910149892c0d09be21a38/content.htm
 
 
 PostgreSQL
 This database can emulate the H2-specific MERGE statement via
 INSERT .. ON CONFLICT DO UPDATE
 http://www.postgresql.org/docs/9.5/static/sql-insert.html
 
 
 DB2, HSQLDB, Oracle, SQL Server, Sybase SQL Anywhere
 These databases can emulate the H2-specific MERGE statement using a
 standard SQL MERGE statement, without restrictions
 See DSLContext.mergeInto(Table) for the standard MERGE statement
 
 

Specified by:
mergeInto in interface DSLContext





mergeInto
public <R extends Record> MergeKeyStepN<R> mergeInto(Table<R> table,
 Collection<? extends Field<?>> fields)
Description copied from interface: DSLContext
Create a new DSL merge statement (H2-specific syntax).

Specified by:
mergeInto in interface DSLContext
See Also:
DSLContext.mergeInto(Table, Field...)





deleteQuery
public <R extends Record> DeleteQuery<R> deleteQuery(Table<R> table)
Description copied from interface: DSLContext
Create a new DeleteQuery

Specified by:
deleteQuery in interface DSLContext
Parameters:
table - The table to delete data from
Returns:
The new DeleteQuery





delete
public <R extends Record> DeleteUsingStep<R> delete(Table<R> table)
Description copied from interface: DSLContext
Create a new DSL delete statement.
 
 This is an alias for DSLContext.deleteFrom(Table)

Specified by:
delete in interface DSLContext





deleteFrom
public <R extends Record> DeleteUsingStep<R> deleteFrom(Table<R> table)
Description copied from interface: DSLContext
Create a new DSL delete statement.
 
 Example: 
 DSLContext create = DSL.using(configuration);

 create.deleteFrom(table)
       .where(field1.greaterThan(100))
       .execute();
 
 
 Some but not all databases support aliased tables in delete statements.
 

 Note that some databases support table expressions more complex than
 simple table references. In MySQL, for instance, you can write this to
 form a multi table DELETE statement:
 

 
 create.delete(t1.join(t2).on(t1.id.eq(t2.id)))
       .where(t1.id.eq(10))
       .execute();
 
 
 For single table delete statements that depend on multiple tables, use
 the DeleteUsingStep.using(TableLike) clause, instead:
 

 
 create.delete(t1)
       .using(t2)
       .where(t1.id.eq(t2.id))
       .and(t1.id.eq(10))
       .execute();
 

Specified by:
deleteFrom in interface DSLContext





batched
public void batched(BatchedRunnable runnable)
Description copied from interface: DSLContext
Run a BatchedRunnable on a BatchedConnection,
 delaying execution as long as possible before batching.

Specified by:
batched in interface DSLContext
See Also:
BatchedConnection for details.





batchedResult
public <T> T batchedResult(BatchedCallable<T> callable)
Description copied from interface: DSLContext
Run a BatchedRunnable on a BatchedConnection,
 delaying execution as long as possible before batching.

Specified by:
batchedResult in interface DSLContext
See Also:
BatchedConnection for details.





batch
public Batch batch(Query... queries)
Description copied from interface: DSLContext
Create a batch statement to execute a set of queries in batch mode
 (without bind values).
 
 This essentially runs the following logic: 
 Statement s = connection.createStatement();

 for (Query query : queries) {
     s.addBatch(query.getSQL(true));
 }

 s.execute();
 

Specified by:
batch in interface DSLContext
See Also:
Statement.executeBatch()





batch
public Batch batch(Queries queries)
Description copied from interface: DSLContext
Create a batch statement to execute a set of queries in batch mode
 (without bind values).
 
 This essentially runs the following logic: 
 Statement s = connection.createStatement();

 for (Query query : queries) {
     s.addBatch(query.getSQL(true));
 }

 s.execute();
 

Specified by:
batch in interface DSLContext
See Also:
Statement.executeBatch()





batch
public Batch batch(String... queries)
Description copied from interface: DSLContext
Create a batch statement to execute a set of queries in batch mode
 (without bind values).
 
 This is a convenience method for calling
 
batch(query(queries[0]), query(queries[1]), ...)
.

Specified by:
batch in interface DSLContext
See Also:
DSLContext.query(String), 
DSLContext.batch(Query...), 
Statement.executeBatch()





batch
public Batch batch(Collection<? extends Query> queries)
Description copied from interface: DSLContext
Create a batch statement to execute a set of queries in batch mode
 (without bind values).
 
 This essentially runs the following logic: 
 Statement s = connection.createStatement();

 for (Query query : queries) {
     s.addBatch(query.getSQL(true));
 }

 s.execute();
 

Specified by:
batch in interface DSLContext
See Also:
Statement.executeBatch()





batch
public BatchBindStep batch(Query query)
Description copied from interface: DSLContext
Create a batch statement to execute a set of queries in batch mode (with
 bind values).
 
 When running 
 create.batch(query)
       .bind(valueA1, valueA2)
       .bind(valueB1, valueB2)
       .execute();
 
 
 This essentially runs the following logic: 
 Statement s = connection.prepareStatement(query.getSQL(false));

 for (Object[] bindValues : allBindValues) {
     for (Object bindValue : bindValues) {
         s.setXXX(bindValue);
     }

     s.addBatch();
 }

 s.execute();
 
 
 Note: bind values will be inlined to a static batch query as in
 DSLContext.batch(Query...), if you choose to execute queries with
 Settings.getStatementType() == StatementType.STATIC_STATEMENT

Specified by:
batch in interface DSLContext
See Also:
Statement.executeBatch()





batch
public BatchBindStep batch(String sql)
Description copied from interface: DSLContext
Create a batch statement to execute a set of queries in batch mode (with
 bind values).
 
 This is a convenience method for calling
 
batch(query(sql))
.

Specified by:
batch in interface DSLContext
See Also:
DSLContext.query(String), 
DSLContext.batch(Query), 
Statement.executeBatch()





batch
public Batch batch(Query query,
 Object[]... bindings)
Description copied from interface: DSLContext
Create a batch statement to execute a set of queries in batch mode (with
 bind values).
 
 This is a convenience method for calling DSLContext.batch(Query) and then
 binding values one by one using BatchBindStep.bind(Object...)
 

 Note: bind values will be inlined to a static batch query as in
 DSLContext.batch(Query...), if you choose to execute queries with
 Settings.getStatementType() == StatementType.STATIC_STATEMENT

Specified by:
batch in interface DSLContext
See Also:
DSLContext.batch(Query), 
Statement.executeBatch()





batch
public Batch batch(String sql,
 Object[]... bindings)
Description copied from interface: DSLContext
Create a batch statement to execute a set of queries in batch mode (with
 bind values).
 
 This is a convenience method for calling
 
batch(query(sql), bindings)
.

Specified by:
batch in interface DSLContext
See Also:
DSLContext.query(String), 
DSLContext.batch(Query, Object[][]), 
Statement.executeBatch()





batchStore
public Batch batchStore(UpdatableRecord<?>... records)
Description copied from interface: DSLContext
Create a batch statement to execute a set of INSERT and
 UPDATE queries in batch mode (with bind values) according to
 UpdatableRecord.store() semantics.
 
 This batch operation can be executed in two modes:
 

 
With
 Settings.getStatementType() == StatementType.PREPARED_STATEMENT
 (the default)
 
 In this mode, record order is preserved as much as possible, as long as
 two subsequent records generate the same SQL (with bind variables). The
 number of executed batch operations corresponds to
 [number of distinct rendered SQL statements]. In the worst
 case, this corresponds to the number of total records.
 

 The record type order is preserved in the way they are passed to this
 method. This is an example of how statements will be ordered: 
 // Let's assume, odd numbers result in INSERTs and even numbers in UPDATES
 // Let's also assume a[n] are all of the same type, just as b[n], c[n]...
 int[] result = create.batchStore(a1, a2, a3, b1, a4, c1, b3, a5)
                      .execute();
 
 The above results in result.length == 8 and
 the following 4 separate batch statements:
 
 INSERT a1, a3, a5
 UPDATE a2, a4
 INSERT b1, b3
 INSERT c1
 
 
 
With
 Settings.getStatementType() == StatementType.STATIC_STATEMENT
 
 
 This mode may be better for large and complex batch store operations, as
 the order of records is preserved entirely, and jOOQ can guarantee that
 only a single batch statement is serialised to the database.
 

 
A note on MERGE / UPSERT semantics
 
 This method (just like UpdatableRecord.store()) does not
 implement the semantics of an actual UPSERT or
 MERGE statement, which delegates the decision of whether to
 INSERT or UPDATE a record to the database. The
 decision is made by the client (jOOQ) depending on whether each
 individual record has been fetched from the database prior to storing it.

Specified by:
batchStore in interface DSLContext
See Also:
UpdatableRecord.store(), 
Statement.executeBatch()





batchStore
public Batch batchStore(Collection<? extends UpdatableRecord<?>> records)
Description copied from interface: DSLContext
Create a batch statement to execute a set of INSERT and
 UPDATE queries in batch mode (with bind values) according to
 UpdatableRecord.store() semantics.

Specified by:
batchStore in interface DSLContext
See Also:
DSLContext.batchStore(UpdatableRecord...), 
UpdatableRecord.store(), 
Statement.executeBatch()





batchInsert
public Batch batchInsert(TableRecord<?>... records)
Description copied from interface: DSLContext
Create a batch statement to execute a set of INSERT queries
 in batch mode (with bind values) according to
 TableRecord.insert() semantics.

Specified by:
batchInsert in interface DSLContext
See Also:
DSLContext.batchStore(UpdatableRecord...), 
TableRecord.insert(), 
Statement.executeBatch()





batchInsert
public Batch batchInsert(Collection<? extends TableRecord<?>> records)
Description copied from interface: DSLContext
Create a batch statement to execute a set of INSERT queries
 in batch mode (with bind values) according to
 TableRecord.insert() semantics.

Specified by:
batchInsert in interface DSLContext
See Also:
DSLContext.batchStore(UpdatableRecord...), 
Statement.executeBatch()





batchUpdate
public Batch batchUpdate(UpdatableRecord<?>... records)
Description copied from interface: DSLContext
Create a batch statement to execute a set of UPDATE queries
 in batch mode (with bind values) according to
 UpdatableRecord.update() semantics.

Specified by:
batchUpdate in interface DSLContext
See Also:
DSLContext.batchStore(UpdatableRecord...), 
UpdatableRecord.update(), 
Statement.executeBatch()





batchUpdate
public Batch batchUpdate(Collection<? extends UpdatableRecord<?>> records)
Description copied from interface: DSLContext
Create a batch statement to execute a set of UPDATE queries
 in batch mode (with bind values) according to
 UpdatableRecord.update() semantics.

Specified by:
batchUpdate in interface DSLContext
See Also:
DSLContext.batchStore(UpdatableRecord...), 
UpdatableRecord.update(), 
Statement.executeBatch()





batchMerge
public Batch batchMerge(UpdatableRecord<?>... records)
Description copied from interface: DSLContext
Create a batch statement to execute a set of MERGE queries
 in batch mode (with bind values) according to
 UpdatableRecord.merge() semantics.

Specified by:
batchMerge in interface DSLContext
See Also:
UpdatableRecord.merge(), 
Statement.executeBatch()





batchMerge
public Batch batchMerge(Collection<? extends UpdatableRecord<?>> records)
Description copied from interface: DSLContext
Create a batch statement to execute a set of MERGE queries
 in batch mode (with bind values) according to
 UpdatableRecord.merge() semantics.

Specified by:
batchMerge in interface DSLContext
See Also:
UpdatableRecord.merge(), 
Statement.executeBatch()





batchDelete
public Batch batchDelete(UpdatableRecord<?>... records)
Description copied from interface: DSLContext
Create a batch statement to execute a set of DELETE queries
 in batch mode (with bind values) according to
 UpdatableRecord.delete() sematics.
 
 This batch operation can be executed in two modes:
 

 
With
 Settings.getStatementType() == StatementType.PREPARED_STATEMENT
 (the default)
 
 In this mode, record order is preserved as much as possible, as long as
 two subsequent records generate the same SQL (with bind variables). The
 number of executed batch operations corresponds to
 [number of distinct rendered SQL statements]. In the worst
 case, this corresponds to the number of total records.
 

 The record type order is preserved in the way they are passed to this
 method. This is an example of how statements will be ordered: 
 // Let's assume a[n] are all of the same type, just as b[n], c[n]...
 int[] result = create.batchDelete(a1, a2, a3, b1, a4, c1, c2, a5)
                      .execute();
 
 The above results in result.length == 8 and
 the following 5 separate batch statements:
 
 DELETE a1, a2, a3
 DELETE b1
 DELETE a4
 DELETE c1, c2
 DELETE a5
 
 
 
With
 Settings.getStatementType() == StatementType.STATIC_STATEMENT
 
 
 This mode may be better for large and complex batch delete operations, as
 the order of records is preserved entirely, and jOOQ can guarantee that
 only a single batch statement is serialised to the database.

Specified by:
batchDelete in interface DSLContext
See Also:
UpdatableRecord.delete(), 
Statement.executeBatch()





batchDelete
public Batch batchDelete(Collection<? extends UpdatableRecord<?>> records)
Description copied from interface: DSLContext
Create a batch statement to execute a set of DELETE queries
 in batch mode (with bind values) according to
 UpdatableRecord.delete() sematics.

Specified by:
batchDelete in interface DSLContext
See Also:
DSLContext.batchDelete(UpdatableRecord...), 
UpdatableRecord.delete(), 
Statement.executeBatch()





alterDatabase
public AlterDatabaseStep alterDatabase(@Name
 String database)
Description copied from interface: DSLContext
The ALTER DATABASE statement.

Specified by:
alterDatabase in interface DSLContext
See Also:
DSL.alterDatabase(String)





alterDatabase
public AlterDatabaseStep alterDatabase(Name database)
Description copied from interface: DSLContext
The ALTER DATABASE statement.

Specified by:
alterDatabase in interface DSLContext
See Also:
DSL.alterDatabase(Name)





alterDatabase
public AlterDatabaseStep alterDatabase(Catalog database)
Description copied from interface: DSLContext
The ALTER DATABASE statement.

Specified by:
alterDatabase in interface DSLContext
See Also:
DSL.alterDatabase(Catalog)





alterDatabaseIfExists
public AlterDatabaseStep alterDatabaseIfExists(@Name
 String database)
Description copied from interface: DSLContext
The ALTER DATABASE IF EXISTS statement.

Specified by:
alterDatabaseIfExists in interface DSLContext
See Also:
DSL.alterDatabaseIfExists(String)





alterDatabaseIfExists
public AlterDatabaseStep alterDatabaseIfExists(Name database)
Description copied from interface: DSLContext
The ALTER DATABASE IF EXISTS statement.

Specified by:
alterDatabaseIfExists in interface DSLContext
See Also:
DSL.alterDatabaseIfExists(Name)





alterDatabaseIfExists
public AlterDatabaseStep alterDatabaseIfExists(Catalog database)
Description copied from interface: DSLContext
The ALTER DATABASE IF EXISTS statement.

Specified by:
alterDatabaseIfExists in interface DSLContext
See Also:
DSL.alterDatabaseIfExists(Catalog)





alterDomain
public <T> AlterDomainStep<T> alterDomain(@Name
 String domain)
Description copied from interface: DSLContext
The ALTER DOMAIN statement.

Specified by:
alterDomain in interface DSLContext
See Also:
DSL.alterDomain(String)





alterDomain
public <T> AlterDomainStep<T> alterDomain(Name domain)
Description copied from interface: DSLContext
The ALTER DOMAIN statement.

Specified by:
alterDomain in interface DSLContext
See Also:
DSL.alterDomain(Name)





alterDomain
public <T> AlterDomainStep<T> alterDomain(Domain<T> domain)
Description copied from interface: DSLContext
The ALTER DOMAIN statement.

Specified by:
alterDomain in interface DSLContext
See Also:
DSL.alterDomain(Domain)





alterDomainIfExists
public <T> AlterDomainStep<T> alterDomainIfExists(@Name
 String domain)
Description copied from interface: DSLContext
The ALTER DOMAIN IF EXISTS statement.

Specified by:
alterDomainIfExists in interface DSLContext
See Also:
DSL.alterDomainIfExists(String)





alterDomainIfExists
public <T> AlterDomainStep<T> alterDomainIfExists(Name domain)
Description copied from interface: DSLContext
The ALTER DOMAIN IF EXISTS statement.

Specified by:
alterDomainIfExists in interface DSLContext
See Also:
DSL.alterDomainIfExists(Name)





alterDomainIfExists
public <T> AlterDomainStep<T> alterDomainIfExists(Domain<T> domain)
Description copied from interface: DSLContext
The ALTER DOMAIN IF EXISTS statement.

Specified by:
alterDomainIfExists in interface DSLContext
See Also:
DSL.alterDomainIfExists(Domain)





alterIndex
public AlterIndexOnStep alterIndex(@Name
 String index)
Description copied from interface: DSLContext
The ALTER INDEX statement.

Specified by:
alterIndex in interface DSLContext
See Also:
DSL.alterIndex(String)





alterIndex
public AlterIndexOnStep alterIndex(Name index)
Description copied from interface: DSLContext
The ALTER INDEX statement.

Specified by:
alterIndex in interface DSLContext
See Also:
DSL.alterIndex(Name)





alterIndex
public AlterIndexOnStep alterIndex(Index index)
Description copied from interface: DSLContext
The ALTER INDEX statement.

Specified by:
alterIndex in interface DSLContext
See Also:
DSL.alterIndex(Index)





alterIndexIfExists
public AlterIndexOnStep alterIndexIfExists(@Name
 String index)
Description copied from interface: DSLContext
The ALTER INDEX IF EXISTS statement.

Specified by:
alterIndexIfExists in interface DSLContext
See Also:
DSL.alterIndexIfExists(String)





alterIndexIfExists
public AlterIndexOnStep alterIndexIfExists(Name index)
Description copied from interface: DSLContext
The ALTER INDEX IF EXISTS statement.

Specified by:
alterIndexIfExists in interface DSLContext
See Also:
DSL.alterIndexIfExists(Name)





alterIndexIfExists
public AlterIndexOnStep alterIndexIfExists(Index index)
Description copied from interface: DSLContext
The ALTER INDEX IF EXISTS statement.

Specified by:
alterIndexIfExists in interface DSLContext
See Also:
DSL.alterIndexIfExists(Index)





alterSchema
public AlterSchemaStep alterSchema(@Name
 String schema)
Description copied from interface: DSLContext
The ALTER SCHEMA statement.

Specified by:
alterSchema in interface DSLContext
See Also:
DSL.alterSchema(String)





alterSchema
public AlterSchemaStep alterSchema(Name schema)
Description copied from interface: DSLContext
The ALTER SCHEMA statement.

Specified by:
alterSchema in interface DSLContext
See Also:
DSL.alterSchema(Name)





alterSchema
public AlterSchemaStep alterSchema(Schema schema)
Description copied from interface: DSLContext
The ALTER SCHEMA statement.

Specified by:
alterSchema in interface DSLContext
See Also:
DSL.alterSchema(Schema)





alterSchemaIfExists
public AlterSchemaStep alterSchemaIfExists(@Name
 String schema)
Description copied from interface: DSLContext
The ALTER SCHEMA IF EXISTS statement.

Specified by:
alterSchemaIfExists in interface DSLContext
See Also:
DSL.alterSchemaIfExists(String)





alterSchemaIfExists
public AlterSchemaStep alterSchemaIfExists(Name schema)
Description copied from interface: DSLContext
The ALTER SCHEMA IF EXISTS statement.

Specified by:
alterSchemaIfExists in interface DSLContext
See Also:
DSL.alterSchemaIfExists(Name)





alterSchemaIfExists
public AlterSchemaStep alterSchemaIfExists(Schema schema)
Description copied from interface: DSLContext
The ALTER SCHEMA IF EXISTS statement.

Specified by:
alterSchemaIfExists in interface DSLContext
See Also:
DSL.alterSchemaIfExists(Schema)





alterSequence
public AlterSequenceStep<Number> alterSequence(@Name
 String sequence)
Description copied from interface: DSLContext
The ALTER SEQUENCE statement.

Specified by:
alterSequence in interface DSLContext
See Also:
DSL.alterSequence(String)





alterSequence
public AlterSequenceStep<Number> alterSequence(Name sequence)
Description copied from interface: DSLContext
The ALTER SEQUENCE statement.

Specified by:
alterSequence in interface DSLContext
See Also:
DSL.alterSequence(Name)





alterSequence
public <T extends Number> AlterSequenceStep<T> alterSequence(Sequence<T> sequence)
Description copied from interface: DSLContext
The ALTER SEQUENCE statement.

Specified by:
alterSequence in interface DSLContext
See Also:
DSL.alterSequence(Sequence)





alterSequenceIfExists
public AlterSequenceStep<Number> alterSequenceIfExists(@Name
 String sequence)
Description copied from interface: DSLContext
The ALTER SEQUENCE IF EXISTS statement.

Specified by:
alterSequenceIfExists in interface DSLContext
See Also:
DSL.alterSequenceIfExists(String)





alterSequenceIfExists
public AlterSequenceStep<Number> alterSequenceIfExists(Name sequence)
Description copied from interface: DSLContext
The ALTER SEQUENCE IF EXISTS statement.

Specified by:
alterSequenceIfExists in interface DSLContext
See Also:
DSL.alterSequenceIfExists(Name)





alterSequenceIfExists
public <T extends Number> AlterSequenceStep<T> alterSequenceIfExists(Sequence<T> sequence)
Description copied from interface: DSLContext
The ALTER SEQUENCE IF EXISTS statement.

Specified by:
alterSequenceIfExists in interface DSLContext
See Also:
DSL.alterSequenceIfExists(Sequence)





alterType
public AlterTypeStep alterType(@Name
 String type)
Description copied from interface: DSLContext
The ALTER TYPE statement.

Specified by:
alterType in interface DSLContext
See Also:
DSL.alterType(String)





alterType
public AlterTypeStep alterType(Name type)
Description copied from interface: DSLContext
The ALTER TYPE statement.

Specified by:
alterType in interface DSLContext
See Also:
DSL.alterType(Name)





alterView
public AlterViewStep alterView(@Name
 String view)
Description copied from interface: DSLContext
The ALTER VIEW statement.

Specified by:
alterView in interface DSLContext
See Also:
DSL.alterView(String)





alterView
public AlterViewStep alterView(Name view)
Description copied from interface: DSLContext
The ALTER VIEW statement.

Specified by:
alterView in interface DSLContext
See Also:
DSL.alterView(Name)





alterView
public AlterViewStep alterView(Table<?> view)
Description copied from interface: DSLContext
The ALTER VIEW statement.

Specified by:
alterView in interface DSLContext
See Also:
DSL.alterView(Table)





alterViewIfExists
public AlterViewStep alterViewIfExists(@Name
 String view)
Description copied from interface: DSLContext
The ALTER VIEW IF EXISTS statement.

Specified by:
alterViewIfExists in interface DSLContext
See Also:
DSL.alterViewIfExists(String)





alterViewIfExists
public AlterViewStep alterViewIfExists(Name view)
Description copied from interface: DSLContext
The ALTER VIEW IF EXISTS statement.

Specified by:
alterViewIfExists in interface DSLContext
See Also:
DSL.alterViewIfExists(Name)





alterViewIfExists
public AlterViewStep alterViewIfExists(Table<?> view)
Description copied from interface: DSLContext
The ALTER VIEW IF EXISTS statement.

Specified by:
alterViewIfExists in interface DSLContext
See Also:
DSL.alterViewIfExists(Table)





commentOnTable
public CommentOnIsStep commentOnTable(@Name
 String table)
Description copied from interface: DSLContext
The COMMENT ON TABLE statement.

Specified by:
commentOnTable in interface DSLContext
See Also:
DSL.commentOnTable(String)





commentOnTable
public CommentOnIsStep commentOnTable(Name table)
Description copied from interface: DSLContext
The COMMENT ON TABLE statement.

Specified by:
commentOnTable in interface DSLContext
See Also:
DSL.commentOnTable(Name)





commentOnTable
public CommentOnIsStep commentOnTable(Table<?> table)
Description copied from interface: DSLContext
The COMMENT ON TABLE statement.

Specified by:
commentOnTable in interface DSLContext
See Also:
DSL.commentOnTable(Table)





commentOnView
public CommentOnIsStep commentOnView(@Name
 String view)
Description copied from interface: DSLContext
The COMMENT ON VIEW statement.

Specified by:
commentOnView in interface DSLContext
See Also:
DSL.commentOnView(String)





commentOnView
public CommentOnIsStep commentOnView(Name view)
Description copied from interface: DSLContext
The COMMENT ON VIEW statement.

Specified by:
commentOnView in interface DSLContext
See Also:
DSL.commentOnView(Name)





commentOnView
public CommentOnIsStep commentOnView(Table<?> view)
Description copied from interface: DSLContext
The COMMENT ON VIEW statement.

Specified by:
commentOnView in interface DSLContext
See Also:
DSL.commentOnView(Table)





commentOnColumn
public CommentOnIsStep commentOnColumn(@Name
 String field)
Description copied from interface: DSLContext
The COMMENT ON COLUMN statement.

Specified by:
commentOnColumn in interface DSLContext
See Also:
DSL.commentOnColumn(String)





commentOnColumn
public CommentOnIsStep commentOnColumn(Name field)
Description copied from interface: DSLContext
The COMMENT ON COLUMN statement.

Specified by:
commentOnColumn in interface DSLContext
See Also:
DSL.commentOnColumn(Name)





commentOnColumn
public CommentOnIsStep commentOnColumn(Field<?> field)
Description copied from interface: DSLContext
The COMMENT ON COLUMN statement.

Specified by:
commentOnColumn in interface DSLContext
See Also:
DSL.commentOnColumn(Field)





createDatabase
public CreateDatabaseFinalStep createDatabase(@Name
 String database)
Description copied from interface: DSLContext
The CREATE DATABASE statement.

Specified by:
createDatabase in interface DSLContext
See Also:
DSL.createDatabase(String)





createDatabase
public CreateDatabaseFinalStep createDatabase(Name database)
Description copied from interface: DSLContext
The CREATE DATABASE statement.

Specified by:
createDatabase in interface DSLContext
See Also:
DSL.createDatabase(Name)





createDatabase
public CreateDatabaseFinalStep createDatabase(Catalog database)
Description copied from interface: DSLContext
The CREATE DATABASE statement.

Specified by:
createDatabase in interface DSLContext
See Also:
DSL.createDatabase(Catalog)





createDatabaseIfNotExists
public CreateDatabaseFinalStep createDatabaseIfNotExists(@Name
 String database)
Description copied from interface: DSLContext
The CREATE DATABASE IF NOT EXISTS statement.

Specified by:
createDatabaseIfNotExists in interface DSLContext
See Also:
DSL.createDatabaseIfNotExists(String)





createDatabaseIfNotExists
public CreateDatabaseFinalStep createDatabaseIfNotExists(Name database)
Description copied from interface: DSLContext
The CREATE DATABASE IF NOT EXISTS statement.

Specified by:
createDatabaseIfNotExists in interface DSLContext
See Also:
DSL.createDatabaseIfNotExists(Name)





createDatabaseIfNotExists
public CreateDatabaseFinalStep createDatabaseIfNotExists(Catalog database)
Description copied from interface: DSLContext
The CREATE DATABASE IF NOT EXISTS statement.

Specified by:
createDatabaseIfNotExists in interface DSLContext
See Also:
DSL.createDatabaseIfNotExists(Catalog)





createDomain
public CreateDomainAsStep createDomain(@Name
 String domain)
Description copied from interface: DSLContext
The CREATE DOMAIN statement.

Specified by:
createDomain in interface DSLContext
See Also:
DSL.createDomain(String)





createDomain
public CreateDomainAsStep createDomain(Name domain)
Description copied from interface: DSLContext
The CREATE DOMAIN statement.

Specified by:
createDomain in interface DSLContext
See Also:
DSL.createDomain(Name)





createDomain
public CreateDomainAsStep createDomain(Domain<?> domain)
Description copied from interface: DSLContext
The CREATE DOMAIN statement.

Specified by:
createDomain in interface DSLContext
See Also:
DSL.createDomain(Domain)





createDomainIfNotExists
public CreateDomainAsStep createDomainIfNotExists(@Name
 String domain)
Description copied from interface: DSLContext
The CREATE DOMAIN IF NOT EXISTS statement.

Specified by:
createDomainIfNotExists in interface DSLContext
See Also:
DSL.createDomainIfNotExists(String)





createDomainIfNotExists
public CreateDomainAsStep createDomainIfNotExists(Name domain)
Description copied from interface: DSLContext
The CREATE DOMAIN IF NOT EXISTS statement.

Specified by:
createDomainIfNotExists in interface DSLContext
See Also:
DSL.createDomainIfNotExists(Name)





createDomainIfNotExists
public CreateDomainAsStep createDomainIfNotExists(Domain<?> domain)
Description copied from interface: DSLContext
The CREATE DOMAIN IF NOT EXISTS statement.

Specified by:
createDomainIfNotExists in interface DSLContext
See Also:
DSL.createDomainIfNotExists(Domain)





createFunction
@Pro
public CreateFunctionParametersStep createFunction(@Name
 String function)
Description copied from interface: DSLContext
The CREATE FUNCTION statement.

Specified by:
createFunction in interface DSLContext
See Also:
DSL.createFunction(String)





createFunction
@Pro
public CreateFunctionParametersStep createFunction(Name function)
Description copied from interface: DSLContext
The CREATE FUNCTION statement.

Specified by:
createFunction in interface DSLContext
See Also:
DSL.createFunction(Name)





createOrReplaceFunction
@Pro
public CreateFunctionParametersStep createOrReplaceFunction(@Name
 String function)
Description copied from interface: DSLContext
The CREATE OR REPLACE FUNCTION statement.

Specified by:
createOrReplaceFunction in interface DSLContext
See Also:
DSL.createOrReplaceFunction(String)





createOrReplaceFunction
@Pro
public CreateFunctionParametersStep createOrReplaceFunction(Name function)
Description copied from interface: DSLContext
The CREATE OR REPLACE FUNCTION statement.

Specified by:
createOrReplaceFunction in interface DSLContext
See Also:
DSL.createOrReplaceFunction(Name)





createIndex
public CreateIndexStep createIndex(@Name
 String index)
Description copied from interface: DSLContext
The CREATE INDEX statement.

Specified by:
createIndex in interface DSLContext
See Also:
DSL.createIndex(String)





createIndex
public CreateIndexStep createIndex(Name index)
Description copied from interface: DSLContext
The CREATE INDEX statement.

Specified by:
createIndex in interface DSLContext
See Also:
DSL.createIndex(Name)





createIndex
public CreateIndexStep createIndex(Index index)
Description copied from interface: DSLContext
The CREATE INDEX statement.

Specified by:
createIndex in interface DSLContext
See Also:
DSL.createIndex(Index)





createIndex
public CreateIndexStep createIndex()
Description copied from interface: DSLContext
The CREATE INDEX statement.

Specified by:
createIndex in interface DSLContext
See Also:
DSL.createIndex()





createIndexIfNotExists
public CreateIndexStep createIndexIfNotExists(@Name
 String index)
Description copied from interface: DSLContext
The CREATE INDEX IF NOT EXISTS statement.

Specified by:
createIndexIfNotExists in interface DSLContext
See Also:
DSL.createIndexIfNotExists(String)





createIndexIfNotExists
public CreateIndexStep createIndexIfNotExists(Name index)
Description copied from interface: DSLContext
The CREATE INDEX IF NOT EXISTS statement.

Specified by:
createIndexIfNotExists in interface DSLContext
See Also:
DSL.createIndexIfNotExists(Name)





createIndexIfNotExists
public CreateIndexStep createIndexIfNotExists(Index index)
Description copied from interface: DSLContext
The CREATE INDEX IF NOT EXISTS statement.

Specified by:
createIndexIfNotExists in interface DSLContext
See Also:
DSL.createIndexIfNotExists(Index)





createIndexIfNotExists
public CreateIndexStep createIndexIfNotExists()
Description copied from interface: DSLContext
The CREATE INDEX IF NOT EXISTS statement.

Specified by:
createIndexIfNotExists in interface DSLContext
See Also:
DSL.createIndexIfNotExists()





createUniqueIndex
public CreateIndexStep createUniqueIndex(@Name
 String index)
Description copied from interface: DSLContext
The CREATE UNIQUE INDEX statement.

Specified by:
createUniqueIndex in interface DSLContext
See Also:
DSL.createUniqueIndex(String)





createUniqueIndex
public CreateIndexStep createUniqueIndex(Name index)
Description copied from interface: DSLContext
The CREATE UNIQUE INDEX statement.

Specified by:
createUniqueIndex in interface DSLContext
See Also:
DSL.createUniqueIndex(Name)





createUniqueIndex
public CreateIndexStep createUniqueIndex(Index index)
Description copied from interface: DSLContext
The CREATE UNIQUE INDEX statement.

Specified by:
createUniqueIndex in interface DSLContext
See Also:
DSL.createUniqueIndex(Index)





createUniqueIndex
public CreateIndexStep createUniqueIndex()
Description copied from interface: DSLContext
The CREATE UNIQUE INDEX statement.

Specified by:
createUniqueIndex in interface DSLContext
See Also:
DSL.createUniqueIndex()





createUniqueIndexIfNotExists
public CreateIndexStep createUniqueIndexIfNotExists(@Name
 String index)
Description copied from interface: DSLContext
The CREATE UNIQUE INDEX IF NOT EXISTS statement.

Specified by:
createUniqueIndexIfNotExists in interface DSLContext
See Also:
DSL.createUniqueIndexIfNotExists(String)





createUniqueIndexIfNotExists
public CreateIndexStep createUniqueIndexIfNotExists(Name index)
Description copied from interface: DSLContext
The CREATE UNIQUE INDEX IF NOT EXISTS statement.

Specified by:
createUniqueIndexIfNotExists in interface DSLContext
See Also:
DSL.createUniqueIndexIfNotExists(Name)





createUniqueIndexIfNotExists
public CreateIndexStep createUniqueIndexIfNotExists(Index index)
Description copied from interface: DSLContext
The CREATE UNIQUE INDEX IF NOT EXISTS statement.

Specified by:
createUniqueIndexIfNotExists in interface DSLContext
See Also:
DSL.createUniqueIndexIfNotExists(Index)





createUniqueIndexIfNotExists
public CreateIndexStep createUniqueIndexIfNotExists()
Description copied from interface: DSLContext
The CREATE UNIQUE INDEX IF NOT EXISTS statement.

Specified by:
createUniqueIndexIfNotExists in interface DSLContext
See Also:
DSL.createUniqueIndexIfNotExists()





createProcedure
@Pro
public CreateProcedureParametersStep createProcedure(@Name
 String procedure)
Description copied from interface: DSLContext
The CREATE PROCEDURE statement.

Specified by:
createProcedure in interface DSLContext
See Also:
DSL.createProcedure(String)





createProcedure
@Pro
public CreateProcedureParametersStep createProcedure(Name procedure)
Description copied from interface: DSLContext
The CREATE PROCEDURE statement.

Specified by:
createProcedure in interface DSLContext
See Also:
DSL.createProcedure(Name)





createOrReplaceProcedure
@Pro
public CreateProcedureParametersStep createOrReplaceProcedure(@Name
 String procedure)
Description copied from interface: DSLContext
The CREATE OR REPLACE PROCEDURE statement.

Specified by:
createOrReplaceProcedure in interface DSLContext
See Also:
DSL.createOrReplaceProcedure(String)





createOrReplaceProcedure
@Pro
public CreateProcedureParametersStep createOrReplaceProcedure(Name procedure)
Description copied from interface: DSLContext
The CREATE OR REPLACE PROCEDURE statement.

Specified by:
createOrReplaceProcedure in interface DSLContext
See Also:
DSL.createOrReplaceProcedure(Name)





createTrigger
@Pro
public CreateTriggerEventStep createTrigger(@Name
 String trigger)
Description copied from interface: DSLContext
The CREATE TRIGGER statement.

Specified by:
createTrigger in interface DSLContext
See Also:
DSL.createTrigger(String)





createTrigger
@Pro
public CreateTriggerEventStep createTrigger(Name trigger)
Description copied from interface: DSLContext
The CREATE TRIGGER statement.

Specified by:
createTrigger in interface DSLContext
See Also:
DSL.createTrigger(Name)





createOrReplaceTrigger
@Pro
public CreateTriggerEventStep createOrReplaceTrigger(@Name
 String trigger)
Description copied from interface: DSLContext
The CREATE OR REPLACE TRIGGER statement.

Specified by:
createOrReplaceTrigger in interface DSLContext
See Also:
DSL.createOrReplaceTrigger(String)





createOrReplaceTrigger
@Pro
public CreateTriggerEventStep createOrReplaceTrigger(Name trigger)
Description copied from interface: DSLContext
The CREATE OR REPLACE TRIGGER statement.

Specified by:
createOrReplaceTrigger in interface DSLContext
See Also:
DSL.createOrReplaceTrigger(Name)





createSchema
public CreateSchemaFinalStep createSchema(@Name
 String schema)
Description copied from interface: DSLContext
The CREATE SCHEMA statement.

Specified by:
createSchema in interface DSLContext
See Also:
DSL.createSchema(String)





createSchema
public CreateSchemaFinalStep createSchema(Name schema)
Description copied from interface: DSLContext
The CREATE SCHEMA statement.

Specified by:
createSchema in interface DSLContext
See Also:
DSL.createSchema(Name)





createSchema
public CreateSchemaFinalStep createSchema(Schema schema)
Description copied from interface: DSLContext
The CREATE SCHEMA statement.

Specified by:
createSchema in interface DSLContext
See Also:
DSL.createSchema(Schema)





createSchemaIfNotExists
public CreateSchemaFinalStep createSchemaIfNotExists(@Name
 String schema)
Description copied from interface: DSLContext
The CREATE SCHEMA IF NOT EXISTS statement.

Specified by:
createSchemaIfNotExists in interface DSLContext
See Also:
DSL.createSchemaIfNotExists(String)





createSchemaIfNotExists
public CreateSchemaFinalStep createSchemaIfNotExists(Name schema)
Description copied from interface: DSLContext
The CREATE SCHEMA IF NOT EXISTS statement.

Specified by:
createSchemaIfNotExists in interface DSLContext
See Also:
DSL.createSchemaIfNotExists(Name)





createSchemaIfNotExists
public CreateSchemaFinalStep createSchemaIfNotExists(Schema schema)
Description copied from interface: DSLContext
The CREATE SCHEMA IF NOT EXISTS statement.

Specified by:
createSchemaIfNotExists in interface DSLContext
See Also:
DSL.createSchemaIfNotExists(Schema)





createSequence
public CreateSequenceFlagsStep createSequence(@Name
 String sequence)
Description copied from interface: DSLContext
The CREATE SEQUENCE statement.

Specified by:
createSequence in interface DSLContext
See Also:
DSL.createSequence(String)





createSequence
public CreateSequenceFlagsStep createSequence(Name sequence)
Description copied from interface: DSLContext
The CREATE SEQUENCE statement.

Specified by:
createSequence in interface DSLContext
See Also:
DSL.createSequence(Name)





createSequence
public CreateSequenceFlagsStep createSequence(Sequence<?> sequence)
Description copied from interface: DSLContext
The CREATE SEQUENCE statement.

Specified by:
createSequence in interface DSLContext
See Also:
DSL.createSequence(Sequence)





createSequenceIfNotExists
public CreateSequenceFlagsStep createSequenceIfNotExists(@Name
 String sequence)
Description copied from interface: DSLContext
The CREATE SEQUENCE IF NOT EXISTS statement.

Specified by:
createSequenceIfNotExists in interface DSLContext
See Also:
DSL.createSequenceIfNotExists(String)





createSequenceIfNotExists
public CreateSequenceFlagsStep createSequenceIfNotExists(Name sequence)
Description copied from interface: DSLContext
The CREATE SEQUENCE IF NOT EXISTS statement.

Specified by:
createSequenceIfNotExists in interface DSLContext
See Also:
DSL.createSequenceIfNotExists(Name)





createSequenceIfNotExists
public CreateSequenceFlagsStep createSequenceIfNotExists(Sequence<?> sequence)
Description copied from interface: DSLContext
The CREATE SEQUENCE IF NOT EXISTS statement.

Specified by:
createSequenceIfNotExists in interface DSLContext
See Also:
DSL.createSequenceIfNotExists(Sequence)





dropDatabase
public DropDatabaseFinalStep dropDatabase(@Name
 String database)
Description copied from interface: DSLContext
The DROP DATABASE statement.

Specified by:
dropDatabase in interface DSLContext
See Also:
DSL.dropDatabase(String)





dropDatabase
public DropDatabaseFinalStep dropDatabase(Name database)
Description copied from interface: DSLContext
The DROP DATABASE statement.

Specified by:
dropDatabase in interface DSLContext
See Also:
DSL.dropDatabase(Name)





dropDatabase
public DropDatabaseFinalStep dropDatabase(Catalog database)
Description copied from interface: DSLContext
The DROP DATABASE statement.

Specified by:
dropDatabase in interface DSLContext
See Also:
DSL.dropDatabase(Catalog)





dropDatabaseIfExists
public DropDatabaseFinalStep dropDatabaseIfExists(@Name
 String database)
Description copied from interface: DSLContext
The DROP DATABASE IF EXISTS statement.

Specified by:
dropDatabaseIfExists in interface DSLContext
See Also:
DSL.dropDatabaseIfExists(String)





dropDatabaseIfExists
public DropDatabaseFinalStep dropDatabaseIfExists(Name database)
Description copied from interface: DSLContext
The DROP DATABASE IF EXISTS statement.

Specified by:
dropDatabaseIfExists in interface DSLContext
See Also:
DSL.dropDatabaseIfExists(Name)





dropDatabaseIfExists
public DropDatabaseFinalStep dropDatabaseIfExists(Catalog database)
Description copied from interface: DSLContext
The DROP DATABASE IF EXISTS statement.

Specified by:
dropDatabaseIfExists in interface DSLContext
See Also:
DSL.dropDatabaseIfExists(Catalog)





dropDomain
public DropDomainCascadeStep dropDomain(@Name
 String domain)
Description copied from interface: DSLContext
The DROP DOMAIN statement.

Specified by:
dropDomain in interface DSLContext
See Also:
DSL.dropDomain(String)





dropDomain
public DropDomainCascadeStep dropDomain(Name domain)
Description copied from interface: DSLContext
The DROP DOMAIN statement.

Specified by:
dropDomain in interface DSLContext
See Also:
DSL.dropDomain(Name)





dropDomain
public DropDomainCascadeStep dropDomain(Domain<?> domain)
Description copied from interface: DSLContext
The DROP DOMAIN statement.

Specified by:
dropDomain in interface DSLContext
See Also:
DSL.dropDomain(Domain)





dropDomainIfExists
public DropDomainCascadeStep dropDomainIfExists(@Name
 String domain)
Description copied from interface: DSLContext
The DROP DOMAIN IF EXISTS statement.

Specified by:
dropDomainIfExists in interface DSLContext
See Also:
DSL.dropDomainIfExists(String)





dropDomainIfExists
public DropDomainCascadeStep dropDomainIfExists(Name domain)
Description copied from interface: DSLContext
The DROP DOMAIN IF EXISTS statement.

Specified by:
dropDomainIfExists in interface DSLContext
See Also:
DSL.dropDomainIfExists(Name)





dropDomainIfExists
public DropDomainCascadeStep dropDomainIfExists(Domain<?> domain)
Description copied from interface: DSLContext
The DROP DOMAIN IF EXISTS statement.

Specified by:
dropDomainIfExists in interface DSLContext
See Also:
DSL.dropDomainIfExists(Domain)





dropFunction
@Pro
public DDLQuery dropFunction(@Name
 String function)
Description copied from interface: DSLContext
The DROP FUNCTION statement.

Specified by:
dropFunction in interface DSLContext
See Also:
DSL.dropFunction(String)





dropFunction
@Pro
public DDLQuery dropFunction(Name function)
Description copied from interface: DSLContext
The DROP FUNCTION statement.

Specified by:
dropFunction in interface DSLContext
See Also:
DSL.dropFunction(Name)





dropFunctionIfExists
@Pro
public DDLQuery dropFunctionIfExists(@Name
 String function)
Description copied from interface: DSLContext
The DROP FUNCTION IF EXISTS statement.

Specified by:
dropFunctionIfExists in interface DSLContext
See Also:
DSL.dropFunctionIfExists(String)





dropFunctionIfExists
@Pro
public DDLQuery dropFunctionIfExists(Name function)
Description copied from interface: DSLContext
The DROP FUNCTION IF EXISTS statement.

Specified by:
dropFunctionIfExists in interface DSLContext
See Also:
DSL.dropFunctionIfExists(Name)





dropIndex
public DropIndexOnStep dropIndex(@Name
 String index)
Description copied from interface: DSLContext
The DROP INDEX statement.

Specified by:
dropIndex in interface DSLContext
See Also:
DSL.dropIndex(String)





dropIndex
public DropIndexOnStep dropIndex(Name index)
Description copied from interface: DSLContext
The DROP INDEX statement.

Specified by:
dropIndex in interface DSLContext
See Also:
DSL.dropIndex(Name)





dropIndex
public DropIndexOnStep dropIndex(Index index)
Description copied from interface: DSLContext
The DROP INDEX statement.

Specified by:
dropIndex in interface DSLContext
See Also:
DSL.dropIndex(Index)





dropIndexIfExists
public DropIndexOnStep dropIndexIfExists(@Name
 String index)
Description copied from interface: DSLContext
The DROP INDEX IF EXISTS statement.

Specified by:
dropIndexIfExists in interface DSLContext
See Also:
DSL.dropIndexIfExists(String)





dropIndexIfExists
public DropIndexOnStep dropIndexIfExists(Name index)
Description copied from interface: DSLContext
The DROP INDEX IF EXISTS statement.

Specified by:
dropIndexIfExists in interface DSLContext
See Also:
DSL.dropIndexIfExists(Name)





dropIndexIfExists
public DropIndexOnStep dropIndexIfExists(Index index)
Description copied from interface: DSLContext
The DROP INDEX IF EXISTS statement.

Specified by:
dropIndexIfExists in interface DSLContext
See Also:
DSL.dropIndexIfExists(Index)





dropProcedure
@Pro
public DDLQuery dropProcedure(@Name
 String procedure)
Description copied from interface: DSLContext
The DROP PROCEDURE statement.

Specified by:
dropProcedure in interface DSLContext
See Also:
DSL.dropProcedure(String)





dropProcedure
@Pro
public DDLQuery dropProcedure(Name procedure)
Description copied from interface: DSLContext
The DROP PROCEDURE statement.

Specified by:
dropProcedure in interface DSLContext
See Also:
DSL.dropProcedure(Name)





dropProcedureIfExists
@Pro
public DDLQuery dropProcedureIfExists(@Name
 String procedure)
Description copied from interface: DSLContext
The DROP PROCEDURE IF EXISTS statement.

Specified by:
dropProcedureIfExists in interface DSLContext
See Also:
DSL.dropProcedureIfExists(String)





dropProcedureIfExists
@Pro
public DDLQuery dropProcedureIfExists(Name procedure)
Description copied from interface: DSLContext
The DROP PROCEDURE IF EXISTS statement.

Specified by:
dropProcedureIfExists in interface DSLContext
See Also:
DSL.dropProcedureIfExists(Name)





dropSchema
public DropSchemaStep dropSchema(@Name
 String schema)
Description copied from interface: DSLContext
The DROP SCHEMA statement.

Specified by:
dropSchema in interface DSLContext
See Also:
DSL.dropSchema(String)





dropSchema
public DropSchemaStep dropSchema(Name schema)
Description copied from interface: DSLContext
The DROP SCHEMA statement.

Specified by:
dropSchema in interface DSLContext
See Also:
DSL.dropSchema(Name)





dropSchema
public DropSchemaStep dropSchema(Schema schema)
Description copied from interface: DSLContext
The DROP SCHEMA statement.

Specified by:
dropSchema in interface DSLContext
See Also:
DSL.dropSchema(Schema)





dropSchemaIfExists
public DropSchemaStep dropSchemaIfExists(@Name
 String schema)
Description copied from interface: DSLContext
The DROP SCHEMA IF EXISTS statement.

Specified by:
dropSchemaIfExists in interface DSLContext
See Also:
DSL.dropSchemaIfExists(String)





dropSchemaIfExists
public DropSchemaStep dropSchemaIfExists(Name schema)
Description copied from interface: DSLContext
The DROP SCHEMA IF EXISTS statement.

Specified by:
dropSchemaIfExists in interface DSLContext
See Also:
DSL.dropSchemaIfExists(Name)





dropSchemaIfExists
public DropSchemaStep dropSchemaIfExists(Schema schema)
Description copied from interface: DSLContext
The DROP SCHEMA IF EXISTS statement.

Specified by:
dropSchemaIfExists in interface DSLContext
See Also:
DSL.dropSchemaIfExists(Schema)





dropSequence
public DropSequenceFinalStep dropSequence(@Name
 String sequence)
Description copied from interface: DSLContext
The DROP SEQUENCE statement.

Specified by:
dropSequence in interface DSLContext
See Also:
DSL.dropSequence(String)





dropSequence
public DropSequenceFinalStep dropSequence(Name sequence)
Description copied from interface: DSLContext
The DROP SEQUENCE statement.

Specified by:
dropSequence in interface DSLContext
See Also:
DSL.dropSequence(Name)





dropSequence
public DropSequenceFinalStep dropSequence(Sequence<?> sequence)
Description copied from interface: DSLContext
The DROP SEQUENCE statement.

Specified by:
dropSequence in interface DSLContext
See Also:
DSL.dropSequence(Sequence)





dropSequenceIfExists
public DropSequenceFinalStep dropSequenceIfExists(@Name
 String sequence)
Description copied from interface: DSLContext
The DROP SEQUENCE IF EXISTS statement.

Specified by:
dropSequenceIfExists in interface DSLContext
See Also:
DSL.dropSequenceIfExists(String)





dropSequenceIfExists
public DropSequenceFinalStep dropSequenceIfExists(Name sequence)
Description copied from interface: DSLContext
The DROP SEQUENCE IF EXISTS statement.

Specified by:
dropSequenceIfExists in interface DSLContext
See Also:
DSL.dropSequenceIfExists(Name)





dropSequenceIfExists
public DropSequenceFinalStep dropSequenceIfExists(Sequence<?> sequence)
Description copied from interface: DSLContext
The DROP SEQUENCE IF EXISTS statement.

Specified by:
dropSequenceIfExists in interface DSLContext
See Also:
DSL.dropSequenceIfExists(Sequence)





dropTable
public DropTableStep dropTable(@Name
 String table)
Description copied from interface: DSLContext
The DROP TABLE statement.

Specified by:
dropTable in interface DSLContext
See Also:
DSL.dropTable(String)





dropTable
public DropTableStep dropTable(Name table)
Description copied from interface: DSLContext
The DROP TABLE statement.

Specified by:
dropTable in interface DSLContext
See Also:
DSL.dropTable(Name)





dropTable
public DropTableStep dropTable(Table<?> table)
Description copied from interface: DSLContext
The DROP TABLE statement.

Specified by:
dropTable in interface DSLContext
See Also:
DSL.dropTable(Table)





dropTableIfExists
public DropTableStep dropTableIfExists(@Name
 String table)
Description copied from interface: DSLContext
The DROP TABLE IF EXISTS statement.

Specified by:
dropTableIfExists in interface DSLContext
See Also:
DSL.dropTableIfExists(String)





dropTableIfExists
public DropTableStep dropTableIfExists(Name table)
Description copied from interface: DSLContext
The DROP TABLE IF EXISTS statement.

Specified by:
dropTableIfExists in interface DSLContext
See Also:
DSL.dropTableIfExists(Name)





dropTableIfExists
public DropTableStep dropTableIfExists(Table<?> table)
Description copied from interface: DSLContext
The DROP TABLE IF EXISTS statement.

Specified by:
dropTableIfExists in interface DSLContext
See Also:
DSL.dropTableIfExists(Table)





dropTemporaryTable
public DropTableStep dropTemporaryTable(@Name
 String table)
Description copied from interface: DSLContext
The DROP TEMPORARY TABLE statement.

Specified by:
dropTemporaryTable in interface DSLContext
See Also:
DSL.dropTemporaryTable(String)





dropTemporaryTable
public DropTableStep dropTemporaryTable(Name table)
Description copied from interface: DSLContext
The DROP TEMPORARY TABLE statement.

Specified by:
dropTemporaryTable in interface DSLContext
See Also:
DSL.dropTemporaryTable(Name)





dropTemporaryTable
public DropTableStep dropTemporaryTable(Table<?> table)
Description copied from interface: DSLContext
The DROP TEMPORARY TABLE statement.

Specified by:
dropTemporaryTable in interface DSLContext
See Also:
DSL.dropTemporaryTable(Table)





dropTemporaryTableIfExists
public DropTableStep dropTemporaryTableIfExists(@Name
 String table)
Description copied from interface: DSLContext
The DROP TEMPORARY TABLE IF EXISTS statement.

Specified by:
dropTemporaryTableIfExists in interface DSLContext
See Also:
DSL.dropTemporaryTableIfExists(String)





dropTemporaryTableIfExists
public DropTableStep dropTemporaryTableIfExists(Name table)
Description copied from interface: DSLContext
The DROP TEMPORARY TABLE IF EXISTS statement.

Specified by:
dropTemporaryTableIfExists in interface DSLContext
See Also:
DSL.dropTemporaryTableIfExists(Name)





dropTemporaryTableIfExists
public DropTableStep dropTemporaryTableIfExists(Table<?> table)
Description copied from interface: DSLContext
The DROP TEMPORARY TABLE IF EXISTS statement.

Specified by:
dropTemporaryTableIfExists in interface DSLContext
See Also:
DSL.dropTemporaryTableIfExists(Table)





dropTrigger
@Pro
public DDLQuery dropTrigger(@Name
 String trigger)
Description copied from interface: DSLContext
The DROP TRIGGER statement.

Specified by:
dropTrigger in interface DSLContext
See Also:
DSL.dropTrigger(String)





dropTrigger
@Pro
public DDLQuery dropTrigger(Name trigger)
Description copied from interface: DSLContext
The DROP TRIGGER statement.

Specified by:
dropTrigger in interface DSLContext
See Also:
DSL.dropTrigger(Name)





dropTriggerIfExists
@Pro
public DDLQuery dropTriggerIfExists(@Name
 String trigger)
Description copied from interface: DSLContext
The DROP TRIGGER IF EXISTS statement.

Specified by:
dropTriggerIfExists in interface DSLContext
See Also:
DSL.dropTriggerIfExists(String)





dropTriggerIfExists
@Pro
public DDLQuery dropTriggerIfExists(Name trigger)
Description copied from interface: DSLContext
The DROP TRIGGER IF EXISTS statement.

Specified by:
dropTriggerIfExists in interface DSLContext
See Also:
DSL.dropTriggerIfExists(Name)





dropView
public DropViewFinalStep dropView(@Name
 String view)
Description copied from interface: DSLContext
The DROP VIEW statement.

Specified by:
dropView in interface DSLContext
See Also:
DSL.dropView(String)





dropView
public DropViewFinalStep dropView(Name view)
Description copied from interface: DSLContext
The DROP VIEW statement.

Specified by:
dropView in interface DSLContext
See Also:
DSL.dropView(Name)





dropView
public DropViewFinalStep dropView(Table<?> view)
Description copied from interface: DSLContext
The DROP VIEW statement.

Specified by:
dropView in interface DSLContext
See Also:
DSL.dropView(Table)





dropViewIfExists
public DropViewFinalStep dropViewIfExists(@Name
 String view)
Description copied from interface: DSLContext
The DROP VIEW IF EXISTS statement.

Specified by:
dropViewIfExists in interface DSLContext
See Also:
DSL.dropViewIfExists(String)





dropViewIfExists
public DropViewFinalStep dropViewIfExists(Name view)
Description copied from interface: DSLContext
The DROP VIEW IF EXISTS statement.

Specified by:
dropViewIfExists in interface DSLContext
See Also:
DSL.dropViewIfExists(Name)





dropViewIfExists
public DropViewFinalStep dropViewIfExists(Table<?> view)
Description copied from interface: DSLContext
The DROP VIEW IF EXISTS statement.

Specified by:
dropViewIfExists in interface DSLContext
See Also:
DSL.dropViewIfExists(Table)





grant
public GrantOnStep grant(Privilege privileges)
Description copied from interface: DSLContext
The GRANT statement.

Specified by:
grant in interface DSLContext
See Also:
DSL.grant(Privilege)





grant
public GrantOnStep grant(Privilege... privileges)
Description copied from interface: DSLContext
The GRANT statement.

Specified by:
grant in interface DSLContext
See Also:
DSL.grant(Privilege...)





grant
public GrantOnStep grant(Collection<? extends Privilege> privileges)
Description copied from interface: DSLContext
The GRANT statement.

Specified by:
grant in interface DSLContext
See Also:
DSL.grant(Collection)





revoke
public RevokeOnStep revoke(Privilege privileges)
Description copied from interface: DSLContext
The REVOKE statement.

Specified by:
revoke in interface DSLContext
See Also:
DSL.revoke(Privilege)





revoke
public RevokeOnStep revoke(Privilege... privileges)
Description copied from interface: DSLContext
The REVOKE statement.

Specified by:
revoke in interface DSLContext
See Also:
DSL.revoke(Privilege...)





revoke
public RevokeOnStep revoke(Collection<? extends Privilege> privileges)
Description copied from interface: DSLContext
The REVOKE statement.

Specified by:
revoke in interface DSLContext
See Also:
DSL.revoke(Collection)





revokeGrantOptionFor
public RevokeOnStep revokeGrantOptionFor(Privilege privileges)
Description copied from interface: DSLContext
The REVOKE GRANT OPTION FOR statement.

Specified by:
revokeGrantOptionFor in interface DSLContext
See Also:
DSL.revokeGrantOptionFor(Privilege)





revokeGrantOptionFor
public RevokeOnStep revokeGrantOptionFor(Privilege... privileges)
Description copied from interface: DSLContext
The REVOKE GRANT OPTION FOR statement.

Specified by:
revokeGrantOptionFor in interface DSLContext
See Also:
DSL.revokeGrantOptionFor(Privilege...)





revokeGrantOptionFor
public RevokeOnStep revokeGrantOptionFor(Collection<? extends Privilege> privileges)
Description copied from interface: DSLContext
The REVOKE GRANT OPTION FOR statement.

Specified by:
revokeGrantOptionFor in interface DSLContext
See Also:
DSL.revokeGrantOptionFor(Collection)





set
public RowCountQuery set(Name name,
 Param<?> value)
Description copied from interface: DSLContext
The SET statement.
 
 Set a vendor specific session configuration to a new value.

Specified by:
set in interface DSLContext
See Also:
DSL.set(Name, Param)





setLocal
public RowCountQuery setLocal(Name name,
 Param<?> value)
Description copied from interface: DSLContext
The SET LOCAL statement.
 
 Set a vendor specific transaction-local configuration to a new value.

Specified by:
setLocal in interface DSLContext
See Also:
DSL.setLocal(Name, Param)





setCatalog
public RowCountQuery setCatalog(@Name
 String catalog)
Description copied from interface: DSLContext
The SET CATALOG statement.
 
 Set the current catalog to a new value.

Specified by:
setCatalog in interface DSLContext
See Also:
DSL.setCatalog(String)





setCatalog
public RowCountQuery setCatalog(Name catalog)
Description copied from interface: DSLContext
The SET CATALOG statement.
 
 Set the current catalog to a new value.

Specified by:
setCatalog in interface DSLContext
See Also:
DSL.setCatalog(Name)





setCatalog
public RowCountQuery setCatalog(Catalog catalog)
Description copied from interface: DSLContext
The SET CATALOG statement.
 
 Set the current catalog to a new value.

Specified by:
setCatalog in interface DSLContext
See Also:
DSL.setCatalog(Catalog)





setSchema
public RowCountQuery setSchema(@Name
 String schema)
Description copied from interface: DSLContext
The SET SCHEMA statement.
 
 Set the current schema to a new value.

Specified by:
setSchema in interface DSLContext
See Also:
DSL.setSchema(String)





setSchema
public RowCountQuery setSchema(Name schema)
Description copied from interface: DSLContext
The SET SCHEMA statement.
 
 Set the current schema to a new value.

Specified by:
setSchema in interface DSLContext
See Also:
DSL.setSchema(Name)





setSchema
public RowCountQuery setSchema(Schema schema)
Description copied from interface: DSLContext
The SET SCHEMA statement.
 
 Set the current schema to a new value.

Specified by:
setSchema in interface DSLContext
See Also:
DSL.setSchema(Schema)





truncate
public TruncateIdentityStep<Record> truncate(@Name
 String table)
Description copied from interface: DSLContext
The TRUNCATE statement.

Specified by:
truncate in interface DSLContext
See Also:
DSL.truncate(String)





truncate
public TruncateIdentityStep<Record> truncate(Name table)
Description copied from interface: DSLContext
The TRUNCATE statement.

Specified by:
truncate in interface DSLContext
See Also:
DSL.truncate(Name)





truncate
public <R extends Record> TruncateIdentityStep<R> truncate(Table<R> table)
Description copied from interface: DSLContext
The TRUNCATE statement.

Specified by:
truncate in interface DSLContext
See Also:
DSL.truncate(Table)





truncateTable
public TruncateIdentityStep<Record> truncateTable(@Name
 String table)
Description copied from interface: DSLContext
The TRUNCATE TABLE statement.

Specified by:
truncateTable in interface DSLContext
See Also:
DSL.truncateTable(String)





truncateTable
public TruncateIdentityStep<Record> truncateTable(Name table)
Description copied from interface: DSLContext
The TRUNCATE TABLE statement.

Specified by:
truncateTable in interface DSLContext
See Also:
DSL.truncateTable(Name)





truncateTable
public <R extends Record> TruncateIdentityStep<R> truncateTable(Table<R> table)
Description copied from interface: DSLContext
The TRUNCATE TABLE statement.

Specified by:
truncateTable in interface DSLContext
See Also:
DSL.truncateTable(Table)





call
@Pro
public CallArgsStep call(@Name
 String procedure)
Description copied from interface: DSLContext
The CALL statement.
 
 Call a stored procedure.

Specified by:
call in interface DSLContext
See Also:
DSL.call(String)





call
@Pro
public CallArgsStep call(Name procedure)
Description copied from interface: DSLContext
The CALL statement.
 
 Call a stored procedure.

Specified by:
call in interface DSLContext
See Also:
DSL.call(Name)





ddl
public Queries ddl(Catalog catalog)
Description copied from interface: DSLContext
Convenience method for Meta.ddl().

Specified by:
ddl in interface DSLContext
See Also:
DSLContext.meta(Catalog...), 
Meta.ddl()





ddl
public Queries ddl(Catalog catalog,
 DDLFlag... flags)
Description copied from interface: DSLContext
Convenience method for Meta.ddl(DDLExportConfiguration).

Specified by:
ddl in interface DSLContext
See Also:
DSLContext.meta(Catalog...), 
Meta.ddl(DDLExportConfiguration)





ddl
public Queries ddl(Catalog catalog,
 DDLExportConfiguration exportConfiguration)
Description copied from interface: DSLContext
Convenience method for Meta.ddl(DDLExportConfiguration).

Specified by:
ddl in interface DSLContext
See Also:
DSLContext.meta(Catalog...), 
Meta.ddl(DDLExportConfiguration)





ddl
public Queries ddl(Schema schema)
Description copied from interface: DSLContext
Convenience method for Meta.ddl().

Specified by:
ddl in interface DSLContext
See Also:
DSLContext.meta(Schema...), 
Meta.ddl()





ddl
public Queries ddl(Schema schema,
 DDLFlag... flags)
Description copied from interface: DSLContext
Convenience method for Meta.ddl(DDLExportConfiguration).

Specified by:
ddl in interface DSLContext
See Also:
DSLContext.meta(Schema...), 
Meta.ddl(DDLExportConfiguration)





ddl
public Queries ddl(Schema schema,
 DDLExportConfiguration exportConfiguration)
Description copied from interface: DSLContext
Convenience method for Meta.ddl(DDLExportConfiguration).

Specified by:
ddl in interface DSLContext
See Also:
DSLContext.meta(Schema...), 
Meta.ddl(DDLExportConfiguration)





ddl
public Queries ddl(Table<?> table)
Description copied from interface: DSLContext
Convenience method for Meta.ddl().

Specified by:
ddl in interface DSLContext
See Also:
DSLContext.meta(Table...), 
Meta.ddl()





ddl
public Queries ddl(Table<?> table,
 DDLFlag... flags)
Description copied from interface: DSLContext
Convenience method for Meta.ddl(DDLExportConfiguration).

Specified by:
ddl in interface DSLContext
See Also:
DSLContext.meta(Table...), 
Meta.ddl(DDLExportConfiguration)





ddl
public Queries ddl(Table<?> table,
 DDLExportConfiguration exportConfiguration)
Description copied from interface: DSLContext
Convenience method for Meta.ddl(DDLExportConfiguration).

Specified by:
ddl in interface DSLContext
See Also:
DSLContext.meta(Table...), 
Meta.ddl(DDLExportConfiguration)





ddl
public Queries ddl(Table... tables)
Description copied from interface: DSLContext
Convenience method for Meta.ddl().

Specified by:
ddl in interface DSLContext
See Also:
DSLContext.meta(Table...), 
Meta.ddl()





ddl
public Queries ddl(Table[] tables,
 DDLFlag... flags)
Description copied from interface: DSLContext
Convenience method for Meta.ddl(DDLExportConfiguration).

Specified by:
ddl in interface DSLContext
See Also:
DSLContext.meta(Table...), 
Meta.ddl(DDLExportConfiguration)





ddl
public Queries ddl(Table[] tables,
 DDLExportConfiguration exportConfiguration)
Description copied from interface: DSLContext
Convenience method for Meta.ddl(DDLExportConfiguration).

Specified by:
ddl in interface DSLContext
See Also:
DSLContext.meta(Table...), 
Meta.ddl(DDLExportConfiguration)





ddl
public Queries ddl(Collection<? extends Table<?>> tables)
Description copied from interface: DSLContext
Convenience method for Meta.ddl().

Specified by:
ddl in interface DSLContext
See Also:
DSLContext.meta(Table...), 
Meta.ddl()





ddl
public Queries ddl(Collection<? extends Table<?>> tables,
 DDLFlag... flags)
Description copied from interface: DSLContext
Convenience method for Meta.ddl(DDLExportConfiguration).

Specified by:
ddl in interface DSLContext
See Also:
DSLContext.meta(Table...), 
Meta.ddl(DDLExportConfiguration)





ddl
public Queries ddl(Collection<? extends Table<?>> tables,
 DDLExportConfiguration exportConfiguration)
Description copied from interface: DSLContext
Convenience method for Meta.ddl(DDLExportConfiguration).

Specified by:
ddl in interface DSLContext
See Also:
DSLContext.meta(Table...), 
Meta.ddl(DDLExportConfiguration)





createView
public CreateViewAsStep<Record> createView(String view,
 String... fields)
Description copied from interface: DSLContext
Create a new DSL CREATE VIEW statement.

Specified by:
createView in interface DSLContext
See Also:
DSL.createView(String, String...)





createView
public CreateViewAsStep<Record> createView(Name view,
 Name... fields)
Description copied from interface: DSLContext
Create a new DSL CREATE VIEW statement.

Specified by:
createView in interface DSLContext
See Also:
DSL.createView(Name, Name...)





createView
public CreateViewAsStep<Record> createView(Table<?> view,
 Field<?>... fields)
Description copied from interface: DSLContext
Create a new DSL CREATE VIEW statement.

Specified by:
createView in interface DSLContext
See Also:
DSL.createView(Table, Field...)





createView
public CreateViewAsStep<Record> createView(String view,
 Function<? super Field<?>,? extends String> fieldNameFunction)
Description copied from interface: DSLContext
Create a new DSL CREATE VIEW statement.
 
 This works like DSLContext.createView(String, String...) except that the
 view's field names are derived from the view's Select statement
 using a function.

Specified by:
createView in interface DSLContext
See Also:
DSL.createView(String, String...)





createView
public CreateViewAsStep<Record> createView(String view,
 BiFunction<? super Field<?>,? super Integer,? extends String> fieldNameFunction)
Description copied from interface: DSLContext
Create a new DSL CREATE VIEW statement.
 
 This works like DSLContext.createView(String, String...) except that the
 view's field names are derived from the view's Select statement
 using a function.

Specified by:
createView in interface DSLContext
See Also:
DSL.createView(String, String...)





createView
public CreateViewAsStep<Record> createView(Name view,
 Function<? super Field<?>,? extends Name> fieldNameFunction)
Description copied from interface: DSLContext
Create a new DSL CREATE VIEW statement.
 
 This works like DSLContext.createView(Name, Name...) except that the
 view's field names are derived from the view's Select statement
 using a function.

Specified by:
createView in interface DSLContext
See Also:
DSL.createView(String, String...)





createView
public CreateViewAsStep<Record> createView(Name view,
 BiFunction<? super Field<?>,? super Integer,? extends Name> fieldNameFunction)
Description copied from interface: DSLContext
Create a new DSL CREATE VIEW statement.
 
 This works like DSLContext.createView(Name, Name...) except that the
 view's field names are derived from the view's Select statement
 using a function.

Specified by:
createView in interface DSLContext
See Also:
DSL.createView(String, String...)





createView
public CreateViewAsStep<Record> createView(Table<?> view,
 Function<? super Field<?>,? extends Field<?>> fieldNameFunction)
Description copied from interface: DSLContext
Create a new DSL CREATE VIEW statement.
 
 This works like DSLContext.createView(Table, Field...) except that the
 view's field names are derived from the view's Select statement
 using a function.

Specified by:
createView in interface DSLContext
See Also:
DSL.createView(String, String...)





createView
public CreateViewAsStep<Record> createView(Table<?> view,
 BiFunction<? super Field<?>,? super Integer,? extends Field<?>> fieldNameFunction)
Description copied from interface: DSLContext
Create a new DSL CREATE VIEW statement.
 
 This works like DSLContext.createView(Table, Field...) except that the
 view's field names are derived from the view's Select statement
 using a function.

Specified by:
createView in interface DSLContext
See Also:
DSL.createView(String, String...)





createOrReplaceView
public CreateViewAsStep<Record> createOrReplaceView(String view,
 String... fields)
Description copied from interface: DSLContext
Create a new DSL CREATE OR REPLACE VIEW statement.

Specified by:
createOrReplaceView in interface DSLContext
See Also:
DSL.createOrReplaceView(String, String...)





createOrReplaceView
public CreateViewAsStep<Record> createOrReplaceView(Name view,
 Name... fields)
Description copied from interface: DSLContext
Create a new DSL CREATE OR REPLACE VIEW statement.

Specified by:
createOrReplaceView in interface DSLContext
See Also:
DSL.createOrReplaceView(Name, Name...)





createOrReplaceView
public CreateViewAsStep<Record> createOrReplaceView(Table<?> view,
 Field<?>... fields)
Description copied from interface: DSLContext
Create a new DSL CREATE OR REPLACE VIEW statement.

Specified by:
createOrReplaceView in interface DSLContext
See Also:
DSL.createOrReplaceView(Table, Field...)





createOrReplaceView
public CreateViewAsStep<Record> createOrReplaceView(String view,
 Function<? super Field<?>,? extends String> fieldNameFunction)
Description copied from interface: DSLContext
Create a new DSL CREATE OR REPLACE VIEW statement.
 
 This works like DSLContext.createOrReplaceView(String, String...) except that the
 view's field names are derived from the view's Select statement
 using a function.

Specified by:
createOrReplaceView in interface DSLContext
See Also:
DSL.createOrReplaceView(String, String...)





createOrReplaceView
public CreateViewAsStep<Record> createOrReplaceView(String view,
 BiFunction<? super Field<?>,? super Integer,? extends String> fieldNameFunction)
Description copied from interface: DSLContext
Create a new DSL CREATE OR REPLACE VIEW statement.
 
 This works like DSLContext.createOrReplaceView(String, String...) except
 that the view's field names are derived from the view's Select
 statement using a function.

Specified by:
createOrReplaceView in interface DSLContext
See Also:
DSL.createOrReplaceView(String, String...)





createOrReplaceView
public CreateViewAsStep<Record> createOrReplaceView(Name view,
 Function<? super Field<?>,? extends Name> fieldNameFunction)
Description copied from interface: DSLContext
Create a new DSL CREATE OR REPLACE VIEW statement.
 
 This works like DSLContext.createOrReplaceView(Name, Name...) except that the
 view's field names are derived from the view's Select statement
 using a function.

Specified by:
createOrReplaceView in interface DSLContext
See Also:
DSL.createOrReplaceView(String, String...)





createOrReplaceView
public CreateViewAsStep<Record> createOrReplaceView(Name view,
 BiFunction<? super Field<?>,? super Integer,? extends Name> fieldNameFunction)
Description copied from interface: DSLContext
Create a new DSL CREATE OR REPLACE VIEW statement.
 
 This works like DSLContext.createOrReplaceView(Name, Name...) except that the
 view's field names are derived from the view's Select statement
 using a function.

Specified by:
createOrReplaceView in interface DSLContext
See Also:
DSL.createOrReplaceView(String, String...)





createOrReplaceView
public CreateViewAsStep<Record> createOrReplaceView(Table<?> view,
 Function<? super Field<?>,? extends Field<?>> fieldNameFunction)
Description copied from interface: DSLContext
Create a new DSL CREATE OR REPLACE VIEW statement.
 
 This works like DSLContext.createOrReplaceView(Table, Field...) except that the
 view's field names are derived from the view's Select statement
 using a function.

Specified by:
createOrReplaceView in interface DSLContext
See Also:
DSL.createOrReplaceView(String, String...)





createOrReplaceView
public CreateViewAsStep<Record> createOrReplaceView(Table<?> view,
 BiFunction<? super Field<?>,? super Integer,? extends Field<?>> fieldNameFunction)
Description copied from interface: DSLContext
Create a new DSL CREATE OR REPLACE VIEW statement.
 
 This works like DSLContext.createOrReplaceView(Table, Field...) except that the
 view's field names are derived from the view's Select statement
 using a function.

Specified by:
createOrReplaceView in interface DSLContext
See Also:
DSL.createOrReplaceView(String, String...)





createViewIfNotExists
public CreateViewAsStep<Record> createViewIfNotExists(String view,
 String... fields)
Description copied from interface: DSLContext
Create a new DSL CREATE VIEW statement.

Specified by:
createViewIfNotExists in interface DSLContext
See Also:
DSL.createViewIfNotExists(String, String...)





createViewIfNotExists
public CreateViewAsStep<Record> createViewIfNotExists(Name view,
 Name... fields)
Description copied from interface: DSLContext
Create a new DSL CREATE VIEW statement.

Specified by:
createViewIfNotExists in interface DSLContext
See Also:
DSL.createViewIfNotExists(Name, Name...)





createViewIfNotExists
public CreateViewAsStep<Record> createViewIfNotExists(Table<?> view,
 Field<?>... fields)
Description copied from interface: DSLContext
Create a new DSL CREATE VIEW statement.

Specified by:
createViewIfNotExists in interface DSLContext
See Also:
DSL.createViewIfNotExists(Table, Field...)





createViewIfNotExists
public CreateViewAsStep<Record> createViewIfNotExists(String view,
 Function<? super Field<?>,? extends String> fieldNameFunction)
Description copied from interface: DSLContext
Create a new DSL CREATE VIEW statement.
 
 This works like DSLContext.createViewIfNotExists(String, String...) except that the
 view's field names are derived from the view's Select statement
 using a function.

Specified by:
createViewIfNotExists in interface DSLContext
See Also:
DSL.createViewIfNotExists(String, String...)





createViewIfNotExists
public CreateViewAsStep<Record> createViewIfNotExists(String view,
 BiFunction<? super Field<?>,? super Integer,? extends String> fieldNameFunction)
Description copied from interface: DSLContext
Create a new DSL CREATE VIEW statement.
 
 This works like DSLContext.createViewIfNotExists(String, String...) except that the
 view's field names are derived from the view's Select statement
 using a function.

Specified by:
createViewIfNotExists in interface DSLContext
See Also:
DSL.createViewIfNotExists(String, String...)





createViewIfNotExists
public CreateViewAsStep<Record> createViewIfNotExists(Name view,
 Function<? super Field<?>,? extends Name> fieldNameFunction)
Description copied from interface: DSLContext
Create a new DSL CREATE VIEW statement.
 
 This works like DSLContext.createViewIfNotExists(Name, Name...) except that the
 view's field names are derived from the view's Select statement
 using a function.

Specified by:
createViewIfNotExists in interface DSLContext
See Also:
DSL.createViewIfNotExists(String, String...)





createViewIfNotExists
public CreateViewAsStep<Record> createViewIfNotExists(Name view,
 BiFunction<? super Field<?>,? super Integer,? extends Name> fieldNameFunction)
Description copied from interface: DSLContext
Create a new DSL CREATE VIEW statement.
 
 This works like DSLContext.createViewIfNotExists(Name, Name...) except that the
 view's field names are derived from the view's Select statement
 using a function.

Specified by:
createViewIfNotExists in interface DSLContext
See Also:
DSL.createViewIfNotExists(String, String...)





createViewIfNotExists
public CreateViewAsStep<Record> createViewIfNotExists(Table<?> view,
 Function<? super Field<?>,? extends Field<?>> fieldNameFunction)
Description copied from interface: DSLContext
Create a new DSL CREATE VIEW statement.
 
 This works like DSLContext.createViewIfNotExists(Table, Field...) except that the
 view's field names are derived from the view's Select statement
 using a function.

Specified by:
createViewIfNotExists in interface DSLContext
See Also:
DSL.createViewIfNotExists(String, String...)





createViewIfNotExists
public CreateViewAsStep<Record> createViewIfNotExists(Table<?> view,
 BiFunction<? super Field<?>,? super Integer,? extends Field<?>> fieldNameFunction)
Description copied from interface: DSLContext
Create a new DSL CREATE VIEW statement.
 
 This works like DSLContext.createViewIfNotExists(Table, Field...) except that the
 view's field names are derived from the view's Select statement
 using a function.

Specified by:
createViewIfNotExists in interface DSLContext
See Also:
DSL.createViewIfNotExists(String, String...)





createTable
public CreateTableColumnStep createTable(String table)
Description copied from interface: DSLContext
Create a new DSL CREATE TABLE statement.

Specified by:
createTable in interface DSLContext
See Also:
DSL.createTable(String)





createTable
public CreateTableColumnStep createTable(Name table)
Description copied from interface: DSLContext
Create a new DSL CREATE TABLE statement.

Specified by:
createTable in interface DSLContext
See Also:
DSL.createTable(Name)





createTable
public CreateTableColumnStep createTable(Table<?> table)
Description copied from interface: DSLContext
Create a new DSL CREATE TABLE statement.

Specified by:
createTable in interface DSLContext
See Also:
DSL.createTable(Table)





createTableIfNotExists
public CreateTableColumnStep createTableIfNotExists(String table)
Description copied from interface: DSLContext
Create a new DSL CREATE TABLE statement.

Specified by:
createTableIfNotExists in interface DSLContext
See Also:
DSL.createTableIfNotExists(String)





createTableIfNotExists
public CreateTableColumnStep createTableIfNotExists(Name table)
Description copied from interface: DSLContext
Create a new DSL CREATE TABLE statement.

Specified by:
createTableIfNotExists in interface DSLContext
See Also:
DSL.createTableIfNotExists(Name)





createTableIfNotExists
public CreateTableColumnStep createTableIfNotExists(Table<?> table)
Description copied from interface: DSLContext
Create a new DSL CREATE TABLE statement.

Specified by:
createTableIfNotExists in interface DSLContext
See Also:
DSL.createTableIfNotExists(Table)





createTemporaryTable
public CreateTableColumnStep createTemporaryTable(String table)
Description copied from interface: DSLContext
Create a new DSL CREATE TEMPORARY TABLE statement.

Specified by:
createTemporaryTable in interface DSLContext
See Also:
DSL.createTemporaryTable(String)





createTemporaryTable
public CreateTableColumnStep createTemporaryTable(Name table)
Description copied from interface: DSLContext
Create a new DSL CREATE TEMPORARY TABLE statement.

Specified by:
createTemporaryTable in interface DSLContext
See Also:
DSL.createTemporaryTable(Name)





createTemporaryTable
public CreateTableColumnStep createTemporaryTable(Table<?> table)
Description copied from interface: DSLContext
Create a new DSL CREATE TEMPORARY TABLE statement.

Specified by:
createTemporaryTable in interface DSLContext
See Also:
DSL.createTemporaryTable(Table)





createTemporaryTableIfNotExists
public CreateTableColumnStep createTemporaryTableIfNotExists(String table)
Description copied from interface: DSLContext
Create a new DSL CREATE TEMPORARY TABLE IF NOT EXISTS statement.

Specified by:
createTemporaryTableIfNotExists in interface DSLContext
See Also:
DSL.createTemporaryTableIfNotExists(String)





createTemporaryTableIfNotExists
public CreateTableColumnStep createTemporaryTableIfNotExists(Name table)
Description copied from interface: DSLContext
Create a new DSL CREATE TEMPORARY TABLE IF NOT EXISTS statement.

Specified by:
createTemporaryTableIfNotExists in interface DSLContext
See Also:
DSL.createTemporaryTableIfNotExists(Name)





createTemporaryTableIfNotExists
public CreateTableColumnStep createTemporaryTableIfNotExists(Table<?> table)
Description copied from interface: DSLContext
Create a new DSL CREATE TEMPORARY TABLE IF NOT EXISTS statement.

Specified by:
createTemporaryTableIfNotExists in interface DSLContext
See Also:
DSL.createTemporaryTableIfNotExists(Table)





createGlobalTemporaryTable
public CreateTableColumnStep createGlobalTemporaryTable(String table)
Description copied from interface: DSLContext
Create a new DSL CREATE GLOBAL TEMPORARY TABLE statement.

Specified by:
createGlobalTemporaryTable in interface DSLContext
See Also:
DSL.createGlobalTemporaryTable(String)





createGlobalTemporaryTable
public CreateTableColumnStep createGlobalTemporaryTable(Name table)
Description copied from interface: DSLContext
Create a new DSL CREATE GLOBAL TEMPORARY TABLE statement.

Specified by:
createGlobalTemporaryTable in interface DSLContext
See Also:
DSL.createGlobalTemporaryTable(Name)





createGlobalTemporaryTable
public CreateTableColumnStep createGlobalTemporaryTable(Table<?> table)
Description copied from interface: DSLContext
Create a new DSL CREATE GLOBAL TEMPORARY TABLE statement.

Specified by:
createGlobalTemporaryTable in interface DSLContext
See Also:
DSL.createGlobalTemporaryTable(Table)





createType
public CreateTypeStep createType(String type)
Description copied from interface: DSLContext
Create a new DSL CREATE TYPE statement.

Specified by:
createType in interface DSLContext
See Also:
DSL.createType(String)





createType
public CreateTypeStep createType(Name type)
Description copied from interface: DSLContext
Create a new DSL CREATE TYPE statement.

Specified by:
createType in interface DSLContext
See Also:
DSL.createType(Name)





dropType
public DropTypeStep dropType(String type)
Description copied from interface: DSLContext
Create a new DSL DROP TYPE statement.

Specified by:
dropType in interface DSLContext
See Also:
DSL.dropType(String)





dropType
public DropTypeStep dropType(Name type)
Description copied from interface: DSLContext
Create a new DSL DROP TYPE statement.

Specified by:
dropType in interface DSLContext
See Also:
DSL.dropType(Name)





dropType
public DropTypeStep dropType(String... type)
Description copied from interface: DSLContext
Create a new DSL DROP TYPE statement.

Specified by:
dropType in interface DSLContext
See Also:
DSL.dropType(String...)





dropType
public DropTypeStep dropType(Name... type)
Description copied from interface: DSLContext
Create a new DSL DROP TYPE statement.

Specified by:
dropType in interface DSLContext
See Also:
DSL.dropType(Name...)





dropType
public DropTypeStep dropType(Collection<?> type)
Description copied from interface: DSLContext
Create a new DSL DROP TYPE statement.

Specified by:
dropType in interface DSLContext
See Also:
DSL.dropType(Collection)





dropTypeIfExists
public DropTypeStep dropTypeIfExists(String type)
Description copied from interface: DSLContext
Create a new DSL DROP TYPE statement.

Specified by:
dropTypeIfExists in interface DSLContext
See Also:
DSL.dropTypeIfExists(String)





dropTypeIfExists
public DropTypeStep dropTypeIfExists(Name type)
Description copied from interface: DSLContext
Create a new DSL DROP TYPE statement.

Specified by:
dropTypeIfExists in interface DSLContext
See Also:
DSL.dropTypeIfExists(Name)





dropTypeIfExists
public DropTypeStep dropTypeIfExists(String... type)
Description copied from interface: DSLContext
Create a new DSL DROP TYPE statement.

Specified by:
dropTypeIfExists in interface DSLContext
See Also:
DSL.dropTypeIfExists(String...)





dropTypeIfExists
public DropTypeStep dropTypeIfExists(Name... type)
Description copied from interface: DSLContext
Create a new DSL DROP TYPE statement.

Specified by:
dropTypeIfExists in interface DSLContext
See Also:
DSL.dropTypeIfExists(Name...)





dropTypeIfExists
public DropTypeStep dropTypeIfExists(Collection<?> type)
Description copied from interface: DSLContext
Create a new DSL DROP TYPE statement.

Specified by:
dropTypeIfExists in interface DSLContext
See Also:
DSL.dropTypeIfExists(Collection)





alterTable
public AlterTableStep alterTable(String table)
Description copied from interface: DSLContext
Create a new DSL ALTER TABLE statement.

Specified by:
alterTable in interface DSLContext
See Also:
DSL.alterTable(String)





alterTable
public AlterTableStep alterTable(Name table)
Description copied from interface: DSLContext
Create a new DSL ALTER TABLE statement.

Specified by:
alterTable in interface DSLContext
See Also:
DSL.alterTable(Name)





alterTable
public AlterTableStep alterTable(Table<?> table)
Description copied from interface: DSLContext
Create a new DSL ALTER TABLE statement.

Specified by:
alterTable in interface DSLContext
See Also:
DSL.alterTable(Table)





alterTableIfExists
public AlterTableStep alterTableIfExists(String table)
Description copied from interface: DSLContext
Create a new DSL ALTER TABLE statement.

Specified by:
alterTableIfExists in interface DSLContext
See Also:
DSL.alterTableIfExists(String)





alterTableIfExists
public AlterTableStep alterTableIfExists(Name table)
Description copied from interface: DSLContext
Create a new DSL ALTER TABLE statement.

Specified by:
alterTableIfExists in interface DSLContext
See Also:
DSL.alterTableIfExists(Name)





alterTableIfExists
public AlterTableStep alterTableIfExists(Table<?> table)
Description copied from interface: DSLContext
Create a new DSL ALTER TABLE statement.

Specified by:
alterTableIfExists in interface DSLContext
See Also:
DSL.alterTableIfExists(Table)





lastID
public BigInteger lastID()
Description copied from interface: DSLContext
Retrieve the last inserted ID.
 
 This is implemented for the following dialects:
 

 SQLDialect.ACCESS: Using @@identity
 SQLDialect.ASE: Using @@identity
 SQLDialect.DERBY: Using identity_val_local()
 SQLDialect.H2: Using identity()
 SQLDialect.HSQLDB: Using identity()
 SQLDialect.INFORMIX: Using
 dbinfo('sqlca.sqlerrd1')
 SQLDialect.INGRES: Using last_identity()
 SQLDialect.MARIADB: Using last_insert_id()
 SQLDialect.MYSQL: Using last_insert_id()
 SQLDialect.POSTGRES: Using lastval()
 SQLDialect.SQLITE: Using last_insert_rowid()
 SQLDialect.SQLSERVER: Using @@identity
 SQLDialect.SYBASE: Using @@identity
 SQLDialect.VERTICA: Using last_insert_id()
 

Specified by:
lastID in interface DSLContext
Returns:
The last inserted ID. This may be null in some
         dialects, if no such number is available.





nextval
public BigInteger nextval(String sequence)
Description copied from interface: DSLContext
Convenience method to fetch the NEXTVAL for a sequence directly from this
 DSLContext's underlying JDBC Connection.

Specified by:
nextval in interface DSLContext





nextval
public BigInteger nextval(Name sequence)
Description copied from interface: DSLContext
Convenience method to fetch the NEXTVAL for a sequence directly from this
 DSLContext's underlying JDBC Connection.

Specified by:
nextval in interface DSLContext





nextval
public <T extends Number> T nextval(Sequence<T> sequence)
Description copied from interface: DSLContext
Convenience method to fetch the NEXTVAL for a sequence directly from this
 DSLContext's underlying JDBC Connection.

Specified by:
nextval in interface DSLContext





nextvals
public <T extends Number> List<T> nextvals(Sequence<T> sequence,
 int size)
Description copied from interface: DSLContext
Convenience method to fetch several NEXTVAL for a sequence directly from
 this DSLContext's underlying JDBC Connection.
 
 This is done using DSL.generateSeries(int, int).

Specified by:
nextvals in interface DSLContext





currval
public BigInteger currval(String sequence)
Description copied from interface: DSLContext
Convenience method to fetch the CURRVAL for a sequence directly from this
 DSLContext's underlying JDBC Connection.

Specified by:
currval in interface DSLContext





currval
public BigInteger currval(Name sequence)
Description copied from interface: DSLContext
Convenience method to fetch the CURRVAL for a sequence directly from this
 DSLContext's underlying JDBC Connection.

Specified by:
currval in interface DSLContext





currval
public <T extends Number> T currval(Sequence<T> sequence)
Description copied from interface: DSLContext
Convenience method to fetch the CURRVAL for a sequence directly from this
 DSLContext's underlying JDBC Connection.

Specified by:
currval in interface DSLContext





newRecord
public Record newRecord(Field<?>... fields)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Parameters:
fields - The fields defining the Record type
Returns:
The new record





newRecord
public Record newRecord(Collection<? extends Field<?>> fields)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Parameters:
fields - The fields defining the Record type
Returns:
The new record





newRecord
public <T1> Record1<T1> newRecord(Field<T1> field1)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Returns:
The new record





newRecord
public <T1,
T2> Record2<T1,T2> newRecord(Field<T1> field1,
 Field<T2> field2)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Returns:
The new record





newRecord
public <T1,
T2,
T3> Record3<T1,T2,T3> newRecord(Field<T1> field1,
 Field<T2> field2,
 Field<T3> field3)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Returns:
The new record





newRecord
public <T1,
T2,
T3,
T4> Record4<T1,T2,T3,T4> newRecord(Field<T1> field1,
 Field<T2> field2,
 Field<T3> field3,
 Field<T4> field4)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Returns:
The new record





newRecord
public <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)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Returns:
The new record





newRecord
public <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)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Returns:
The new record





newRecord
public <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)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Returns:
The new record





newRecord
public <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)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Returns:
The new record





newRecord
public <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)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Returns:
The new record





newRecord
public <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)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Returns:
The new record





newRecord
public <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)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Returns:
The new record





newRecord
public <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)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Returns:
The new record





newRecord
public <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)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Returns:
The new record





newRecord
public <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)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Returns:
The new record





newRecord
public <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)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Returns:
The new record





newRecord
public <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)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Returns:
The new record





newRecord
public <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)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Returns:
The new record





newRecord
public <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)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Returns:
The new record





newRecord
public <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)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Returns:
The new record





newRecord
public <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)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Returns:
The new record





newRecord
public <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)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Returns:
The new record





newRecord
public <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)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Returns:
The new record





newRecord
public <R extends UDTRecord<R>> R newRecord(UDT<R> type)
Description copied from interface: DSLContext
Create a new UDTRecord.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Type Parameters:
R - The generic record type
Parameters:
type - The UDT describing records of type <R>
Returns:
The new record





newRecord
public <R extends Record> R newRecord(Table<R> table)
Description copied from interface: DSLContext
Create a new Record that can be inserted into the corresponding
 table.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Type Parameters:
R - The generic record type
Parameters:
table - The table holding records of type <R>
Returns:
The new record





newRecord
public <R extends Record> R newRecord(Table<R> table,
 Object source)
Description copied from interface: DSLContext
Create a new pre-filled Record that can be inserted into the
 corresponding table.
 
 This is convenience for calling DSLContext.newRecord(Table) and then
 Record.from(Object) on the resulting record. The record unmapping
 implementation is governed by
 Configuration.recordUnmapperProvider().
 

 The resulting record will have its internal "changed" flags set to true
 for all values. This means that UpdatableRecord.store() will
 perform an INSERT statement. If you wish to store the record
 using an UPDATE statement, use
 DSLContext.executeUpdate(UpdatableRecord) instead.
 

 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newRecord in interface DSLContext
Type Parameters:
R - The generic record type
Parameters:
table - The table holding records of type <R>
source - The source to be used to fill the new record
Returns:
The new record
See Also:
Record.from(Object), 
Record.into(Class)





newResult
public <R extends Record> Result<R> newResult(Table<R> table)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The result is attached to this Configuration by default. This
 result can be used as a container for records.

Specified by:
newResult in interface DSLContext
Type Parameters:
R - The generic record type
Parameters:
table - The table holding records of type <R>
Returns:
The new result





newResult
public Result<Record> newResult(Field<?>... fields)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Parameters:
fields - The fields defining the Record type
Returns:
The new record





newResult
public Result<Record> newResult(Collection<? extends Field<?>> fields)
Description copied from interface: DSLContext
Create a new empty Record.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Parameters:
fields - The fields defining the Record type
Returns:
The new record





newResult
public <T1> Result<Record1<T1>> newResult(Field<T1> field1)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The resulting result is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Returns:
The new result





newResult
public <T1,
T2> Result<Record2<T1,T2>> newResult(Field<T1> field1,
 Field<T2> field2)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The resulting result is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Returns:
The new result





newResult
public <T1,
T2,
T3> Result<Record3<T1,T2,T3>> newResult(Field<T1> field1,
 Field<T2> field2,
 Field<T3> field3)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The resulting result is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Returns:
The new result





newResult
public <T1,
T2,
T3,
T4> Result<Record4<T1,T2,T3,T4>> newResult(Field<T1> field1,
 Field<T2> field2,
 Field<T3> field3,
 Field<T4> field4)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The resulting result is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Returns:
The new result





newResult
public <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)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The resulting result is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Returns:
The new result





newResult
public <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)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The resulting result is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Returns:
The new result





newResult
public <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)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The resulting result is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Returns:
The new result





newResult
public <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)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The resulting result is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Returns:
The new result





newResult
public <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)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The resulting result is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Returns:
The new result





newResult
public <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)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The resulting result is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Returns:
The new result





newResult
public <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)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The resulting result is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Returns:
The new result





newResult
public <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)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The resulting result is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Returns:
The new result





newResult
public <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)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The resulting result is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Returns:
The new result





newResult
public <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)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The resulting result is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Returns:
The new result





newResult
public <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)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The resulting result is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Returns:
The new result





newResult
public <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)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The resulting result is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Returns:
The new result





newResult
public <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)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The resulting result is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Returns:
The new result





newResult
public <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)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The resulting result is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Returns:
The new result





newResult
public <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)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The resulting result is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Returns:
The new result





newResult
public <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)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The resulting result is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Returns:
The new result





newResult
public <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)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The resulting result is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Returns:
The new result





newResult
public <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)
Description copied from interface: DSLContext
Create a new empty Result.
 
 The resulting result is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
newResult in interface DSLContext
Returns:
The new result





fetch
public <R extends Record> Result<R> fetch(ResultQuery<R> query)
Description copied from interface: DSLContext
Execute a ResultQuery in the context of this DSLContext and return
 results.

Specified by:
fetch in interface DSLContext
Parameters:
query - The query to execute
Returns:
The result. This will never be null.
See Also:
ResultQuery.fetch()





fetchLazy
public <R extends Record> Cursor<R> fetchLazy(ResultQuery<R> query)
Description copied from interface: DSLContext
Execute a ResultQuery in the context of this
 DSLContext and return a cursor.
 
 Depending on your JDBC driver's default behaviour, this may load the
 whole database result into the driver's memory. In order to indicate to
 the driver that you may not want to fetch all records at once, use
 ResultQuery.fetchSize(int) and run
 ResultQuery.fetchLazy() instead, or specify
 Settings.setFetchSize(Integer) prior to calling this method.
 

 Client code is responsible for closing the cursor after use.

Specified by:
fetchLazy in interface DSLContext
Parameters:
query - The query to execute
Returns:
The cursor. This will never be null.
See Also:
ResultQuery.fetchLazy()





fetchAsync
public <R extends Record>
CompletionStage<Result<R>> fetchAsync(ResultQuery<R> query)
Description copied from interface: DSLContext
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().

Specified by:
fetchAsync in interface DSLContext
Parameters:
query - The query to execute
Returns:
The completion stage. The completed result will never be
         null.
See Also:
ResultQuery.fetchAsync()





fetchAsync
public <R extends Record>
CompletionStage<Result<R>> fetchAsync(Executor executor,
 ResultQuery<R> query)
Description copied from interface: DSLContext
Fetch results in a new CompletionStage that is asynchronously
 completed by a task running in the given executor.

Specified by:
fetchAsync in interface DSLContext
query - The query to execute
Returns:
The completion stage. The completed result will never be
         null.
See Also:
ResultQuery.fetchAsync()





fetchStream
public <R extends Record> Stream<R> fetchStream(ResultQuery<R> query)
Description copied from interface: DSLContext
Execute a ResultQuery in the context of this
 DSLContext and return a stream.
 
 Depending on your JDBC driver's default behaviour, this may load the
 whole database result into the driver's memory. In order to indicate to
 the driver that you may not want to fetch all records at once, use
 ResultQuery.fetchSize(int) and run
 ResultQuery.fetchStream() instead, or specify
 Settings.setFetchSize(Integer) prior to calling this method.
 

 Client code is responsible for closing the stream after use.

Specified by:
fetchStream in interface DSLContext
Parameters:
query - The query to execute
Returns:
The stream
See Also:
ResultQuery.stream()





fetchMany
public <R extends Record> Results fetchMany(ResultQuery<R> query)
Description copied from interface: DSLContext
Execute a ResultQuery in the context of this DSLContext and return
 a cursor.

Specified by:
fetchMany in interface DSLContext
Parameters:
query - The query to execute
Returns:
The results. This will never be null.
See Also:
ResultQuery.fetchMany()





fetchOne
public <R extends Record> R fetchOne(ResultQuery<R> query)
Description copied from interface: DSLContext
Execute a ResultQuery in the context of this DSLContext and return
 a record.

Specified by:
fetchOne in interface DSLContext
Parameters:
query - The query to execute
Returns:
The record or null, if no record was found.
See Also:
ResultQuery.fetchOne()





fetchSingle
public <R extends Record> R fetchSingle(ResultQuery<R> query)
Description copied from interface: DSLContext
Execute a ResultQuery in the context of this DSLContext and return
 a record.

Specified by:
fetchSingle in interface DSLContext
Parameters:
query - The query to execute
Returns:
The record. This is never null.
See Also:
ResultQuery.fetchSingle()





fetchOptional
public <R extends Record> Optional<R> fetchOptional(ResultQuery<R> query)
Description copied from interface: DSLContext
Execute a ResultQuery in the context of this DSLContext and return
 a record.

Specified by:
fetchOptional in interface DSLContext
Parameters:
query - The query to execute
Returns:
The record
See Also:
ResultQuery.fetchOptional()





fetchValue
public <T> T fetchValue(Table<? extends Record1<T>> table)
Description copied from interface: DSLContext
Fetch a single value from a single column table.

Specified by:
fetchValue in interface DSLContext
Parameters:
table - The table from which to fetch a value
Returns:
The value or null, if no record was found.





fetchValue
public <T,
R extends Record1<T>> T fetchValue(ResultQuery<R> query)
Description copied from interface: DSLContext
Execute a ResultQuery in the context of this
 DSLContext and return a single value.

Specified by:
fetchValue in interface DSLContext
Parameters:
query - The query to execute
Returns:
The value or null, if no record was found.





fetchValue
public <T> T fetchValue(TableField<?,T> field)
Description copied from interface: DSLContext
Execute a ResultQuery in the context of this
 DSLContext and return a single value.

Specified by:
fetchValue in interface DSLContext
Parameters:
field - The field for which to fetch a single value.
Returns:
The value or null, if no record was found.





fetchValue
public <T> T fetchValue(SelectField<T> field)
Description copied from interface: DSLContext
Execute a ResultQuery in the context of this
 DSLContext and return a single value.

Specified by:
fetchValue in interface DSLContext
Parameters:
field - The field for which to fetch a single value.
Returns:
The value or null, if no record was found.





fetchOptionalValue
public <T,
R extends Record1<T>> Optional<T> fetchOptionalValue(ResultQuery<R> query)
Description copied from interface: DSLContext
Execute a ResultQuery in the context of this
 DSLContext and return a single value.

Specified by:
fetchOptionalValue in interface DSLContext
Parameters:
query - The query to execute
Returns:
The value.





fetchOptionalValue
public <T> Optional<T> fetchOptionalValue(TableField<?,T> field)
Description copied from interface: DSLContext
Execute a ResultQuery in the context of this
 DSLContext and return a single value.

Specified by:
fetchOptionalValue in interface DSLContext
Parameters:
field - The field for which to fetch a single value.
Returns:
The value.





fetchValues
public <T> List<T> fetchValues(Table<? extends Record1<T>> table)
Description copied from interface: DSLContext
Fetch all values from a single column table.

Specified by:
fetchValues in interface DSLContext
Parameters:
table - The table from which to fetch values
Returns:
The values. This will never be null.





fetchValues
public <T,
R extends Record1<T>> List<T> fetchValues(ResultQuery<R> query)
Description copied from interface: DSLContext
Execute a ResultQuery in the context of this
 DSLContext and return all values for the only column.

Specified by:
fetchValues in interface DSLContext
Parameters:
query - The query to execute
Returns:
The values. This will never be null.





fetchValues
public <T> List<T> fetchValues(TableField<?,T> field)
Description copied from interface: DSLContext
Fetch all values in a given Table's TableField.

Specified by:
fetchValues in interface DSLContext
Parameters:
field - The field for which to fetch all values.
Returns:
The values. This will never be null.





fetchByExample
public <R extends TableRecord<R>> Result<R> fetchByExample(R example)
Description copied from interface: DSLContext
Execute a "Query by Example" (QBE) based on an example record.

Specified by:
fetchByExample in interface DSLContext
Parameters:
example - The example record
Returns:
The resulting records matching the example record.
See Also:
DSL.condition(Record)





fetchCount
public int fetchCount(Select<?> query)
Description copied from interface: DSLContext
Execute a Select query in the context of this DSLContext and return
 a COUNT(*) value.
 
 This wraps a pre-existing SELECT query in another one to
 calculate the COUNT(*) value, without modifying the original
 SELECT. An example: 
 -- Original query:
 SELECT id, title FROM book WHERE title LIKE '%a%'

 -- Wrapped query:
 SELECT count(*) FROM (
   SELECT id, title FROM book WHERE title LIKE '%a%'
 )
  This is particularly useful for those databases that do not
 support the COUNT(*) OVER() window function to calculate
 total results in paged queries.

Specified by:
fetchCount in interface DSLContext
Parameters:
query - The wrapped query
Returns:
The COUNT(*) result





fetchCount
public int fetchCount(Table<?> table)
Description copied from interface: DSLContext
Count the number of records in a table.
 
 This executes 
SELECT COUNT(*) FROM table

Specified by:
fetchCount in interface DSLContext
Parameters:
table - The table whose records to count
Returns:
The number of records in the table





fetchCount
public int fetchCount(Table<?> table,
 Condition condition)
Description copied from interface: DSLContext
Count the number of records in a table that satisfy a condition.
 
 This executes 
SELECT COUNT(*) FROM table WHERE condition

Specified by:
fetchCount in interface DSLContext
Parameters:
table - The table whose records to count
condition - The condition to apply
Returns:
The number of records in the table that satisfy a condition





fetchCount
public int fetchCount(Table<?> table,
 Condition... conditions)
Description copied from interface: DSLContext
Count the number of records in a table that satisfy a condition.
 
 This executes
 
SELECT COUNT(*) FROM table WHERE condition
 
 Convenience API for calling DSLContext.fetchCount(Table, Condition) with
 DSL.and(Condition...).

Specified by:
fetchCount in interface DSLContext
Parameters:
table - The table whose records to count
conditions - The conditions to apply
Returns:
The number of records in the table that satisfy a condition





fetchCount
public int fetchCount(Table<?> table,
 Collection<? extends Condition> conditions)
Description copied from interface: DSLContext
Count the number of records in a table that satisfy a condition.
 
 This executes
 
SELECT COUNT(*) FROM table WHERE condition
 
 Convenience API for calling DSLContext.fetchCount(Table, Condition) with
 DSL.and(Collection).

Specified by:
fetchCount in interface DSLContext
Parameters:
table - The table whose records to count
conditions - The conditions to apply
Returns:
The number of records in the table that satisfy a condition





fetchExists
public boolean fetchExists(Select<?> query)
Description copied from interface: DSLContext
Check if a Select would return any records, if it were executed.
 
 This wraps a pre-existing SELECT query in another one to
 check for result existence, without modifying the original
 SELECT. An example: 
 -- Original query:
 SELECT id, title FROM book WHERE title LIKE '%a%'

 -- Wrapped query:
 SELECT EXISTS (
   SELECT id, title FROM book WHERE title LIKE '%a%'
 )
 

Specified by:
fetchExists in interface DSLContext
Parameters:
query - The wrapped query
Returns:
The EXISTS(...) result





fetchExists
public boolean fetchExists(Table<?> table)
Description copied from interface: DSLContext
Check if a table has any records.
 
 This executes 
SELECT EXISTS(SELECT * FROM table)

Specified by:
fetchExists in interface DSLContext
Parameters:
table - The table whose records to count
Returns:
Whether the table contains any records





fetchExists
public boolean fetchExists(Table<?> table,
 Condition condition)
Description copied from interface: DSLContext
Check if a table has any records that satisfy a condition.
 
 This executes 
SELECT EXISTS(SELECT * FROM table WHERE condition)

Specified by:
fetchExists in interface DSLContext
Parameters:
table - The table whose records to count
Returns:
Whether the table contains any records that satisfy a condition





fetchExists
public boolean fetchExists(Table<?> table,
 Condition... conditions)
Description copied from interface: DSLContext
Check if a table has any records that satisfy a condition.
 
 This executes 
SELECT EXISTS(SELECT * FROM table WHERE condition)
 
 Convenience API for calling DSLContext.fetchExists(Table, Condition) with
 DSL.and(Condition...).

Specified by:
fetchExists in interface DSLContext
Parameters:
table - The table whose records to count
Returns:
Whether the table contains any records that satisfy a condition





fetchExists
public boolean fetchExists(Table<?> table,
 Collection<? extends Condition> conditions)
Description copied from interface: DSLContext
Check if a table has any records that satisfy a condition.
 
 This executes 
SELECT EXISTS(SELECT * FROM table WHERE condition)
 
 Convenience API for calling DSLContext.fetchExists(Table, Condition) with
 DSL.and(Collection).

Specified by:
fetchExists in interface DSLContext
Parameters:
table - The table whose records to count
Returns:
Whether the table contains any records that satisfy a condition





execute
public int execute(Query query)
Description copied from interface: DSLContext
Execute a Query in the context of this DSLContext.

Specified by:
execute in interface DSLContext
Parameters:
query - The query to execute
Returns:
The number of affected rows
See Also:
Query.execute()





fetch
public <R extends Record> Result<R> fetch(Table<R> table)
Description copied from interface: DSLContext
Execute and return all records for
 SELECT table.col1, table.col2 FROM table.
 
 The result and its contained records are attached to this
 Configuration by default. Use Settings.isAttachRecords()
 to override this behaviour.

Specified by:
fetch in interface DSLContext
Returns:
The results from the executed query. This will never be
         null.





fetch
public <R extends Record> Result<R> fetch(Table<R> table,
 Condition condition)
Description copied from interface: DSLContext
Execute and return all records for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The result and its contained records are attached to this
 Configuration by default. Use Settings.isAttachRecords()
 to override this behaviour.

Specified by:
fetch in interface DSLContext
Returns:
The results from the executed query. This will never be
         null.





fetch
public <R extends Record> Result<R> fetch(Table<R> table,
 Condition... conditions)
Description copied from interface: DSLContext
Execute and return all records for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The result and its contained records are attached to this
 Configuration by default. Use Settings.isAttachRecords()
 to override this behaviour.
 

 Convenience API for calling DSLContext.fetch(Table, Condition) with
 DSL.and(Condition...).

Specified by:
fetch in interface DSLContext
Returns:
The results from the executed query. This will never be
         null.





fetch
public <R extends Record> Result<R> fetch(Table<R> table,
 Collection<? extends Condition> conditions)
Description copied from interface: DSLContext
Execute and return all records for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The result and its contained records are attached to this
 Configuration by default. Use Settings.isAttachRecords()
 to override this behaviour.
 

 Convenience API for calling DSLContext.fetch(Table, Condition) with
 DSL.and(Collection).

Specified by:
fetch in interface DSLContext
Returns:
The results from the executed query. This will never be
         null.





fetchOne
public <R extends Record> R fetchOne(Table<R> table)
Description copied from interface: DSLContext
Execute and return zero or one record for
 SELECT table.col1, table.col2 FROM table.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
fetchOne in interface DSLContext
Returns:
The record or null, if no record was found.





fetchOne
public <R extends Record> R fetchOne(Table<R> table,
 Condition condition)
Description copied from interface: DSLContext
Execute and return zero or one record for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
fetchOne in interface DSLContext
Returns:
The record or null, if no record was found.





fetchOne
public <R extends Record> R fetchOne(Table<R> table,
 Condition... conditions)
Description copied from interface: DSLContext
Execute and return zero or one record for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchOne(Table, Condition) with
 DSL.and(Condition...).

Specified by:
fetchOne in interface DSLContext
Returns:
The record or null, if no record was found.





fetchOne
public <R extends Record> R fetchOne(Table<R> table,
 Collection<? extends Condition> conditions)
Description copied from interface: DSLContext
Execute and return zero or one record for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchOne(Table, Condition) with
 DSL.and(Collection).

Specified by:
fetchOne in interface DSLContext
Returns:
The record or null, if no record was found.





fetchSingle
public <R extends Record> R fetchSingle(Table<R> table)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT table.col1, table.col2 FROM table.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <R extends Record> R fetchSingle(Table<R> table,
 Condition condition)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <R extends Record> R fetchSingle(Table<R> table,
 Condition... conditions)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(Table, Condition) with
 DSL.and(Condition...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <R extends Record> R fetchSingle(Table<R> table,
 Collection<? extends Condition> conditions)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(Table, Condition) with
 DSL.and(Collection).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public Record fetchSingle(SelectField<?>... fields)
                   throws DataAccessException
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.
Throws:
DataAccessException - if something went wrong executing the query





fetchSingle
public Record fetchSingle(Collection<? extends SelectField<?>> fields)
                   throws DataAccessException
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.
Throws:
DataAccessException - if something went wrong executing the query





fetchSingle
public <T1> Record1<T1> fetchSingle(SelectField<T1> field1)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <T1,
T2> Record2<T1,T2> fetchSingle(SelectField<T1> field1,
 SelectField<T2> field2)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <T1,
T2,
T3> Record3<T1,T2,T3> fetchSingle(SelectField<T1> field1,
 SelectField<T2> field2,
 SelectField<T3> field3)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <T1,
T2,
T3,
T4> Record4<T1,T2,T3,T4> fetchSingle(SelectField<T1> field1,
 SelectField<T2> field2,
 SelectField<T3> field3,
 SelectField<T4> field4)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <T1,
T2,
T3,
T4,
T5> Record5<T1,T2,T3,T4,T5> fetchSingle(SelectField<T1> field1,
 SelectField<T2> field2,
 SelectField<T3> field3,
 SelectField<T4> field4,
 SelectField<T5> field5)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <T1,
T2,
T3,
T4,
T5,
T6>
Record6<T1,T2,T3,T4,T5,T6> fetchSingle(SelectField<T1> field1,
 SelectField<T2> field2,
 SelectField<T3> field3,
 SelectField<T4> field4,
 SelectField<T5> field5,
 SelectField<T6> field6)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <T1,
T2,
T3,
T4,
T5,
T6,
T7>
Record7<T1,T2,T3,T4,T5,T6,T7> fetchSingle(SelectField<T1> field1,
 SelectField<T2> field2,
 SelectField<T3> field3,
 SelectField<T4> field4,
 SelectField<T5> field5,
 SelectField<T6> field6,
 SelectField<T7> field7)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <T1,
T2,
T3,
T4,
T5,
T6,
T7,
T8>
Record8<T1,T2,T3,T4,T5,T6,T7,T8> fetchSingle(SelectField<T1> field1,
 SelectField<T2> field2,
 SelectField<T3> field3,
 SelectField<T4> field4,
 SelectField<T5> field5,
 SelectField<T6> field6,
 SelectField<T7> field7,
 SelectField<T8> field8)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <T1,
T2,
T3,
T4,
T5,
T6,
T7,
T8,
T9>
Record9<T1,T2,T3,T4,T5,T6,T7,T8,T9> fetchSingle(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)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <T1,
T2,
T3,
T4,
T5,
T6,
T7,
T8,
T9,
T10>
Record10<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10> fetchSingle(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)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <T1,
T2,
T3,
T4,
T5,
T6,
T7,
T8,
T9,
T10,
T11>
Record11<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11> fetchSingle(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)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <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> fetchSingle(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)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <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> fetchSingle(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)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <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> fetchSingle(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)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <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> fetchSingle(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)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <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> fetchSingle(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)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <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> fetchSingle(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)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <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> fetchSingle(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)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <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> fetchSingle(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)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <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> fetchSingle(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)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <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> fetchSingle(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)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchSingle
public <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> fetchSingle(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)
Description copied from interface: DSLContext
Execute and return exactly one record for
 SELECT F1, F2, ..., FN.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchSingle(ResultQuery) with
 DSL.select(SelectFieldOrAsterisk...).

Specified by:
fetchSingle in interface DSLContext
Returns:
The record. This is never null.





fetchOptional
public <R extends Record> Optional<R> fetchOptional(Table<R> table)
Description copied from interface: DSLContext
Execute and return zero or one record for
 SELECT table.col1, table.col2 FROM table.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
fetchOptional in interface DSLContext
Returns:
The record





fetchOptional
public <R extends Record> Optional<R> fetchOptional(Table<R> table,
 Condition condition)
Description copied from interface: DSLContext
Execute and return zero or one record for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
fetchOptional in interface DSLContext
Returns:
The record





fetchOptional
public <R extends Record> Optional<R> fetchOptional(Table<R> table,
 Condition... conditions)
Description copied from interface: DSLContext
Execute and return zero or one record for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchOptional(Table, Condition) with
 DSL.and(Condition...).

Specified by:
fetchOptional in interface DSLContext
Returns:
The record





fetchOptional
public <R extends Record> Optional<R> fetchOptional(Table<R> table,
 Collection<? extends Condition> conditions)
Description copied from interface: DSLContext
Execute and return zero or one record for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchOptional(Table, Condition) with
 DSL.and(Collection).

Specified by:
fetchOptional in interface DSLContext
Returns:
The record





fetchAny
public <R extends Record> R fetchAny(Table<R> table)
Description copied from interface: DSLContext
Execute and return zero or one record for
 SELECT table.col1, table.col2 FROM table LIMIT 1.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
fetchAny in interface DSLContext
Returns:
The record or null if no record was returned





fetchAny
public <R extends Record> R fetchAny(Table<R> table,
 Condition condition)
Description copied from interface: DSLContext
Execute and return zero or one record for
 SELECT table.col1, table.col2 FROM table WHERE condition LIMIT 1.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.

Specified by:
fetchAny in interface DSLContext
Returns:
The record or null if no record was returned





fetchAny
public <R extends Record> R fetchAny(Table<R> table,
 Condition... conditions)
Description copied from interface: DSLContext
Execute and return zero or on e record for
 SELECT table.col1, table.col2 FROM table WHERE condition LIMIT 1.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchAny(Table, Condition) with
 DSL.and(Condition...).

Specified by:
fetchAny in interface DSLContext
Returns:
The record or null if no record was returned





fetchAny
public <R extends Record> R fetchAny(Table<R> table,
 Collection<? extends Condition> conditions)
Description copied from interface: DSLContext
Execute and return zero or one record for
 SELECT table.col1, table.col2 FROM table WHERE condition LIMIT 1.
 
 The resulting record is attached to this Configuration by
 default. Use Settings.isAttachRecords() to override this
 behaviour.
 

 Convenience API for calling DSLContext.fetchAny(Table, Condition) with
 DSL.and(Collection).

Specified by:
fetchAny in interface DSLContext
Returns:
The record or null if no record was returned





fetchLazy
public <R extends Record> Cursor<R> fetchLazy(Table<R> table)
Description copied from interface: DSLContext
Execute and return all records lazily for
 SELECT table.col1, table.col2 FROM table.
 
 The result and its contained records are attached to this
 Configuration by default. Use Settings.isAttachRecords()
 to override this behaviour.
 

 Depending on your JDBC driver's default behaviour, this may load the
 whole database result into the driver's memory. In order to indicate to
 the driver that you may not want to fetch all records at once, use
 ResultQuery.fetchSize(int) and run
 ResultQuery.fetchLazy() instead, or specify
 Settings.setFetchSize(Integer) prior to calling this method.
 

 Client code is responsible for closing the cursor after use.

Specified by:
fetchLazy in interface DSLContext
Returns:
The cursor. This will never be null.





fetchLazy
public <R extends Record> Cursor<R> fetchLazy(Table<R> table,
 Condition condition)
Description copied from interface: DSLContext
Execute and return all records lazily for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The result and its contained records are attached to this
 Configuration by default. Use Settings.isAttachRecords()
 to override this behaviour.
 

 Depending on your JDBC driver's default behaviour, this may load the
 whole database result into the driver's memory. In order to indicate to
 the driver that you may not want to fetch all records at once, use
 ResultQuery.fetchSize(int) and run
 ResultQuery.fetchLazy() instead, or specify
 Settings.setFetchSize(Integer) prior to calling this method.
 

 Client code is responsible for closing the cursor after use.

Specified by:
fetchLazy in interface DSLContext
Returns:
The cursor. This will never be null.





fetchLazy
public <R extends Record> Cursor<R> fetchLazy(Table<R> table,
 Condition... conditions)
Description copied from interface: DSLContext
Execute and return all records lazily for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The result and its contained records are attached to this
 Configuration by default. Use Settings.isAttachRecords()
 to override this behaviour.
 

 Convenience API for calling DSLContext.fetchLazy(Table, Condition) with
 DSL.and(Condition...).
 

 Depending on your JDBC driver's default behaviour, this may load the
 whole database result into the driver's memory. In order to indicate to
 the driver that you may not want to fetch all records at once, use
 ResultQuery.fetchSize(int) and run
 ResultQuery.fetchLazy() instead, or specify
 Settings.setFetchSize(Integer) prior to calling this method.
 

 Client code is responsible for closing the cursor after use.

Specified by:
fetchLazy in interface DSLContext
Returns:
The cursor. This will never be null.





fetchLazy
public <R extends Record> Cursor<R> fetchLazy(Table<R> table,
 Collection<? extends Condition> conditions)
Description copied from interface: DSLContext
Execute and return all records lazily for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The result and its contained records are attached to this
 Configuration by default. Use Settings.isAttachRecords()
 to override this behaviour.
 

 Convenience API for calling DSLContext.fetchLazy(Table, Condition) with
 DSL.and(Collection).
 

 Depending on your JDBC driver's default behaviour, this may load the
 whole database result into the driver's memory. In order to indicate to
 the driver that you may not want to fetch all records at once, use
 ResultQuery.fetchSize(int) and run
 ResultQuery.fetchLazy() instead, or specify
 Settings.setFetchSize(Integer) prior to calling this method.
 

 Client code is responsible for closing the cursor after use.

Specified by:
fetchLazy in interface DSLContext
Returns:
The cursor. This will never be null.





fetchAsync
public <R extends Record>
CompletionStage<Result<R>> fetchAsync(Table<R> table)
Description copied from interface: DSLContext
Execute and return all records asynchronously for
 SELECT table.col1, table.col2 FROM table.
 
 The result and its contained records are attached to this
 Configuration by default. Use Settings.isAttachRecords()
 to override this behaviour.

Specified by:
fetchAsync in interface DSLContext
Returns:
The completion stage. The completed result will never be
         null.





fetchAsync
public <R extends Record>
CompletionStage<Result<R>> fetchAsync(Table<R> table,
 Condition condition)
Description copied from interface: DSLContext
Execute and return all records asynchronously for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The result and its contained records are attached to this
 Configuration by default. Use Settings.isAttachRecords()
 to override this behaviour.

Specified by:
fetchAsync in interface DSLContext
Returns:
The completion stage. The completed result will never be
         null.





fetchAsync
public <R extends Record>
CompletionStage<Result<R>> fetchAsync(Table<R> table,
 Condition... conditions)
Description copied from interface: DSLContext
Execute and return all records asynchronously for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The result and its contained records are attached to this
 Configuration by default. Use Settings.isAttachRecords()
 to override this behaviour.
 

 Convenience API for calling DSLContext.fetchAsync(Table, Condition) with
 DSL.and(Condition...).

Specified by:
fetchAsync in interface DSLContext
Returns:
The completion stage. The completed result will never be
         null.





fetchAsync
public <R extends Record>
CompletionStage<Result<R>> fetchAsync(Table<R> table,
 Collection<? extends Condition> conditions)
Description copied from interface: DSLContext
Execute and return all records asynchronously for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The result and its contained records are attached to this
 Configuration by default. Use Settings.isAttachRecords()
 to override this behaviour.
 

 Convenience API for calling DSLContext.fetchAsync(Table, Condition) with
 DSL.and(Collection).

Specified by:
fetchAsync in interface DSLContext
Returns:
The completion stage. The completed result will never be
         null.





fetchAsync
public <R extends Record>
CompletionStage<Result<R>> fetchAsync(Executor executor,
 Table<R> table)
Description copied from interface: DSLContext
Execute and return all records asynchronously for
 SELECT table.col1, table.col2 FROM table.
 
 The result and its contained records are attached to this
 Configuration by default. Use Settings.isAttachRecords()
 to override this behaviour.

Specified by:
fetchAsync in interface DSLContext
Returns:
The completion stage. The completed result will never be
         null.





fetchAsync
public <R extends Record>
CompletionStage<Result<R>> fetchAsync(Executor executor,
 Table<R> table,
 Condition condition)
Description copied from interface: DSLContext
Execute and return all records asynchronously for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The result and its contained records are attached to this
 Configuration by default. Use Settings.isAttachRecords()
 to override this behaviour.

Specified by:
fetchAsync in interface DSLContext
Returns:
The completion stage. The completed result will never be
         null.





fetchAsync
public <R extends Record>
CompletionStage<Result<R>> fetchAsync(Executor executor,
 Table<R> table,
 Condition... conditions)
Description copied from interface: DSLContext
Execute and return all records asynchronously for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The result and its contained records are attached to this
 Configuration by default. Use Settings.isAttachRecords()
 to override this behaviour.
 

 Convenience API for calling DSLContext.fetchAsync(Executor, Table, Condition) with
 DSL.and(Condition...).

Specified by:
fetchAsync in interface DSLContext
Returns:
The completion stage. The completed result will never be
         null.





fetchAsync
public <R extends Record>
CompletionStage<Result<R>> fetchAsync(Executor executor,
 Table<R> table,
 Collection<? extends Condition> conditions)
Description copied from interface: DSLContext
Execute and return all records asynchronously for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The result and its contained records are attached to this
 Configuration by default. Use Settings.isAttachRecords()
 to override this behaviour.
 

 Convenience API for calling DSLContext.fetchAsync(Executor, Table, Condition) with
 DSL.and(Collection).

Specified by:
fetchAsync in interface DSLContext
Returns:
The completion stage. The completed result will never be
         null.





fetchStream
public <R extends Record> Stream<R> fetchStream(Table<R> table)
Description copied from interface: DSLContext
Execute and return all records lazily for
 SELECT table.col1, table.col2 FROM table.
 
 The result and its contained records are attached to this
 Configuration by default. Use Settings.isAttachRecords()
 to override this behaviour.
 

 Depending on your JDBC driver's default behaviour, this may load the
 whole database result into the driver's memory. In order to indicate to
 the driver that you may not want to fetch all records at once, use
 ResultQuery.fetchSize(int) and run
 ResultQuery.fetchStream() instead, or specify
 Settings.setFetchSize(Integer) prior to calling this method.
 

 Client code is responsible for closing the stream after use.

Specified by:
fetchStream in interface DSLContext





fetchStream
public <R extends Record> Stream<R> fetchStream(Table<R> table,
 Condition condition)
Description copied from interface: DSLContext
Execute and return all records lazily for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The result and its contained records are attached to this
 Configuration by default. Use Settings.isAttachRecords()
 to override this behaviour.
 

 Depending on your JDBC driver's default behaviour, this may load the
 whole database result into the driver's memory. In order to indicate to
 the driver that you may not want to fetch all records at once, use
 ResultQuery.fetchSize(int) and run
 ResultQuery.fetchStream() instead, or specify
 Settings.setFetchSize(Integer) prior to calling this method.
 

 Client code is responsible for closing the stream after use.

Specified by:
fetchStream in interface DSLContext





fetchStream
public <R extends Record> Stream<R> fetchStream(Table<R> table,
 Condition... conditions)
Description copied from interface: DSLContext
Execute and return all records lazily for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The result and its contained records are attached to this
 Configuration by default. Use Settings.isAttachRecords()
 to override this behaviour.
 

 Convenience API for calling DSLContext.fetchStream(Table, Condition) with
 DSL.and(Condition...).
 

 Depending on your JDBC driver's default behaviour, this may load the
 whole database result into the driver's memory. In order to indicate to
 the driver that you may not want to fetch all records at once, use
 ResultQuery.fetchSize(int) and run
 ResultQuery.fetchStream() instead, or specify
 Settings.setFetchSize(Integer) prior to calling this method.
 

 Client code is responsible for closing the stream after use.

Specified by:
fetchStream in interface DSLContext





fetchStream
public <R extends Record> Stream<R> fetchStream(Table<R> table,
 Collection<? extends Condition> conditions)
Description copied from interface: DSLContext
Execute and return all records lazily for
 SELECT table.col1, table.col2 FROM table WHERE condition.
 
 The result and its contained records are attached to this
 Configuration by default. Use Settings.isAttachRecords()
 to override this behaviour.
 

 Convenience API for calling DSLContext.fetchStream(Table, Condition) with
 DSL.and(Collection).
 

 Depending on your JDBC driver's default behaviour, this may load the
 whole database result into the driver's memory. In order to indicate to
 the driver that you may not want to fetch all records at once, use
 ResultQuery.fetchSize(int) and run
 ResultQuery.fetchStream() instead, or specify
 Settings.setFetchSize(Integer) prior to calling this method.
 

 Client code is responsible for closing the stream after use.

Specified by:
fetchStream in interface DSLContext





executeInsert
public int executeInsert(TableRecord<?> record)
Description copied from interface: DSLContext
Insert one record.
 
 This executes something like the following statement:
 
INSERT INTO [table] ... VALUES [record] 
 
 Unlike UpdatableRecord.store(), this does not change any of the
 argument record's internal "changed" flags, such that a
 subsequent call to UpdatableRecord.store() might lead to another
 INSERT statement being executed.

Specified by:
executeInsert in interface DSLContext
Returns:
The number of inserted records





executeUpdate
public int executeUpdate(UpdatableRecord<?> record)
Description copied from interface: DSLContext
Update a table.
 UPDATE [table] SET [modified values in record] WHERE [record is supplied record] 

Specified by:
executeUpdate in interface DSLContext
Returns:
The number of updated records





executeUpdate
public int executeUpdate(TableRecord<?> record,
 Condition condition)
Description copied from interface: DSLContext
Update a table.
 UPDATE [table] SET [modified values in record] WHERE [condition]

Specified by:
executeUpdate in interface DSLContext
Returns:
The number of updated records





executeDelete
public int executeDelete(UpdatableRecord<?> record)
Description copied from interface: DSLContext
Delete a record from a table.
 DELETE FROM [table] WHERE [record is supplied record]

Specified by:
executeDelete in interface DSLContext
Returns:
The number of deleted records





executeDelete
public int executeDelete(TableRecord<?> record,
 Condition condition)
Description copied from interface: DSLContext
Delete a record from a table.
 DELETE FROM [table] WHERE [condition]

Specified by:
executeDelete in interface DSLContext
Returns:
The number of deleted records





toString
public String toString()

Overrides:
toString in class Object





configuration
public final Configuration configuration()
Description copied from interface: Scope
The configuration of the current scope.

Specified by:
configuration in interface Scope





dsl
public final DSLContext dsl()
Description copied from interface: Scope
Wrap the Scope.configuration() in a DSLContext, providing
 access to the configuration-contextual DSL to construct executable
 queries.

Specified by:
dsl in interface Scope





settings
public final Settings settings()
Description copied from interface: Scope
The settings wrapped by this context.
 
 This method is a convenient way of accessing
 configuration().settings().

Specified by:
settings in interface Scope





dialect
public final SQLDialect dialect()
Description copied from interface: Scope
The SQLDialect wrapped by this context.
 
 This method is a convenient way of accessing
 configuration().dialect().

Specified by:
dialect in interface Scope





family
public final SQLDialect family()
Description copied from interface: Scope
The SQLDialect.family() wrapped by this context.
 
 This method is a convenient way of accessing
 configuration().family().

Specified by:
family in interface Scope





data
public final Map<Object,Object> data()
Description copied from interface: Scope
Get all custom data from this Scope.
 
 This is custom data that was previously set to the context using
 Scope.data(Object, Object). Use custom data if you want to pass data
 to QueryPart objects for a given Scope.

Specified by:
data in interface Scope
Returns:
The custom data. This is never null





data
public final Object data(Object key)
Description copied from interface: Scope
Get some custom data from this Scope.
 
 This is custom data that was previously set to the context using
 Scope.data(Object, Object). Use custom data if you want to pass data
 to QueryPart objects for a given Scope

Specified by:
data in interface Scope
Parameters:
key - A key to identify the custom data
Returns:
The custom data or null if no such data is contained
         in this Scope





data
public final Object data(Object key,
 Object value)
Description copied from interface: Scope
Set some custom data to this Scope.
 
 This is custom data that was previously set to the context using
 Scope.data(Object, Object). Use custom data if you want to pass data
 to QueryPart objects for a given Scope.

Specified by:
data in interface Scope
Parameters:
key - A key to identify the custom data
value - The custom data
Returns:
The previously set custom data or null if no data
         was previously set for the given key

`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)

dialect	support type	documentation
DB2	SQL:2008 standard and major enhancements	http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com. ibm.db2.udb.admin.doc/doc/r0010873.htm
HSQLDB	SQL:2008 standard	http://hsqldb.org/doc/2.0/guide/dataaccess-chapt.html#N129BA
Oracle	SQL:2008 standard and minor enhancements	http://download.oracle.com/docs/cd/B28359_01/server.111/b28286/ statements_9016.htm
SQL Server	Similar to SQL:2008 standard with some major enhancements	http://msdn.microsoft.com/de-de/library/bb510625.aspx
Sybase	Similar to SQL:2008 standard with some major enhancements	http://dcx.sybase.com/1100/en/dbreference_en11/merge-statement.html

H2	H2 natively supports this special syntax	https://www.h2database.com/html/commands.html#merge_into
HANA	HANA natively supports this syntax	http://help.sap.com/saphelp_hanaplatform/helpdata/en/20/fc06a7751910149892c0d09be21a38/content.htm
PostgreSQL	This database can emulate the H2-specific MERGE statement via `INSERT .. ON CONFLICT DO UPDATE`	http://www.postgresql.org/docs/9.5/static/sql-insert.html
DB2, HSQLDB, Oracle, SQL Server, Sybase SQL Anywhere	These databases can emulate the H2-specific MERGE statement using a standard SQL MERGE statement, without restrictions	See `DSLContext.mergeInto(Table)` for the standard MERGE statement

Class DefaultDSLContext

Constructor Summary

Method Summary

Methods inherited from class java.lang.Object

Methods inherited from interface org.jooq.Scope

Constructor Details

DefaultDSLContext

DefaultDSLContext

DefaultDSLContext

DefaultDSLContext

DefaultDSLContext

DefaultDSLContext

DefaultDSLContext

DefaultDSLContext

DefaultDSLContext

DefaultDSLContext

DefaultDSLContext

Method Details

map

map

parser

parsingConnection

parsingDataSource

parsingConnectionFactory

diagnosticsConnection

diagnosticsDataSource

version

versions

commit

commits

migrateTo

meta

meta

meta

meta

meta

meta

meta

meta

meta

informationSchema

informationSchema

informationSchema

informationSchema

informationSchema

informationSchema

explain

transactionResult

transactionResult

transaction

transaction

transactionAsync

transactionAsync

transactionResultAsync

transactionResultAsync

connectionResult

connection

mockResult

mock

renderContext

render

renderNamedParams

renderNamedOrInlinedParams

renderInlined

extractBindValues

extractParams

extractParam

bindContext

attach

attach

loadInto

queries

queries

begin

begin

statements

statements

query

query

query