- All Implemented Interfaces:
Serializable
,DSLContext
,Scope
- Direct Known Subclasses:
DefaultCloseableDSLContext
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:
-
Constructor Summary
ConstructorDescriptionDefaultDSLContext
(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 TypeMethodDescriptionalterDatabase
(String database) TheALTER DATABASE
statement.alterDatabase
(Catalog database) TheALTER DATABASE
statement.alterDatabase
(Name database) TheALTER DATABASE
statement.alterDatabaseIfExists
(String database) TheALTER DATABASE IF EXISTS
statement.alterDatabaseIfExists
(Catalog database) TheALTER DATABASE IF EXISTS
statement.alterDatabaseIfExists
(Name database) TheALTER DATABASE IF EXISTS
statement.<T> AlterDomainStep<T>
alterDomain
(String domain) TheALTER DOMAIN
statement.<T> AlterDomainStep<T>
alterDomain
(Domain<T> domain) TheALTER DOMAIN
statement.<T> AlterDomainStep<T>
alterDomain
(Name domain) TheALTER DOMAIN
statement.<T> AlterDomainStep<T>
alterDomainIfExists
(String domain) TheALTER DOMAIN IF EXISTS
statement.<T> AlterDomainStep<T>
alterDomainIfExists
(Domain<T> domain) TheALTER DOMAIN IF EXISTS
statement.<T> AlterDomainStep<T>
alterDomainIfExists
(Name domain) TheALTER DOMAIN IF EXISTS
statement.alterIndex
(String index) TheALTER INDEX
statement.alterIndex
(Index index) TheALTER INDEX
statement.alterIndex
(Name index) TheALTER INDEX
statement.alterIndexIfExists
(String index) TheALTER INDEX IF EXISTS
statement.alterIndexIfExists
(Index index) TheALTER INDEX IF EXISTS
statement.alterIndexIfExists
(Name index) TheALTER INDEX IF EXISTS
statement.alterMaterializedView
(String view) TheALTER MATERIALIZED VIEW
statement.alterMaterializedView
(Name view) TheALTER MATERIALIZED VIEW
statement.alterMaterializedView
(Table<?> view) TheALTER MATERIALIZED VIEW
statement.TheALTER MATERIALIZED VIEW IF EXISTS
statement.TheALTER MATERIALIZED VIEW IF EXISTS
statement.alterMaterializedViewIfExists
(Table<?> view) TheALTER MATERIALIZED VIEW IF EXISTS
statement.alterSchema
(String schema) TheALTER SCHEMA
statement.alterSchema
(Name schema) TheALTER SCHEMA
statement.alterSchema
(Schema schema) TheALTER SCHEMA
statement.alterSchemaIfExists
(String schema) TheALTER SCHEMA IF EXISTS
statement.alterSchemaIfExists
(Name schema) TheALTER SCHEMA IF EXISTS
statement.alterSchemaIfExists
(Schema schema) TheALTER SCHEMA IF EXISTS
statement.alterSequence
(String sequence) TheALTER SEQUENCE
statement.alterSequence
(Name sequence) TheALTER SEQUENCE
statement.<T extends Number>
AlterSequenceStep<T>alterSequence
(Sequence<T> sequence) TheALTER SEQUENCE
statement.alterSequenceIfExists
(String sequence) TheALTER SEQUENCE IF EXISTS
statement.alterSequenceIfExists
(Name sequence) TheALTER SEQUENCE IF EXISTS
statement.<T extends Number>
AlterSequenceStep<T>alterSequenceIfExists
(Sequence<T> sequence) TheALTER SEQUENCE IF EXISTS
statement.alterTable
(String table) Create a new DSLALTER TABLE
statement.alterTable
(Name table) Create a new DSLALTER TABLE
statement.alterTable
(Table<?> table) Create a new DSLALTER TABLE
statement.alterTableIfExists
(String table) Create a new DSLALTER TABLE
statement.alterTableIfExists
(Name table) Create a new DSLALTER TABLE
statement.alterTableIfExists
(Table<?> table) Create a new DSLALTER TABLE
statement.TheALTER TYPE
statement.TheALTER TYPE
statement.alterTypeIfExists
(String type) TheALTER TYPE IF EXISTS
statement.alterTypeIfExists
(Name type) TheALTER TYPE IF EXISTS
statement.TheALTER VIEW
statement.TheALTER VIEW
statement.TheALTER VIEW
statement.alterView
(Table<?> view, Collection<? extends Field<?>> fields) TheALTER VIEW
statement.TheALTER VIEW
statement.alterViewIfExists
(String view) TheALTER VIEW IF EXISTS
statement.alterViewIfExists
(Name view) TheALTER VIEW IF EXISTS
statement.alterViewIfExists
(Table<?> view) TheALTER VIEW IF EXISTS
statement.void
attach
(Collection<? extends Attachable> attachables) Attach thisDSLContext
's underlyingScope.configuration()
to some attachables.void
attach
(Attachable... attachables) Attach thisDSLContext
's underlyingScope.configuration()
to some attachables.Create a batch statement to execute a set of queries in batch mode (with bind values).Create a batch statement to execute a set of queries in batch mode (without bind values).Create a batch statement to execute a set of queries in batch mode (with bind values).batch
(Collection<? extends Query> queries) Create a batch statement to execute a set of queries in batch mode (without bind values).Create a batch statement to execute a set of queries in batch mode (without bind values).Create a batch statement to execute a set of queries in batch mode (with bind values).Create a batch statement to execute a set of queries in batch mode (without bind values).Create a batch statement to execute a set of queries in batch mode (with bind values).batchDelete
(Collection<? extends UpdatableRecord<?>> records) Create a batch statement to execute a set ofDELETE
queries in batch mode (with bind values) according toUpdatableRecord.delete()
sematics.batchDelete
(UpdatableRecord<?>... records) Create a batch statement to execute a set ofDELETE
queries in batch mode (with bind values) according toUpdatableRecord.delete()
sematics.void
batched
(BatchedRunnable runnable) Run aBatchedRunnable
on aBatchedConnection
, delaying execution as long as possible before batching.<T> T
batchedResult
(BatchedCallable<T> callable) Run aBatchedRunnable
on aBatchedConnection
, delaying execution as long as possible before batching.batchInsert
(Collection<? extends TableRecord<?>> records) Create a batch statement to execute a set ofINSERT
queries in batch mode (with bind values) according toTableRecord.insert()
semantics.batchInsert
(TableRecord<?>... records) Create a batch statement to execute a set ofINSERT
queries in batch mode (with bind values) according toTableRecord.insert()
semantics.batchMerge
(Collection<? extends UpdatableRecord<?>> records) Create a batch statement to execute a set ofMERGE
queries in batch mode (with bind values) according toUpdatableRecord.merge()
semantics.batchMerge
(UpdatableRecord<?>... records) Create a batch statement to execute a set ofMERGE
queries in batch mode (with bind values) according toUpdatableRecord.merge()
semantics.batchStore
(Collection<? extends UpdatableRecord<?>> records) Create a batch statement to execute a set ofINSERT
andUPDATE
queries in batch mode (with bind values) according toUpdatableRecord.store()
semantics.batchStore
(UpdatableRecord<?>... records) Create a batch statement to execute a set ofINSERT
andUPDATE
queries in batch mode (with bind values) according toUpdatableRecord.store()
semantics.batchUpdate
(Collection<? extends UpdatableRecord<?>> records) Create a batch statement to execute a set ofUPDATE
queries in batch mode (with bind values) according toUpdatableRecord.update()
semantics.batchUpdate
(UpdatableRecord<?>... records) Create a batch statement to execute a set ofUPDATE
queries in batch mode (with bind values) according toUpdatableRecord.update()
semantics.begin
(Collection<? extends Statement> statements) Wrap a collection of statements in an anoymous procedural block.Wrap a collection of statements in an anonymous procedural block.bindContext
(PreparedStatement stmt) Get a newBindContext
for the context of thisDSLContext
.TheCALL
statement.TheCALL
statement.commentOnColumn
(String field) TheCOMMENT ON COLUMN
statement.commentOnColumn
(Field<?> field) TheCOMMENT ON COLUMN
statement.commentOnColumn
(Name field) TheCOMMENT ON COLUMN
statement.TheCOMMENT ON MATERIALIZED VIEW
statement.TheCOMMENT ON MATERIALIZED VIEW
statement.commentOnMaterializedView
(Table<?> view) TheCOMMENT ON MATERIALIZED VIEW
statement.commentOnTable
(String table) TheCOMMENT ON TABLE
statement.commentOnTable
(Name table) TheCOMMENT ON TABLE
statement.commentOnTable
(Table<?> table) TheCOMMENT ON TABLE
statement.commentOnView
(String view) TheCOMMENT ON VIEW
statement.commentOnView
(Name view) TheCOMMENT ON VIEW
statement.commentOnView
(Table<?> view) TheCOMMENT ON VIEW
statement.commit()
TheCOMMIT
statement.final Configuration
The configuration of the current scope.void
connection
(ConnectionRunnable runnable) Run aConnectionRunnable
in the context of thisDSLContext
's underlyingScope.configuration()
'sConfiguration.connectionProvider()
.<T> T
connectionResult
(ConnectionCallable<T> callable) Run aConnectionCallable
in the context of thisDSLContext
's underlyingScope.configuration()
'sConfiguration.connectionProvider()
.createDatabase
(String database) TheCREATE DATABASE
statement.createDatabase
(Catalog database) TheCREATE DATABASE
statement.createDatabase
(Name database) TheCREATE DATABASE
statement.createDatabaseIfNotExists
(String database) TheCREATE DATABASE IF NOT EXISTS
statement.createDatabaseIfNotExists
(Catalog database) TheCREATE DATABASE IF NOT EXISTS
statement.createDatabaseIfNotExists
(Name database) TheCREATE DATABASE IF NOT EXISTS
statement.createDomain
(String domain) TheCREATE DOMAIN
statement.createDomain
(Domain<?> domain) TheCREATE DOMAIN
statement.createDomain
(Name domain) TheCREATE DOMAIN
statement.createDomainIfNotExists
(String domain) TheCREATE DOMAIN IF NOT EXISTS
statement.createDomainIfNotExists
(Domain<?> domain) TheCREATE DOMAIN IF NOT EXISTS
statement.createDomainIfNotExists
(Name domain) TheCREATE DOMAIN IF NOT EXISTS
statement.createFunction
(String function) TheCREATE FUNCTION
statement.createFunction
(Name function) TheCREATE FUNCTION
statement.createGlobalTemporaryTable
(String table) TheCREATE GLOBAL TEMPORARY TABLE
statement.createGlobalTemporaryTable
(Name table) TheCREATE GLOBAL TEMPORARY TABLE
statement.createGlobalTemporaryTable
(Table<?> table) TheCREATE GLOBAL TEMPORARY TABLE
statement.TheCREATE GLOBAL TEMPORARY TABLE IF NOT EXISTS
statement.TheCREATE GLOBAL TEMPORARY TABLE IF NOT EXISTS
statement.createGlobalTemporaryTableIfNotExists
(Table<?> table) TheCREATE GLOBAL TEMPORARY TABLE IF NOT EXISTS
statement.TheCREATE INDEX
statement.createIndex
(String index) TheCREATE INDEX
statement.createIndex
(Index index) TheCREATE INDEX
statement.createIndex
(Name index) TheCREATE INDEX
statement.TheCREATE INDEX IF NOT EXISTS
statement.createIndexIfNotExists
(String index) TheCREATE INDEX IF NOT EXISTS
statement.createIndexIfNotExists
(Index index) TheCREATE INDEX IF NOT EXISTS
statement.createIndexIfNotExists
(Name index) TheCREATE INDEX IF NOT EXISTS
statement.createMaterializedView
(String view, String... fields) TheCREATE MATERIALIZED VIEW
statement.createMaterializedView
(String view, Collection<? extends String> fields) TheCREATE MATERIALIZED VIEW
statement.createMaterializedView
(Name view, Collection<? extends Name> fields) TheCREATE MATERIALIZED VIEW
statement.createMaterializedView
(Name view, Name... fields) TheCREATE MATERIALIZED VIEW
statement.createMaterializedView
(Table<?> view, Collection<? extends Field<?>> fields) TheCREATE MATERIALIZED VIEW
statement.createMaterializedView
(Table<?> view, Field<?>... fields) TheCREATE MATERIALIZED VIEW
statement.createMaterializedViewIfNotExists
(String view, String... fields) TheCREATE MATERIALIZED VIEW IF NOT EXISTS
statement.createMaterializedViewIfNotExists
(String view, Collection<? extends String> fields) TheCREATE MATERIALIZED VIEW IF NOT EXISTS
statement.createMaterializedViewIfNotExists
(Name view, Collection<? extends Name> fields) TheCREATE MATERIALIZED VIEW IF NOT EXISTS
statement.createMaterializedViewIfNotExists
(Name view, Name... fields) TheCREATE MATERIALIZED VIEW IF NOT EXISTS
statement.createMaterializedViewIfNotExists
(Table<?> view, Collection<? extends Field<?>> fields) TheCREATE MATERIALIZED VIEW IF NOT EXISTS
statement.createMaterializedViewIfNotExists
(Table<?> view, Field<?>... fields) TheCREATE MATERIALIZED VIEW IF NOT EXISTS
statement.createOrReplaceFunction
(String function) TheCREATE OR REPLACE FUNCTION
statement.createOrReplaceFunction
(Name function) TheCREATE OR REPLACE FUNCTION
statement.createOrReplaceMaterializedView
(String view, String... fields) TheCREATE OR REPLACE MATERIALIZED VIEW
statement.createOrReplaceMaterializedView
(String view, Collection<? extends String> fields) TheCREATE OR REPLACE MATERIALIZED VIEW
statement.createOrReplaceMaterializedView
(Name view, Collection<? extends Name> fields) TheCREATE OR REPLACE MATERIALIZED VIEW
statement.createOrReplaceMaterializedView
(Name view, Name... fields) TheCREATE OR REPLACE MATERIALIZED VIEW
statement.createOrReplaceMaterializedView
(Table<?> view, Collection<? extends Field<?>> fields) TheCREATE OR REPLACE MATERIALIZED VIEW
statement.createOrReplaceMaterializedView
(Table<?> view, Field<?>... fields) TheCREATE OR REPLACE MATERIALIZED VIEW
statement.createOrReplaceProcedure
(String procedure) TheCREATE OR REPLACE PROCEDURE
statement.createOrReplaceProcedure
(Name procedure) TheCREATE OR REPLACE PROCEDURE
statement.createOrReplaceTrigger
(String trigger) TheCREATE OR REPLACE TRIGGER
statement.createOrReplaceTrigger
(Name trigger) TheCREATE OR REPLACE TRIGGER
statement.createOrReplaceTrigger
(Trigger trigger) TheCREATE OR REPLACE TRIGGER
statement.createOrReplaceView
(String view, String... fields) TheCREATE OR REPLACE VIEW
statement.createOrReplaceView
(String view, Collection<? extends String> fields) TheCREATE OR REPLACE VIEW
statement.createOrReplaceView
(String view, BiFunction<? super Field<?>, ? super Integer, ? extends String> fieldNameFunction) Create a new DSLCREATE OR REPLACE VIEW
statement.createOrReplaceView
(String view, Function<? super Field<?>, ? extends String> fieldNameFunction) Create a new DSLCREATE OR REPLACE VIEW
statement.createOrReplaceView
(Name view, Collection<? extends Name> fields) TheCREATE OR REPLACE VIEW
statement.createOrReplaceView
(Name view, BiFunction<? super Field<?>, ? super Integer, ? extends Name> fieldNameFunction) Create a new DSLCREATE OR REPLACE VIEW
statement.createOrReplaceView
(Name view, Function<? super Field<?>, ? extends Name> fieldNameFunction) Create a new DSLCREATE OR REPLACE VIEW
statement.createOrReplaceView
(Name view, Name... fields) TheCREATE OR REPLACE VIEW
statement.createOrReplaceView
(Table<?> view, Collection<? extends Field<?>> fields) TheCREATE OR REPLACE VIEW
statement.createOrReplaceView
(Table<?> view, BiFunction<? super Field<?>, ? super Integer, ? extends Field<?>> fieldNameFunction) Create a new DSLCREATE OR REPLACE VIEW
statement.createOrReplaceView
(Table<?> view, Function<? super Field<?>, ? extends Field<?>> fieldNameFunction) Create a new DSLCREATE OR REPLACE VIEW
statement.createOrReplaceView
(Table<?> view, Field<?>... fields) TheCREATE OR REPLACE VIEW
statement.createProcedure
(String procedure) TheCREATE PROCEDURE
statement.createProcedure
(Name procedure) TheCREATE PROCEDURE
statement.createSchema
(String schema) TheCREATE SCHEMA
statement.createSchema
(Name schema) TheCREATE SCHEMA
statement.createSchema
(Schema schema) TheCREATE SCHEMA
statement.createSchemaIfNotExists
(String schema) TheCREATE SCHEMA IF NOT EXISTS
statement.createSchemaIfNotExists
(Name schema) TheCREATE SCHEMA IF NOT EXISTS
statement.createSchemaIfNotExists
(Schema schema) TheCREATE SCHEMA IF NOT EXISTS
statement.createSequence
(String sequence) TheCREATE SEQUENCE
statement.createSequence
(Name sequence) TheCREATE SEQUENCE
statement.createSequence
(Sequence<?> sequence) TheCREATE SEQUENCE
statement.createSequenceIfNotExists
(String sequence) TheCREATE SEQUENCE IF NOT EXISTS
statement.createSequenceIfNotExists
(Name sequence) TheCREATE SEQUENCE IF NOT EXISTS
statement.createSequenceIfNotExists
(Sequence<?> sequence) TheCREATE SEQUENCE IF NOT EXISTS
statement.createTable
(String table) TheCREATE TABLE
statement.createTable
(Name table) TheCREATE TABLE
statement.createTable
(Table<?> table) TheCREATE TABLE
statement.createTableIfNotExists
(String table) TheCREATE TABLE IF NOT EXISTS
statement.createTableIfNotExists
(Name table) TheCREATE TABLE IF NOT EXISTS
statement.createTableIfNotExists
(Table<?> table) TheCREATE TABLE IF NOT EXISTS
statement.createTemporaryTable
(String table) TheCREATE TEMPORARY TABLE
statement.createTemporaryTable
(Name table) TheCREATE TEMPORARY TABLE
statement.createTemporaryTable
(Table<?> table) TheCREATE TEMPORARY TABLE
statement.TheCREATE TEMPORARY TABLE IF NOT EXISTS
statement.TheCREATE TEMPORARY TABLE IF NOT EXISTS
statement.createTemporaryTableIfNotExists
(Table<?> table) TheCREATE TEMPORARY TABLE IF NOT EXISTS
statement.createTrigger
(String trigger) TheCREATE TRIGGER
statement.createTrigger
(Name trigger) TheCREATE TRIGGER
statement.createTrigger
(Trigger trigger) TheCREATE TRIGGER
statement.createType
(String type) TheCREATE TYPE
statement.createType
(Name type) TheCREATE TYPE
statement.createType
(Type<?> type) TheCREATE TYPE
statement.createTypeIfNotExists
(String type) TheCREATE TYPE IF NOT EXISTS
statement.createTypeIfNotExists
(Name type) TheCREATE TYPE IF NOT EXISTS
statement.createTypeIfNotExists
(Type<?> type) TheCREATE TYPE IF NOT EXISTS
statement.TheCREATE UNIQUE INDEX
statement.createUniqueIndex
(String index) TheCREATE UNIQUE INDEX
statement.createUniqueIndex
(Index index) TheCREATE UNIQUE INDEX
statement.createUniqueIndex
(Name index) TheCREATE UNIQUE INDEX
statement.TheCREATE UNIQUE INDEX IF NOT EXISTS
statement.TheCREATE UNIQUE INDEX IF NOT EXISTS
statement.TheCREATE UNIQUE INDEX IF NOT EXISTS
statement.createUniqueIndexIfNotExists
(Name index) TheCREATE UNIQUE INDEX IF NOT EXISTS
statement.createView
(String view, String... fields) TheCREATE VIEW
statement.createView
(String view, Collection<? extends String> fields) TheCREATE VIEW
statement.createView
(String view, BiFunction<? super Field<?>, ? super Integer, ? extends String> fieldNameFunction) Create a new DSLCREATE VIEW
statement.createView
(String view, Function<? super Field<?>, ? extends String> fieldNameFunction) Create a new DSLCREATE VIEW
statement.createView
(Name view, Collection<? extends Name> fields) TheCREATE VIEW
statement.createView
(Name view, BiFunction<? super Field<?>, ? super Integer, ? extends Name> fieldNameFunction) Create a new DSLCREATE VIEW
statement.createView
(Name view, Function<? super Field<?>, ? extends Name> fieldNameFunction) Create a new DSLCREATE VIEW
statement.createView
(Name view, Name... fields) TheCREATE VIEW
statement.createView
(Table<?> view, Collection<? extends Field<?>> fields) TheCREATE VIEW
statement.createView
(Table<?> view, BiFunction<? super Field<?>, ? super Integer, ? extends Field<?>> fieldNameFunction) Create a new DSLCREATE VIEW
statement.createView
(Table<?> view, Function<? super Field<?>, ? extends Field<?>> fieldNameFunction) Create a new DSLCREATE VIEW
statement.createView
(Table<?> view, Field<?>... fields) TheCREATE VIEW
statement.createViewIfNotExists
(String view, String... fields) TheCREATE VIEW IF NOT EXISTS
statement.createViewIfNotExists
(String view, Collection<? extends String> fields) TheCREATE VIEW IF NOT EXISTS
statement.createViewIfNotExists
(String view, BiFunction<? super Field<?>, ? super Integer, ? extends String> fieldNameFunction) Create a new DSLCREATE VIEW
statement.createViewIfNotExists
(String view, Function<? super Field<?>, ? extends String> fieldNameFunction) Create a new DSLCREATE VIEW
statement.createViewIfNotExists
(Name view, Collection<? extends Name> fields) TheCREATE VIEW IF NOT EXISTS
statement.createViewIfNotExists
(Name view, BiFunction<? super Field<?>, ? super Integer, ? extends Name> fieldNameFunction) Create a new DSLCREATE VIEW
statement.createViewIfNotExists
(Name view, Function<? super Field<?>, ? extends Name> fieldNameFunction) Create a new DSLCREATE VIEW
statement.createViewIfNotExists
(Name view, Name... fields) TheCREATE VIEW IF NOT EXISTS
statement.createViewIfNotExists
(Table<?> view, Collection<? extends Field<?>> fields) TheCREATE VIEW IF NOT EXISTS
statement.createViewIfNotExists
(Table<?> view, BiFunction<? super Field<?>, ? super Integer, ? extends Field<?>> fieldNameFunction) Create a new DSLCREATE VIEW
statement.createViewIfNotExists
(Table<?> view, Function<? super Field<?>, ? extends Field<?>> fieldNameFunction) Create a new DSLCREATE VIEW
statement.createViewIfNotExists
(Table<?> view, Field<?>... fields) TheCREATE VIEW IF NOT EXISTS
statement.final Instant
The time, according toConfiguration.clock()
, when thisScope
was created.Convenience method to fetch the CURRVAL for a sequence directly from thisDSLContext
's underlying JDBCConnection
.Convenience method to fetch the CURRVAL for a sequence directly from thisDSLContext
's underlying JDBCConnection
.<T extends Number>
TConvenience method to fetch the CURRVAL for a sequence directly from thisDSLContext
's underlying JDBCConnection
.data()
Get all custom data from thisScope
.final Object
Get some custom data from thisScope
.final Object
Set some custom data to thisScope
.ddl
(Collection<? extends Table<?>> tables) Convenience method forMeta.ddl()
.ddl
(Collection<? extends Table<?>> tables, DDLExportConfiguration exportConfiguration) Convenience method forMeta.ddl(DDLExportConfiguration)
.ddl
(Collection<? extends Table<?>> tables, DDLFlag... flags) Convenience method forMeta.ddl(DDLExportConfiguration)
.Convenience method forMeta.ddl()
.ddl
(Catalog catalog, DDLExportConfiguration exportConfiguration) Convenience method forMeta.ddl(DDLExportConfiguration)
.Convenience method forMeta.ddl(DDLExportConfiguration)
.Convenience method forMeta.ddl()
.ddl
(Schema schema, DDLExportConfiguration exportConfiguration) Convenience method forMeta.ddl(DDLExportConfiguration)
.Convenience method forMeta.ddl(DDLExportConfiguration)
.Convenience method forMeta.ddl()
.ddl
(Table[] tables, DDLExportConfiguration exportConfiguration) Convenience method forMeta.ddl(DDLExportConfiguration)
.Convenience method forMeta.ddl(DDLExportConfiguration)
.Convenience method forMeta.ddl()
.ddl
(Table<?> table, DDLExportConfiguration exportConfiguration) Convenience method forMeta.ddl(DDLExportConfiguration)
.Convenience method forMeta.ddl(DDLExportConfiguration)
.<R extends Record>
DeleteUsingStep<R>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 newDeleteQuery
A JDBC connection that proxies the underlying connection to run the jOOQ Diagnostics Pack on executed queries.A JDBC connection that proxies the underlying connection to run the jOOQ Diagnostics Pack on executed queries.final SQLDialect
dialect()
TheSQLDialect
wrapped by this context.dropDatabase
(String database) TheDROP DATABASE
statement.dropDatabase
(Catalog database) TheDROP DATABASE
statement.dropDatabase
(Name database) TheDROP DATABASE
statement.dropDatabaseIfExists
(String database) TheDROP DATABASE IF EXISTS
statement.dropDatabaseIfExists
(Catalog database) TheDROP DATABASE IF EXISTS
statement.dropDatabaseIfExists
(Name database) TheDROP DATABASE IF EXISTS
statement.dropDomain
(String domain) TheDROP DOMAIN
statement.dropDomain
(Domain<?> domain) TheDROP DOMAIN
statement.dropDomain
(Name domain) TheDROP DOMAIN
statement.dropDomainIfExists
(String domain) TheDROP DOMAIN IF EXISTS
statement.dropDomainIfExists
(Domain<?> domain) TheDROP DOMAIN IF EXISTS
statement.dropDomainIfExists
(Name domain) TheDROP DOMAIN IF EXISTS
statement.dropFunction
(String function) TheDROP FUNCTION
statement.dropFunction
(Name function) TheDROP FUNCTION
statement.dropFunctionIfExists
(String function) TheDROP FUNCTION IF EXISTS
statement.dropFunctionIfExists
(Name function) TheDROP FUNCTION IF EXISTS
statement.TheDROP INDEX
statement.TheDROP INDEX
statement.TheDROP INDEX
statement.dropIndexIfExists
(String index) TheDROP INDEX IF EXISTS
statement.dropIndexIfExists
(Index index) TheDROP INDEX IF EXISTS
statement.dropIndexIfExists
(Name index) TheDROP INDEX IF EXISTS
statement.dropMaterializedView
(String view) TheDROP MATERIALIZED VIEW
statement.dropMaterializedView
(Name view) TheDROP MATERIALIZED VIEW
statement.dropMaterializedView
(Table<?> view) TheDROP MATERIALIZED VIEW
statement.TheDROP MATERIALIZED VIEW IF EXISTS
statement.TheDROP MATERIALIZED VIEW IF EXISTS
statement.dropMaterializedViewIfExists
(Table<?> view) TheDROP MATERIALIZED VIEW IF EXISTS
statement.dropProcedure
(String procedure) TheDROP PROCEDURE
statement.dropProcedure
(Name procedure) TheDROP PROCEDURE
statement.dropProcedureIfExists
(String procedure) TheDROP PROCEDURE IF EXISTS
statement.dropProcedureIfExists
(Name procedure) TheDROP PROCEDURE IF EXISTS
statement.dropSchema
(String schema) TheDROP SCHEMA
statement.dropSchema
(Name schema) TheDROP SCHEMA
statement.dropSchema
(Schema schema) TheDROP SCHEMA
statement.dropSchemaIfExists
(String schema) TheDROP SCHEMA IF EXISTS
statement.dropSchemaIfExists
(Name schema) TheDROP SCHEMA IF EXISTS
statement.dropSchemaIfExists
(Schema schema) TheDROP SCHEMA IF EXISTS
statement.dropSequence
(String sequence) TheDROP SEQUENCE
statement.dropSequence
(Name sequence) TheDROP SEQUENCE
statement.dropSequence
(Sequence<?> sequence) TheDROP SEQUENCE
statement.dropSequenceIfExists
(String sequence) TheDROP SEQUENCE IF EXISTS
statement.dropSequenceIfExists
(Name sequence) TheDROP SEQUENCE IF EXISTS
statement.dropSequenceIfExists
(Sequence<?> sequence) TheDROP SEQUENCE IF EXISTS
statement.TheDROP TABLE
statement.TheDROP TABLE
statement.TheDROP TABLE
statement.dropTableIfExists
(String table) TheDROP TABLE IF EXISTS
statement.dropTableIfExists
(Name table) TheDROP TABLE IF EXISTS
statement.dropTableIfExists
(Table<?> table) TheDROP TABLE IF EXISTS
statement.dropTemporaryTable
(String table) TheDROP TEMPORARY TABLE
statement.dropTemporaryTable
(Name table) TheDROP TEMPORARY TABLE
statement.dropTemporaryTable
(Table<?> table) TheDROP TEMPORARY TABLE
statement.dropTemporaryTableIfExists
(String table) TheDROP TEMPORARY TABLE IF EXISTS
statement.dropTemporaryTableIfExists
(Name table) TheDROP TEMPORARY TABLE IF EXISTS
statement.dropTemporaryTableIfExists
(Table<?> table) TheDROP TEMPORARY TABLE IF EXISTS
statement.dropTrigger
(String trigger) TheDROP TRIGGER
statement.dropTrigger
(Name trigger) TheDROP TRIGGER
statement.dropTrigger
(Trigger trigger) TheDROP TRIGGER
statement.dropTriggerIfExists
(String trigger) TheDROP TRIGGER IF EXISTS
statement.dropTriggerIfExists
(Name trigger) TheDROP TRIGGER IF EXISTS
statement.dropTriggerIfExists
(Trigger trigger) TheDROP TRIGGER IF EXISTS
statement.TheDROP TYPE
statement.TheDROP TYPE
statement.dropType
(Collection<? extends Type<?>> types) TheDROP TYPE
statement.TheDROP TYPE
statement.TheDROP TYPE
statement.TheDROP TYPE
statement.TheDROP TYPE
statement.dropTypeIfExists
(String types) TheDROP TYPE IF EXISTS
statement.dropTypeIfExists
(String... types) TheDROP TYPE IF EXISTS
statement.dropTypeIfExists
(Collection<? extends Type<?>> types) TheDROP TYPE IF EXISTS
statement.dropTypeIfExists
(Name types) TheDROP TYPE IF EXISTS
statement.dropTypeIfExists
(Name... types) TheDROP TYPE IF EXISTS
statement.dropTypeIfExists
(Type<?> types) TheDROP TYPE IF EXISTS
statement.dropTypeIfExists
(Type<?>... types) TheDROP TYPE IF EXISTS
statement.TheDROP VIEW
statement.TheDROP VIEW
statement.TheDROP VIEW
statement.dropViewIfExists
(String view) TheDROP VIEW IF EXISTS
statement.dropViewIfExists
(Name view) TheDROP VIEW IF EXISTS
statement.dropViewIfExists
(Table<?> view) TheDROP VIEW IF EXISTS
statement.final DSLContext
dsl()
Wrap theScope.configuration()
in aDSLContext
, providing access to the configuration-contextual DSL to construct executable queries.int
Execute a query holding plain SQL.int
Execute a new query holding plain SQL.int
Execute a new query holding plain SQL.int
Execute aQuery
in the context of thisDSLContext
.int
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.Run anEXPLAIN
statement in the database to estimate the cardinality of the query.extractBindValues
(QueryPart part) Retrieve the bind values that will be bound by a givenQueryPart
.Param<?>
extractParam
(QueryPart part, String name) Get a named parameter from aQueryPart
, provided its name.extractParams
(QueryPart part) Get aMap
of named parameters.final SQLDialect
family()
TheSQLDialect.family()
wrapped by this context.Execute a new query holding plain SQL.Execute a new query holding plain SQL.Execute a new query holding plain SQL.fetch
(ResultQuery<R> query) Execute aResultQuery
in the context of thisDSLContext
and return results.Execute a new query holding plain SQL.Execute and return all records forfetch
(Table<R> table, Collection<? extends Condition> conditions) Execute and return all records forExecute and return all records forExecute and return all records for<R extends Record>
RExecute and return zero or one record for<R extends Record>
RfetchAny
(Table<R> table, Collection<? extends Condition> conditions) Execute and return zero or one record for<R extends Record>
RExecute and return zero or one record for<R extends Record>
RExecute and return zero or on e record forfetchAsync
(String sql) Fetch results in a newCompletionStage
.fetchAsync
(String sql, Object... bindings) Fetch results in a newCompletionStage
.fetchAsync
(String sql, QueryPart... parts) Fetch results in a newCompletionStage
.fetchAsync
(ResultSet rs) Fetch results in a newCompletionStage
.fetchAsync
(ResultSet rs, Class<?>... types) Fetch results in a newCompletionStage
.fetchAsync
(ResultSet rs, DataType<?>... types) Fetch results in a newCompletionStage
.fetchAsync
(ResultSet rs, Field<?>... fields) Fetch results in a newCompletionStage
.fetchAsync
(Executor executor, String sql) Fetch results in a newCompletionStage
that is asynchronously completed by a task running in the given executor.fetchAsync
(Executor executor, String sql, Object... bindings) Fetch results in a newCompletionStage
that is asynchronously completed by a task running in the given executor.fetchAsync
(Executor executor, String sql, QueryPart... parts) Fetch results in a newCompletionStage
that is asynchronously completed by a task running in the given executor.fetchAsync
(Executor executor, ResultSet rs) Fetch results in a newCompletionStage
that is asynchronously completed by a task running in the given executor.fetchAsync
(Executor executor, ResultSet rs, Class<?>... types) Fetch results in a newCompletionStage
that is asynchronously completed by a task running in the given executor.fetchAsync
(Executor executor, ResultSet rs, DataType<?>... types) Fetch results in a newCompletionStage
that is asynchronously completed by a task running in the given executor.fetchAsync
(Executor executor, ResultSet rs, Field<?>... fields) Fetch results in a newCompletionStage
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 newCompletionStage
that is asynchronously completed by a task running in the given executor.fetchAsync
(Executor executor, SQL sql) Fetch results in a newCompletionStage
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 newCompletionStage
.fetchAsync
(SQL sql) Fetch results in a newCompletionStage
.<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) 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 aSelect
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.fetchFromCSV
(String string) Fetch all data from a CSV string.fetchFromCSV
(String string, boolean header) Fetch all data from a CSV string.fetchFromCSV
(String string, boolean header, char delimiter) Fetch all data from a CSV string.fetchFromCSV
(String string, char delimiter) Fetch all data from a CSV string.fetchFromHTML
(String string) Convert an HTML table into a jOOQResult
.fetchFromJSON
(String string) Fetch all data from a JSON string.fetchFromStringData
(String[]... strings) Fetch all data from a list of strings.fetchFromStringData
(List<String[]> strings) Fetch all data from a list of strings.fetchFromStringData
(List<String[]> strings, boolean header) Fetch all data from a list of strings.fetchFromTXT
(String string) Fetch all data from a formatted string.fetchFromTXT
(String string, String nullLiteral) Fetch all data from a formatted string.fetchFromXML
(String string) Fetch all data from an XML string.fetchGroups
(ResultQuery<? extends Record2<K, V>> query) Execute the query and return aMap
with the first column as the map key and the second column as the map values.Execute a new query holding plain SQL and "lazily" return the generated result.Execute a new query holding plain SQL and "lazily" return the generated result.Execute a new query holding plain SQL and "lazily" return the generated result.fetchLazy
(ResultQuery<R> query) Execute aResultQuery
in the context of thisDSLContext
and return a cursor.Execute a new query holding plain SQL and "lazily" return the generated result.Execute and return all records lazily forfetchLazy
(Table<R> table, Collection<? extends Condition> conditions) Execute and return all records lazily forExecute and return all records lazily forExecute and return all records lazily forExecute a new query holding plain SQL, possibly returning several result sets.Execute a new query holding plain SQL, possibly returning several result sets.Execute a new query holding plain SQL, possibly returning several result sets.fetchMany
(ResultQuery<R> query) Execute aResultQuery
in the context of thisDSLContext
and return a cursor.Execute a new query holding plain SQL, possibly returning several result sets.<K,
V> Map<K, V> fetchMap
(ResultQuery<? extends Record2<K, V>> query) Execute the query and return aMap
with the first column as the map key and the second column as the map value.Execute a new query holding plain SQL.Execute a new query holding plain SQL.Execute a new query holding plain SQL.<R extends Record>
RfetchOne
(ResultQuery<R> query) Execute aResultQuery
in the context of thisDSLContext
and return a record.Execute a new query holding plain SQL.<R extends Record>
RExecute and return zero or one record for<R extends Record>
RfetchOne
(Table<R> table, Collection<? extends Condition> conditions) Execute and return zero or one record for<R extends Record>
RExecute and return zero or one record for<R extends Record>
RExecute and return zero or one record forfetchOptional
(String sql) Execute a new query holding plain SQL.fetchOptional
(String sql, Object... bindings) Execute a new query holding plain SQL.fetchOptional
(String sql, QueryPart... parts) Execute a new query holding plain SQL.fetchOptional
(ResultSet rs, Class<?>... types) fetchOptional
(ResultSet rs, DataType<?>... types) fetchOptional
(ResultSet rs, Field<?>... fields) fetchOptional
(ResultQuery<R> query) Execute aResultQuery
in the context of thisDSLContext
and return a record.fetchOptional
(SQL sql) Execute a new query holding plain SQL.fetchOptional
(Table<R> table) Execute and return zero or one record forfetchOptional
(Table<R> table, Collection<? extends Condition> conditions) Execute and return zero or one record forfetchOptional
(Table<R> table, Condition condition) Execute and return zero or one record forfetchOptional
(Table<R> table, Condition... conditions) Execute and return zero or one record forOptional<?>
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<?>
Fetch a record from a JDBCResultSet
and return the only contained value.<T> Optional<T>
fetchOptionalValue
(ResultSet rs, Class<T> type) Fetch a record from a JDBCResultSet
and return the only contained value.<T> Optional<T>
fetchOptionalValue
(ResultSet rs, DataType<T> type) Fetch a record from a JDBCResultSet
and return the only contained value.<T> Optional<T>
fetchOptionalValue
(ResultSet rs, Field<T> field) Fetch a record from a JDBCResultSet
and return the only contained value.fetchOptionalValue
(ResultQuery<R> query) Execute aResultQuery
in the context of thisDSLContext
and return a single value.Optional<?>
fetchOptionalValue
(SQL sql) Execute a new query holding plain SQL.<T> Optional<T>
fetchOptionalValue
(TableField<?, T> field) Execute aResultQuery
in the context of thisDSLContext
and return a single value.<T> Optional<T>
fetchOptionalValue
(TableField<?, T> field, Condition condition) Execute aResultQuery
in the context of thisDSLContext
and return a single value.fetchSingle
(String sql) Execute a new query holding plain SQL.fetchSingle
(String sql, Object... bindings) Execute a new query holding plain SQL.fetchSingle
(String sql, QueryPart... parts) Execute a new query holding plain SQL.fetchSingle
(ResultSet rs) fetchSingle
(ResultSet rs, Class<?>... types) fetchSingle
(ResultSet rs, DataType<?>... types) fetchSingle
(ResultSet rs, Field<?>... fields) fetchSingle
(Collection<? extends SelectField<?>> fields) Execute and return exactly one record for<R extends Record>
RfetchSingle
(ResultQuery<R> query) Execute aResultQuery
in the context of thisDSLContext
and return a 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 forfetchSingle
(SQL sql) Execute a new query holding plain SQL.<R extends Record>
RfetchSingle
(Table<R> table) Execute and return exactly one record for<R extends Record>
RfetchSingle
(Table<R> table, Collection<? extends Condition> conditions) Execute and return exactly one record for<R extends Record>
RfetchSingle
(Table<R> table, Condition condition) Execute and return exactly one record for<R extends Record>
RfetchSingle
(Table<R> table, Condition... conditions) Execute and return exactly one record for<R extends Record>
RfetchSingle
(Table<R> table, Condition c1, Condition c2) Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.<R extends Record>
RfetchSingle
(Table<R> table, Condition c1, Condition c2, Condition c3) Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.<R extends Record>
RDisambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.<R extends Record>
RDisambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.<R extends Record>
RfetchSingle
(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6) Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.<R extends Record>
RfetchSingle
(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7) Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.<R extends Record>
RfetchSingle
(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8) Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.<R extends Record>
RfetchSingle
(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9) Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.<R extends Record>
RfetchSingle
(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10) Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.<R extends Record>
RfetchSingle
(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11) Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.<R extends Record>
RfetchSingle
(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11, Condition c12) Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.<R extends Record>
RfetchSingle
(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11, Condition c12, Condition c13) Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.<R extends Record>
RfetchSingle
(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11, Condition c12, Condition c13, Condition c14) Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.<R extends Record>
RfetchSingle
(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11, Condition c12, Condition c13, Condition c14, Condition c15) Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.<R extends Record>
RfetchSingle
(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11, Condition c12, Condition c13, Condition c14, Condition c15, Condition c16) Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.<R extends Record>
RfetchSingle
(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11, Condition c12, Condition c13, Condition c14, Condition c15, Condition c16, Condition c17) Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.<R extends Record>
RfetchSingle
(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11, Condition c12, Condition c13, Condition c14, Condition c15, Condition c16, Condition c17, Condition c18) Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.<R extends Record>
RfetchSingle
(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11, Condition c12, Condition c13, Condition c14, Condition c15, Condition c16, Condition c17, Condition c18, Condition c19) Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.<R extends Record>
RfetchSingle
(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11, Condition c12, Condition c13, Condition c14, Condition c15, Condition c16, Condition c17, Condition c18, Condition c19, Condition c20) Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.<R extends Record>
RfetchSingle
(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11, Condition c12, Condition c13, Condition c14, Condition c15, Condition c16, Condition c17, Condition c18, Condition c19, Condition c20, Condition c21) Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.<R extends Record>
RfetchSingle
(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11, Condition c12, Condition c13, Condition c14, Condition c15, Condition c16, Condition c17, Condition c18, Condition c19, Condition c20, Condition c21, Condition c22) Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.fetchStream
(String sql) Execute a new query holding plain SQL and "lazily" return the generated result.fetchStream
(String sql, Object... bindings) Execute a new query holding plain SQL and "lazily" return the generated result.fetchStream
(String sql, QueryPart... parts) Execute a new query holding plain SQL and "lazily" return the generated result.fetchStream
(ResultSet rs) fetchStream
(ResultSet rs, Class<?>... types) fetchStream
(ResultSet rs, DataType<?>... types) fetchStream
(ResultSet rs, Field<?>... fields) fetchStream
(ResultQuery<R> query) Execute aResultQuery
in the context of thisDSLContext
and return a stream.fetchStream
(SQL sql) Execute a new query holding plain SQL and "lazily" return the generated result.fetchStream
(Table<R> table) Execute and return all records lazily forfetchStream
(Table<R> table, Collection<? extends Condition> conditions) Execute and return all records lazily forfetchStream
(Table<R> table, Condition condition) Execute and return all records lazily forfetchStream
(Table<R> table, Condition... conditions) Execute and return all records lazily forfetchValue
(String sql) Execute a new query holding plain SQL.fetchValue
(String sql, Object... bindings) Execute a new query holding plain SQL.fetchValue
(String sql, QueryPart... parts) Execute a new query holding plain SQL.fetchValue
(ResultSet rs) Fetch a record from a JDBCResultSet
and return the only contained value.<T> T
fetchValue
(ResultSet rs, Class<T> type) Fetch a record from a JDBCResultSet
and return the only contained value.<T> T
fetchValue
(ResultSet rs, DataType<T> type) Fetch a record from a JDBCResultSet
and return the only contained value.<T> T
fetchValue
(ResultSet rs, Field<T> field) Fetch a record from a JDBCResultSet
and return the only contained value.<T,
R extends Record1<T>>
TfetchValue
(ResultQuery<R> query) Execute aResultQuery
in the context of thisDSLContext
and return a single value.<T> T
fetchValue
(SelectField<T> field) Execute aResultQuery
in the context of thisDSLContext
and return a single value.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 aResultQuery
in the context of thisDSLContext
and return a single value.<T> T
fetchValue
(TableField<?, T> field, Condition condition) Execute aResultQuery
in the context of thisDSLContext
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 JDBCResultSet
and return the only contained column's values.<T> List<T>
fetchValues
(ResultSet rs, Class<T> type) Fetch a result from a JDBCResultSet
and return the only contained column's values.<T> List<T>
fetchValues
(ResultSet rs, DataType<T> type) Fetch a result from a JDBCResultSet
and return the only contained column's values.<T> List<T>
fetchValues
(ResultSet rs, Field<T> field) Fetch a result from a JDBCResultSet
and return the only contained column's values.fetchValues
(ResultQuery<R> query) Execute aResultQuery
in the context of thisDSLContext
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 givenTable
'sTableField
.<T> List<T>
fetchValues
(TableField<?, T> field, Condition condition) Fetch all values in a givenTable
'sTableField
.grant
(Collection<? extends Privilege> privileges) TheGRANT
statement.TheGRANT
statement.TheGRANT
statement.informationSchema
(Catalog catalog) Convenience method forMeta.informationSchema()
.informationSchema
(Catalog... catalogs) Convenience method forMeta.informationSchema()
.informationSchema
(Schema schema) Convenience method forMeta.informationSchema()
.informationSchema
(Schema... schemas) Convenience method forMeta.informationSchema()
.informationSchema
(Table<?> table) Convenience method forMeta.informationSchema()
.informationSchema
(Table<?>... tables) Convenience method forMeta.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> 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 newInsertQuery
lastID()
Retrieve the last inserted ID.<R extends Record>
LoaderOptionsStep<R>Create a newLoader
object to load data from a CSV or XML source.Map a schema to another one.Map a table to another one.<R extends Record>
MergeUsingStep<R>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><R extends Record,
T1>
MergeKeyStep1<R,T1> Deprecated, for removal: This API element is subject to removal in a future version.<R extends Record,
T1, T2>
MergeKeyStep2<R,T1, T2> 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, viamergeInto(Table)
<R extends Record,
T1, T2, T3>
MergeKeyStep3<R,T1, T2, T3> 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, viamergeInto(Table)
<R extends Record,
T1, T2, T3, T4>
MergeKeyStep4<R,T1, T2, T3, T4> 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, viamergeInto(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, viamergeInto(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, viamergeInto(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, viamergeInto(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, viamergeInto(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, viamergeInto(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, viamergeInto(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, viamergeInto(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, viamergeInto(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, viamergeInto(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, viamergeInto(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, viamergeInto(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, viamergeInto(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, viamergeInto(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, viamergeInto(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, viamergeInto(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, viamergeInto(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, viamergeInto(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, viamergeInto(Table)
meta()
Access the database meta data.Create meta data from a set of sources.meta
(DatabaseMetaData meta) Access the database meta data from an explicit JDBCDatabaseMetaData
.Access the database meta data from explicit catalog information.Create meta data from a set of DDL queries.Access the database meta data from explicit schema information.Create meta data from a set of sources.Access the database meta data from explicit table information.meta
(InformationSchema schema) Access the database meta data from an explicit JAXB-annotated meta model.The experimental migrations API.void
mock
(MockDataProvider provider, MockRunnable mockable) Run aMockRunnable
in the context of thisDSLContext
's underlyingScope.configuration()
's, and of aMockDataProvider
.<T> T
mockResult
(MockDataProvider provider, MockCallable<T> mockable) Run aMockRunnable
in the context of thisDSLContext
's underlyingScope.configuration()
's, and of aMockDataProvider
and return themockable
's outcome.newRecord
(Collection<? extends Field<?>> fields) Create a new emptyRecord
.Create a new emptyRecord
.<T1> Record1<T1>
Create a new emptyRecord
.<T1,
T2> Record2<T1, T2> Create a new emptyRecord
.<T1,
T2, T3>
Record3<T1,T2, T3> Create a new emptyRecord
.<T1,
T2, T3, T4>
Record4<T1,T2, T3, T4> Create a new emptyRecord
.<T1,
T2, T3, T4, T5>
Record5<T1,T2, T3, T4, T5> Create a new emptyRecord
.<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 emptyRecord
.<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 emptyRecord
.<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 emptyRecord
.<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 emptyRecord
.<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 emptyRecord
.<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 emptyRecord
.<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 emptyRecord
.<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 emptyRecord
.<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 emptyRecord
.<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 emptyRecord
.<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 emptyRecord
.<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 emptyRecord
.<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 emptyRecord
.<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 emptyRecord
.<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 emptyRecord
.<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 emptyRecord
.<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 emptyRecord
.<R extends Record>
RCreate a newRecord
that can be inserted into the corresponding table.<R extends Record>
RCreate a new pre-filledRecord
that can be inserted into the corresponding table.<R extends UDTRecord<R>>
RCreate a newUDTRecord
.newResult
(Collection<? extends Field<?>> fields) Create a new emptyRecord
.Create a new emptyRecord
.Create a new emptyResult
.Create a new emptyResult
.Create a new emptyResult
.Create a new emptyResult
.Create a new emptyResult
.newResult
(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6) Create a new emptyResult
.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 emptyResult
.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 emptyResult
.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 emptyResult
.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 emptyResult
.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 emptyResult
.<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 emptyResult
.<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 emptyResult
.<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 emptyResult
.<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 emptyResult
.<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 emptyResult
.<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 emptyResult
.<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 emptyResult
.<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 emptyResult
.<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 emptyResult
.<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 emptyResult
.<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 emptyResult
.Create a new emptyResult
.Convenience method to fetch the NEXTVAL for a sequence directly from thisDSLContext
's underlying JDBCConnection
.Convenience method to fetch the NEXTVAL for a sequence directly from thisDSLContext
's underlying JDBCConnection
.<T extends Number>
TConvenience method to fetch the NEXTVAL for a sequence directly from thisDSLContext
's underlying JDBCConnection
.Convenience method to fetch several NEXTVAL for a sequence directly from thisDSLContext
's underlying JDBCConnection
.parser()
Access the parser API.A JDBC connection that runs each statement through theDSLContext.parser()
first, prior to re-generating and running the SQL.io.r2dbc.spi.ConnectionFactory
An R2DBCConnectionFactory
that runs each statement through theDSLContext.parser()
first, prior to re-generating and running the SQL.A JDBC data source that runs each statement through theDSLContext.parser()
first, prior to re-generating and running the SQL.queries
(Collection<? extends Query> queries) Wrap a collection of queries.Wrap a collection of queries.Create a new query holding plain SQL.Create a new query holding plain SQL.Create a new query holding plain SQL.Create a new query holding plain SQL.releaseSavepoint
(String name) TheRELEASE SAVEPOINT
statement.releaseSavepoint
(Name name) TheRELEASE SAVEPOINT
statement.Render a QueryPart in the context of thisDSLContext
.Get a newRenderContext
for the context of thisDSLContext
.renderInlined
(QueryPart part) Render a QueryPart in the context of thisDSLContext
, inlining all bind variables.Render a QueryPart in the context of thisDSLContext
, rendering bind variables as named parameters, or inlined parameters if they have no name.renderNamedParams
(QueryPart part) Render a QueryPart in the context of thisDSLContext
, rendering bind variables as named parameters.resultQuery
(String sql) Create a new query holding plain SQL.resultQuery
(String sql, Object... bindings) Create a new query holding plain SQL.resultQuery
(String sql, QueryPart... parts) Create a new query holding plain SQL.resultQuery
(SQL sql) Create a new query holding plain SQL.revoke
(Collection<? extends Privilege> privileges) TheREVOKE
statement.TheREVOKE
statement.TheREVOKE
statement.revokeGrantOptionFor
(Collection<? extends Privilege> privileges) TheREVOKE GRANT OPTION FOR
statement.revokeGrantOptionFor
(Privilege privileges) TheREVOKE GRANT OPTION FOR
statement.revokeGrantOptionFor
(Privilege... privileges) TheREVOKE GRANT OPTION FOR
statement.rollback()
TheROLLBACK
statement.TheSAVEPOINT
statement.TheSAVEPOINT
statement.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.select
(SelectFieldOrAsterisk... fields) Create a new DSL select statement.Create a new DSL select statement forCOUNT(*)
.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.selectDistinct
(SelectFieldOrAsterisk... fields) Create a new DSL select statement.selectFrom
(String sql) Create a new DSL select statement, projecting*
.selectFrom
(String sql, Object... bindings) Create a new DSL select statement, projecting*
.selectFrom
(String sql, QueryPart... parts) Create a new DSL select statement, projecting*
.selectFrom
(Name table) Create a new DSL select statement, projecting*
.selectFrom
(SQL sql) Create a new DSL select statement, projecting*
.<R extends Record>
SelectWhereStep<R>selectFrom
(TableLike<R> table) Create a new DSL select statement, projecting the known columns from a table.Create a new DSL select statement for a constant1
literal.Create a newSelectQuery
<R extends Record>
SelectQuery<R>selectQuery
(TableLike<R> table) Create a newSelectQuery
Create a new DSL select statement for a constant0
literal.TheSET
statement.TheSET
statement.setCatalog
(String catalog) TheSET CATALOG
statement.setCatalog
(Catalog catalog) TheSET CATALOG
statement.setCatalog
(Name catalog) TheSET CATALOG
statement.TheSET LOCAL
statement.TheSET LOCAL
statement.TheSET SCHEMA
statement.TheSET SCHEMA
statement.TheSET SCHEMA
statement.final Settings
settings()
The settings wrapped by this context.TheSTART TRANSACTION
statement.statements
(Collection<? extends Statement> statements) Wrap a collection of statements in an anonymous procedural block that does not wrap inBEGIN … END;
, unless explicitly needed.statements
(Statement... statements) Wrap a collection of statements in an anonymous procedural block that does not wrap inBEGIN … END;
, unless explicitly needed.toString()
void
transaction
(ContextTransactionalRunnable transactional) Run aContextTransactionalRunnable
in the context of thisDSLContext
's underlyingScope.configuration()
'sConfiguration.transactionProvider()
.void
transaction
(TransactionalRunnable transactional) Run aTransactionalRunnable
in the context of thisDSLContext
's underlyingScope.configuration()
'sConfiguration.transactionProvider()
.transactionAsync
(Executor executor, TransactionalRunnable transactional) Run aTransactionalRunnable
asynchronously.transactionAsync
(TransactionalRunnable transactional) Run aTransactionalRunnable
asynchronously.<T> Publisher<T>
transactionPublisher
(TransactionalPublishable<T> transactional) Run aTransactionalPublishable
reactively.<T> T
transactionResult
(ContextTransactionalCallable<T> transactional) Run aContextTransactionalRunnable
in the context of thisDSLContext
's underlyingScope.configuration()
'sConfiguration.transactionProvider()
, and return thetransactional
's outcome.<T> T
transactionResult
(TransactionalCallable<T> transactional) Run aTransactionalCallable
in the context of thisDSLContext
's underlyingScope.configuration()
'sConfiguration.transactionProvider()
, and return thetransactional
's outcome.<T> CompletionStage<T>
transactionResultAsync
(Executor executor, TransactionalCallable<T> transactional) Run aTransactionalCallable
asynchronously.<T> CompletionStage<T>
transactionResultAsync
(TransactionalCallable<T> transactional) Run aTransactionalCallable
asynchronously.TheTRUNCATE
statement.TheTRUNCATE
statement.truncate
(Collection<? extends Table<?>> table) TheTRUNCATE
statement.TheTRUNCATE
statement.TheTRUNCATE
statement.TheTRUNCATE
statement.<R extends Record>
TruncateIdentityStep<R>TheTRUNCATE
statement.truncateTable
(String table) TheTRUNCATE TABLE
statement.truncateTable
(String... table) TheTRUNCATE TABLE
statement.truncateTable
(Collection<? extends Table<?>> table) TheTRUNCATE TABLE
statement.truncateTable
(Name table) TheTRUNCATE TABLE
statement.truncateTable
(Name... table) TheTRUNCATE TABLE
statement.truncateTable
(Table<?>... table) TheTRUNCATE TABLE
statement.<R extends Record>
TruncateIdentityStep<R>truncateTable
(Table<R> table) TheTRUNCATE TABLE
statement.<R extends Record>
UpdateSetFirstStep<R>Create a new DSL update statement.<R extends Record>
UpdateQuery<R>updateQuery
(Table<R> table) Create a newUpdateQuery
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.with
(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.with
(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.with
(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.with
(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.with
(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.with
(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.with
(String alias, Collection<String> fieldAliases) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.with
(Collection<? extends CommonTableExpression<?>> tables) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.with
(CommonTableExpression<?>... tables) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.with
(Name alias, Collection<? extends Name> fieldAliases) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.with
(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.with
(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.with
(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.with
(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.with
(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.with
(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(String alias) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(String alias, String fieldAlias1) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(String alias, String... fieldAliases) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(String alias, String fieldAlias1, String fieldAlias2) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9, String fieldAlias10) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(String alias, Collection<String> fieldAliases) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(String alias, BiFunction<? super Field<?>, ? super Integer, ? extends String> fieldNameFunction) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(String alias, Function<? super Field<?>, ? extends String> fieldNameFunction) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(Collection<? extends CommonTableExpression<?>> tables) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(CommonTableExpression<?>... tables) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(Name alias) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(Name alias, Collection<? extends Name> fieldAliases) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(Name alias, Name fieldAlias1) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(Name alias, Name... fieldAliases) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(Name alias, Name fieldAlias1, Name fieldAlias2) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.withRecursive
(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6, Name fieldAlias7, Name fieldAlias8, Name fieldAlias9, Name fieldAlias10) Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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, creationTime, data, data, data, dialect, dsl, family, settings
-
Constructor Details
-
DefaultDSLContext
-
DefaultDSLContext
-
DefaultDSLContext
-
DefaultDSLContext
-
DefaultDSLContext
-
DefaultDSLContext
-
DefaultDSLContext
-
DefaultDSLContext
public DefaultDSLContext(ConnectionProvider connectionProvider, SQLDialect dialect, Settings settings) -
DefaultDSLContext
-
DefaultDSLContext
public DefaultDSLContext(io.r2dbc.spi.ConnectionFactory connectionFactory, SQLDialect dialect, Settings settings) -
DefaultDSLContext
-
-
Method Details
-
map
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 interfaceDSLContext
- Parameters:
schema
- A schema- Returns:
- The mapped schema
-
map
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 interfaceDSLContext
- Parameters:
table
- A table- Returns:
- The mapped table
-
parser
Description copied from interface:DSLContext
Access the parser API.- Specified by:
parser
in interfaceDSLContext
-
parsingConnection
Description copied from interface:DSLContext
A JDBC connection that runs each statement through theDSLContext.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, aPreparedStatement
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 forCacheType.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 fromConnectionProvider.acquire()
and must be released by callingConnection.close()
, which callsConnectionProvider.release(Connection)
.- Specified by:
parsingConnection
in interfaceDSLContext
-
parsingDataSource
Description copied from interface:DSLContext
A JDBC data source that runs each statement through theDSLContext.parser()
first, prior to re-generating and running the SQL.This simply wraps the
DSLContext.parsingConnection()
in aDataSource
.- Specified by:
parsingDataSource
in interfaceDSLContext
-
parsingConnectionFactory
public io.r2dbc.spi.ConnectionFactory parsingConnectionFactory()Description copied from interface:DSLContext
An R2DBCConnectionFactory
that runs each statement through theDSLContext.parser()
first, prior to re-generating and running the SQL.- Specified by:
parsingConnectionFactory
in interfaceDSLContext
-
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 interfaceDSLContext
-
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 aDataSource
.- Specified by:
diagnosticsDataSource
in interfaceDSLContext
-
migrations
Description copied from interface:DSLContext
The experimental migrations API.This is EXPERIMENTAL functionality and subject to change in future jOOQ versions.
- Specified by:
migrations
in interfaceDSLContext
-
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'sDatabaseMetaData
as obtained from yourConnectionProvider
.- Specified by:
meta
in interfaceDSLContext
- See Also:
-
meta
Description copied from interface:DSLContext
Access the database meta data from an explicit JDBCDatabaseMetaData
.- Specified by:
meta
in interfaceDSLContext
-
meta
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()
andDSLContext.meta(DatabaseMetaData)
.- Specified by:
meta
in interfaceDSLContext
-
meta
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()
andDSLContext.meta(DatabaseMetaData)
.- Specified by:
meta
in interfaceDSLContext
-
meta
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()
andDSLContext.meta(DatabaseMetaData)
.- Specified by:
meta
in interfaceDSLContext
-
meta
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()
andDSLContext.meta(DatabaseMetaData)
.- Specified by:
meta
in interfaceDSLContext
-
meta
Description copied from interface:DSLContext
Create meta data from a set of sources.This is convenience for wrapping all argument
String
s inSource
. The same set of content types are supported as inDSLContext.meta(Source...)
.- Specified by:
meta
in interfaceDSLContext
-
meta
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()
andDSLContext.meta(DatabaseMetaData)
.- Specified by:
meta
in interfaceDSLContext
- A set of DDL scripts, which will be parsed using
-
meta
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 interfaceDSLContext
-
informationSchema
Description copied from interface:DSLContext
Convenience method forMeta.informationSchema()
.- Specified by:
informationSchema
in interfaceDSLContext
- See Also:
-
informationSchema
Description copied from interface:DSLContext
Convenience method forMeta.informationSchema()
.- Specified by:
informationSchema
in interfaceDSLContext
- See Also:
-
informationSchema
Description copied from interface:DSLContext
Convenience method forMeta.informationSchema()
.- Specified by:
informationSchema
in interfaceDSLContext
- See Also:
-
informationSchema
Description copied from interface:DSLContext
Convenience method forMeta.informationSchema()
.- Specified by:
informationSchema
in interfaceDSLContext
- See Also:
-
informationSchema
Description copied from interface:DSLContext
Convenience method forMeta.informationSchema()
.- Specified by:
informationSchema
in interfaceDSLContext
- See Also:
-
informationSchema
Description copied from interface:DSLContext
Convenience method forMeta.informationSchema()
.- Specified by:
informationSchema
in interfaceDSLContext
- See Also:
-
explain
Description copied from interface:DSLContext
Run anEXPLAIN
statement in the database to estimate the cardinality of the query.- Specified by:
explain
in interfaceDSLContext
-
transactionResult
Description copied from interface:DSLContext
Run aContextTransactionalRunnable
in the context of thisDSLContext
's underlyingScope.configuration()
'sConfiguration.transactionProvider()
, and return thetransactional
'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, byThreadLocalTransactionProvider
automatically.- Specified by:
transactionResult
in interfaceDSLContext
- Parameters:
transactional
- The transactional code- Returns:
- The transactional outcome
-
transactionResult
Description copied from interface:DSLContext
Run aTransactionalCallable
in the context of thisDSLContext
's underlyingScope.configuration()
'sConfiguration.transactionProvider()
, and return thetransactional
's outcome.The argument transactional code should not capture any scope but derive its
Configuration
from theTransactionalCallable.run(Configuration)
argument in order to create new statements.- Specified by:
transactionResult
in interfaceDSLContext
- Parameters:
transactional
- The transactional code- Returns:
- The transactional outcome
-
transaction
Description copied from interface:DSLContext
Run aContextTransactionalRunnable
in the context of thisDSLContext
's underlyingScope.configuration()
'sConfiguration.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, byThreadLocalTransactionProvider
automatically.- Specified by:
transaction
in interfaceDSLContext
- Parameters:
transactional
- The transactional code
-
transaction
Description copied from interface:DSLContext
Run aTransactionalRunnable
in the context of thisDSLContext
's underlyingScope.configuration()
'sConfiguration.transactionProvider()
.The argument transactional code should not capture any scope but derive its
Configuration
from theTransactionalCallable.run(Configuration)
argument in order to create new statements.- Specified by:
transaction
in interfaceDSLContext
- Parameters:
transactional
- The transactional code
-
transactionAsync
Description copied from interface:DSLContext
Run aTransactionalRunnable
asynchronously.The
TransactionRunnable
is run in the context of thisDSLContext
's underlyingScope.configuration()
'sConfiguration.transactionProvider()
, and returns thetransactional
's outcome in a newCompletionStage
that is asynchronously completed by a task run by anExecutor
provided by the underlyingScope.configuration()
'sConfiguration.executorProvider()
.- Specified by:
transactionAsync
in interfaceDSLContext
- Parameters:
transactional
- The transactional code
-
transactionAsync
public CompletionStage<Void> transactionAsync(Executor executor, TransactionalRunnable transactional) Description copied from interface:DSLContext
Run aTransactionalRunnable
asynchronously.The
TransactionRunnable
is run in the context of thisDSLContext
's underlyingScope.configuration()
'sConfiguration.transactionProvider()
, and returns thetransactional
's outcome in a newCompletionStage
that is asynchronously completed by a task run by a givenExecutor
.- Specified by:
transactionAsync
in interfaceDSLContext
- Parameters:
transactional
- The transactional code
-
transactionResultAsync
Description copied from interface:DSLContext
Run aTransactionalCallable
asynchronously.The
TransactionCallable
is run in the context of thisDSLContext
's underlyingScope.configuration()
'sConfiguration.transactionProvider()
, and returns thetransactional
's outcome in a newCompletionStage
that is asynchronously completed by a task run by anExecutor
provided by the underlyingScope.configuration()
'sConfiguration.executorProvider()
.- Specified by:
transactionResultAsync
in interfaceDSLContext
- 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 aTransactionalCallable
asynchronously.The
TransactionCallable
is run in the context of thisDSLContext
's underlyingScope.configuration()
'sConfiguration.transactionProvider()
, and returns thetransactional
's outcome in a newCompletionStage
that is asynchronously completed by a task run by a givenExecutor
.- Specified by:
transactionResultAsync
in interfaceDSLContext
- Parameters:
transactional
- The transactional code- Returns:
- The transactional outcome
-
transactionPublisher
Description copied from interface:DSLContext
Run aTransactionalPublishable
reactively.- Specified by:
transactionPublisher
in interfaceDSLContext
- Parameters:
transactional
- The transactional code- Returns:
- The transactional outcome
-
connectionResult
Description copied from interface:DSLContext
Run aConnectionCallable
in the context of thisDSLContext
's underlyingScope.configuration()
'sConfiguration.connectionProvider()
.- Specified by:
connectionResult
in interfaceDSLContext
- Parameters:
callable
- The code running statements against theconnection
.- Returns:
- The outcome of the callable
-
connection
Description copied from interface:DSLContext
Run aConnectionRunnable
in the context of thisDSLContext
's underlyingScope.configuration()
'sConfiguration.connectionProvider()
.- Specified by:
connection
in interfaceDSLContext
- Parameters:
runnable
- The code running statements against theconnection
.
-
mockResult
Description copied from interface:DSLContext
Run aMockRunnable
in the context of thisDSLContext
's underlyingScope.configuration()
's, and of aMockDataProvider
and return themockable
's outcome.- Specified by:
mockResult
in interfaceDSLContext
-
mock
Description copied from interface:DSLContext
Run aMockRunnable
in the context of thisDSLContext
's underlyingScope.configuration()
's, and of aMockDataProvider
.- Specified by:
mock
in interfaceDSLContext
-
renderContext
Description copied from interface:DSLContext
Get a newRenderContext
for the context of thisDSLContext
.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 interfaceDSLContext
-
-
render
Description copied from interface:DSLContext
Render a QueryPart in the context of thisDSLContext
.This is the same as calling
renderContext().render(part)
- Specified by:
render
in interfaceDSLContext
- Parameters:
part
- TheQueryPart
to be rendered- Returns:
- The rendered SQL
-
renderNamedParams
Description copied from interface:DSLContext
Render a QueryPart in the context of thisDSLContext
, rendering bind variables as named parameters.This is the same as calling
renderContext().paramType(NAMED).render(part)
- Specified by:
renderNamedParams
in interfaceDSLContext
- Parameters:
part
- TheQueryPart
to be rendered- Returns:
- The rendered SQL
-
renderNamedOrInlinedParams
Description copied from interface:DSLContext
Render a QueryPart in the context of thisDSLContext
, 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 interfaceDSLContext
- Parameters:
part
- TheQueryPart
to be rendered- Returns:
- The rendered SQL
-
renderInlined
Description copied from interface:DSLContext
Render a QueryPart in the context of thisDSLContext
, inlining all bind variables.This is the same as calling
renderContext().inline(true).render(part)
- Specified by:
renderInlined
in interfaceDSLContext
- Parameters:
part
- TheQueryPart
to be rendered- Returns:
- The rendered SQL
-
extractBindValues
Description copied from interface:DSLContext
Retrieve the bind values that will be bound by a givenQueryPart
.The returned
List
is immutable. To modify bind values, useDSLContext.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 interfaceDSLContext
-
extractParams
Description copied from interface:DSLContext
Get aMap
of named parameters.The
Map
itself is immutable, but theParam
elements allow for modifying bind values on an existingQuery
(or any otherQueryPart
).Bind values created with
DSL.val(Object)
will have their bind index as name.- Specified by:
extractParams
in interfaceDSLContext
- See Also:
-
extractParam
Description copied from interface:DSLContext
Get a named parameter from aQueryPart
, provided its name.Bind values created with
DSL.val(Object)
will have their bind index as name.- Specified by:
extractParam
in interfaceDSLContext
- See Also:
-
bindContext
Description copied from interface:DSLContext
Get a newBindContext
for the context of thisDSLContext
.This will return an initialised bind context as such:
Context.declareFields()
== falseContext.declareTables()
== false
BindContext for JOOQ INTERNAL USE only. Avoid referencing it directly
- Specified by:
bindContext
in interfaceDSLContext
-
attach
Description copied from interface:DSLContext
Attach thisDSLContext
's underlyingScope.configuration()
to some attachables.- Specified by:
attach
in interfaceDSLContext
-
attach
Description copied from interface:DSLContext
Attach thisDSLContext
's underlyingScope.configuration()
to some attachables.- Specified by:
attach
in interfaceDSLContext
-
loadInto
Description copied from interface:DSLContext
Create a newLoader
object to load data from a CSV or XML source.- Specified by:
loadInto
in interfaceDSLContext
-
queries
Description copied from interface:DSLContext
Wrap a collection of queries.- Specified by:
queries
in interfaceDSLContext
- See Also:
-
queries
Description copied from interface:DSLContext
Wrap a collection of queries.- Specified by:
queries
in interfaceDSLContext
- See Also:
-
begin
Description copied from interface:DSLContext
Wrap a collection of statements in an anonymous procedural block.- Specified by:
begin
in interfaceDSLContext
- See Also:
-
begin
Description copied from interface:DSLContext
Wrap a collection of statements in an anoymous procedural block.- Specified by:
begin
in interfaceDSLContext
- See Also:
-
statements
Description copied from interface:DSLContext
Wrap a collection of statements in an anonymous procedural block that does not wrap inBEGIN … END;
, unless explicitly needed.- Specified by:
statements
in interfaceDSLContext
- See Also:
-
statements
Description copied from interface:DSLContext
Wrap a collection of statements in an anonymous procedural block that does not wrap inBEGIN … END;
, unless explicitly needed.- Specified by:
statements
in interfaceDSLContext
- See Also:
-
query
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- A query wrapping the plain SQL
- See Also:
-
query
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- A query wrapping the plain SQL
- See Also:
-
query
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 interfaceDSLContext
- Parameters:
sql
- The SQLbindings
- The bindings- Returns:
- A query wrapping the plain SQL
- See Also:
-
query
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 passQueryPart
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 interfaceDSLContext
- Parameters:
sql
- The SQL clause, containing {numbered placeholders} where query parts can be injectedparts
- TheQueryPart
objects that are rendered at the {numbered placeholder} locations- Returns:
- A query wrapping the plain SQL
- See Also:
-
fetch
Description copied from interface:DSLContext
Execute a new query holding plain SQL.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The results from the executed query. This will never be
null
. - See Also:
-
fetch
Description copied from interface:DSLContext
Execute a new query holding plain SQL.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The results from the executed query. This will never be
null
. - See Also:
-
fetch
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):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQLbindings
- The bindings- Returns:
- The results from the executed query. This will never be
null
. - See Also:
-
fetch
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 passQueryPart
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 interfaceDSLContext
- Parameters:
sql
- The SQL clause, containing {numbered placeholders} where query parts can be injectedparts
- TheQueryPart
objects that are rendered at the {numbered placeholder} locations- Returns:
- The results from the executed query. This will never be
null
. - See Also:
-
fetchLazy
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 executedPreparedStatement
and the associatedResultSet
. Data can be fetched (or iterated over) lazily, fetching records from theResultSet
one by one.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 runResultQuery.fetchLazy()
instead, or specifySettings.setFetchSize(Integer)
prior to calling this method.Client code is responsible for closing the cursor after use.
- Specified by:
fetchLazy
in interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The cursor. This will never be
null
. - See Also:
-
fetchLazy
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 executedPreparedStatement
and the associatedResultSet
. Data can be fetched (or iterated over) lazily, fetching records from theResultSet
one by one.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 runResultQuery.fetchLazy()
instead, or specifySettings.setFetchSize(Integer)
prior to calling this method.Client code is responsible for closing the cursor after use.
- Specified by:
fetchLazy
in interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The cursor. This will never be
null
. - See Also:
-
fetchLazy
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 executedPreparedStatement
and the associatedResultSet
. Data can be fetched (or iterated over) lazily, fetching records from theResultSet
one by one.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 runResultQuery.fetchLazy()
instead, or specifySettings.setFetchSize(Integer)
prior to calling this method.Client code is responsible for closing the cursor after use.
- Specified by:
fetchLazy
in interfaceDSLContext
- Parameters:
sql
- The SQLbindings
- The bindings- Returns:
- The cursor. This will never be
null
. - See Also:
-
fetchLazy
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 executedPreparedStatement
and the associatedResultSet
. Data can be fetched (or iterated over) lazily, fetching records from theResultSet
one by one.Unlike
DSLContext.fetchLazy(String, Object...)
, the SQL passed to this method should not contain any bind variables. Instead, you can passQueryPart
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 methodsDepending 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 runResultQuery.fetchLazy()
instead, or specifySettings.setFetchSize(Integer)
prior to calling this method.Client code is responsible for closing the cursor after use.
- Specified by:
fetchLazy
in interfaceDSLContext
- Parameters:
sql
- The SQL clause, containing {numbered placeholders} where query parts can be injectedparts
- TheQueryPart
objects that are rendered at the {numbered placeholder} locations- Returns:
- The cursor. This will never be
null
. - See Also:
-
fetchAsync
Description copied from interface:DSLContext
Fetch results in a newCompletionStage
.The result is asynchronously completed by a task running in an
Executor
provided by theScope.configuration()
'sConfiguration.executorProvider()
.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The completion stage. The completed result will never be
null
. - See Also:
-
fetchAsync
Description copied from interface:DSLContext
Fetch results in a newCompletionStage
.The result is asynchronously completed by a task running in an
Executor
provided by theScope.configuration()
'sConfiguration.executorProvider()
.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The completion stage. The completed result will never be
null
. - See Also:
-
fetchAsync
Description copied from interface:DSLContext
Fetch results in a newCompletionStage
.The result is asynchronously completed by a task running in an
Executor
provided by theScope.configuration()
'sConfiguration.executorProvider()
.There must be as many bind variables contained in the SQL, as passed in the bindings parameter
Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQLbindings
- The bindings- Returns:
- The completion stage. The completed result will never be
null
. - See Also:
-
fetchAsync
Description copied from interface:DSLContext
Fetch results in a newCompletionStage
.The result is asynchronously completed by a task running in an
Executor
provided by theScope.configuration()
'sConfiguration.executorProvider()
.Unlike
DSLContext.fetchLazy(String, Object...)
, the SQL passed to this method should not contain any bind variables. Instead, you can passQueryPart
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 interfaceDSLContext
- Parameters:
sql
- The SQL clause, containing {numbered placeholders} where query parts can be injectedparts
- TheQueryPart
objects that are rendered at the {numbered placeholder} locations- Returns:
- The completion stage. The completed result will never be
null
. - See Also:
-
fetchAsync
Description copied from interface:DSLContext
Fetch results in a newCompletionStage
that is asynchronously completed by a task running in the given executor.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The completion stage. The completed result will never be
null
. - See Also:
-
fetchAsync
Description copied from interface:DSLContext
Fetch results in a newCompletionStage
that is asynchronously completed by a task running in the given executor.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The completion stage. The completed result will never be
null
. - See Also:
-
fetchAsync
public CompletionStage<Result<Record>> fetchAsync(Executor executor, String sql, Object... bindings) Description copied from interface:DSLContext
Fetch results in a newCompletionStage
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):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQLbindings
- The bindings- Returns:
- The completion stage. The completed result will never be
null
. - See Also:
-
fetchAsync
public CompletionStage<Result<Record>> fetchAsync(Executor executor, String sql, QueryPart... parts) Description copied from interface:DSLContext
Fetch results in a newCompletionStage
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 passQueryPart
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 interfaceDSLContext
- Parameters:
sql
- The SQL clause, containing {numbered placeholders} where query parts can be injectedparts
- TheQueryPart
objects that are rendered at the {numbered placeholder} locations- Returns:
- The completion stage. The completed result will never be
null
. - See Also:
-
fetchStream
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 executedPreparedStatement
and the associatedResultSet
. Data can be fetched (or iterated over) lazily, fetching records from theResultSet
one by one.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 runResultQuery.fetchStream()
instead, or specifySettings.setFetchSize(Integer)
prior to calling this method.Client code is responsible for closing the stream after use.
- Specified by:
fetchStream
in interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The results from the executed query. This is never
null
, even if the database returns noResultSet
- See Also:
-
fetchStream
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 executedPreparedStatement
and the associatedResultSet
. Data can be fetched (or iterated over) lazily, fetching records from theResultSet
one by one.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 runResultQuery.fetchStream()
instead, or specifySettings.setFetchSize(Integer)
prior to calling this method.Client code is responsible for closing the stream after use.
- Specified by:
fetchStream
in interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The results from the executed query. This is never
null
, even if the database returns noResultSet
- See Also:
-
fetchStream
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 executedPreparedStatement
and the associatedResultSet
. Data can be fetched (or iterated over) lazily, fetching records from theResultSet
one by one.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 runResultQuery.fetchStream()
instead, or specifySettings.setFetchSize(Integer)
prior to calling this method.Client code is responsible for closing the stream after use.
- Specified by:
fetchStream
in interfaceDSLContext
- Parameters:
sql
- The SQLbindings
- The bindings- Returns:
- The results from the executed query. This is never
null
, even if the database returns noResultSet
- See Also:
-
fetchStream
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 executedPreparedStatement
and the associatedResultSet
. Data can be fetched (or iterated over) lazily, fetching records from theResultSet
one by one.Unlike
DSLContext.fetchStream(String, Object...)
, the SQL passed to this method should not contain any bind variables. Instead, you can passQueryPart
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 methodsDepending 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 runResultQuery.fetchStream()
instead, or specifySettings.setFetchSize(Integer)
prior to calling this method.Client code is responsible for closing the stream after use.
- Specified by:
fetchStream
in interfaceDSLContext
- Parameters:
sql
- The SQL clause, containing {numbered placeholders} where query parts can be injectedparts
- TheQueryPart
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 noResultSet
- See Also:
-
fetchMany
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The results. This will never be
null
. - See Also:
-
fetchMany
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The results. This will never be
null
. - See Also:
-
fetchMany
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 interfaceDSLContext
- Parameters:
sql
- The SQLbindings
- The bindings- Returns:
- The results. This will never be
null
. - See Also:
-
fetchMany
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 passQueryPart
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 interfaceDSLContext
- Parameters:
sql
- The SQL clause, containing {numbered placeholders} where query parts can be injectedparts
- TheQueryPart
objects that are rendered at the {numbered placeholder} locations- Returns:
- The results. This will never be
null
. - See Also:
-
fetchOne
Description copied from interface:DSLContext
Execute a new query holding plain SQL.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The record or
null
, if no record was found. - See Also:
-
fetchOne
Description copied from interface:DSLContext
Execute a new query holding plain SQL.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The record or
null
, if no record was found. - See Also:
-
fetchOne
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):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQLbindings
- The bindings- Returns:
- The record or
null
, if no record was found. - See Also:
-
fetchOne
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 passQueryPart
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 interfaceDSLContext
- Parameters:
sql
- The SQL clause, containing {numbered placeholders} where query parts can be injectedparts
- TheQueryPart
objects that are rendered at the {numbered placeholder} locations- Returns:
- The record or
null
, if no record was found. - See Also:
-
fetchSingle
Description copied from interface:DSLContext
Execute a new query holding plain SQL.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The record. This is never
null
. - See Also:
-
fetchSingle
Description copied from interface:DSLContext
Execute a new query holding plain SQL.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The record. This is never
null
. - See Also:
-
fetchSingle
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):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQLbindings
- The bindings- Returns:
- The record. This is never
null
. - See Also:
-
fetchSingle
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 passQueryPart
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 interfaceDSLContext
- Parameters:
sql
- The SQL clause, containing {numbered placeholders} where query parts can be injectedparts
- TheQueryPart
objects that are rendered at the {numbered placeholder} locations- Returns:
- The record. This is never
null
. - See Also:
-
fetchOptional
Description copied from interface:DSLContext
Execute a new query holding plain SQL.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The results from the executed query
- See Also:
-
fetchOptional
Description copied from interface:DSLContext
Execute a new query holding plain SQL.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The results from the executed query
- See Also:
-
fetchOptional
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):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQLbindings
- The bindings- Returns:
- The results from the executed query
- See Also:
-
fetchOptional
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 passQueryPart
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 interfaceDSLContext
- Parameters:
sql
- The SQL clause, containing {numbered placeholders} where query parts can be injectedparts
- TheQueryPart
objects that are rendered at the {numbered placeholder} locations- Returns:
- The results from the executed query
- See Also:
-
fetchValue
Description copied from interface:DSLContext
Execute a new query holding plain SQL.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The value or
null
, if no record was found. - See Also:
-
fetchValue
Description copied from interface:DSLContext
Execute a new query holding plain SQL.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The value or
null
, if no record was found. - See Also:
-
fetchValue
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):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQLbindings
- The bindings- Returns:
- The value or
null
, if no record was found. - See Also:
-
fetchValue
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 passQueryPart
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 interfaceDSLContext
- Parameters:
sql
- The SQL clause, containing {numbered placeholders} where query parts can be injectedparts
- TheQueryPart
objects that are rendered at the {numbered placeholder} locations- Returns:
- The value or
null
, if no record was found. - See Also:
-
fetchOptionalValue
Description copied from interface:DSLContext
Execute a new query holding plain SQL.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The result value from the executed query
- See Also:
-
fetchOptionalValue
Description copied from interface:DSLContext
Execute a new query holding plain SQL.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The result value from the executed query
- See Also:
-
fetchOptionalValue
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):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQLbindings
- The bindings- Returns:
- The results from the executed query
- See Also:
-
fetchOptionalValue
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 passQueryPart
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 interfaceDSLContext
- Parameters:
sql
- The SQL clause, containing {numbered placeholders} where query parts can be injectedparts
- TheQueryPart
objects that are rendered at the {numbered placeholder} locations- Returns:
- The results from the executed query
- See Also:
-
fetchValues
Description copied from interface:DSLContext
Execute a new query holding plain SQL.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The values. This will never be
null
. - See Also:
-
fetchValues
Description copied from interface:DSLContext
Execute a new query holding plain SQL.Example (Postgres):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The values. This will never be
null
. - See Also:
-
fetchValues
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):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQLbindings
- The bindings- Returns:
- The values. This will never be
null
. - See Also:
-
fetchValues
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 passQueryPart
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 interfaceDSLContext
- Parameters:
sql
- The SQL clause, containing {numbered placeholders} where query parts can be injectedparts
- TheQueryPart
objects that are rendered at the {numbered placeholder} locations- Returns:
- The values. This will never be
null
. - See Also:
-
execute
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The results from the executed query
- See Also:
-
execute
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- The results from the executed query
- See Also:
-
execute
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 interfaceDSLContext
- Parameters:
sql
- The SQLbindings
- The bindings- Returns:
- The results from the executed query
- See Also:
-
execute
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 passQueryPart
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 interfaceDSLContext
- Parameters:
sql
- The SQL clause, containing {numbered placeholders} where query parts can be injectedparts
- TheQueryPart
objects that are rendered at the {numbered placeholder} locations- Returns:
- The results from the executed query
- See Also:
-
resultQuery
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):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- An executable query
- See Also:
-
resultQuery
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):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQL- Returns:
- An executable query
- See Also:
-
resultQuery
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):
Example (SQLite):String sql = "FETCH ALL IN \"<unnamed cursor 1>\"";
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 interfaceDSLContext
- Parameters:
sql
- The SQLbindings
- The bindings- Returns:
- A query wrapping the plain SQL
- See Also:
-
resultQuery
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 passQueryPart
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 interfaceDSLContext
- Parameters:
sql
- The SQL clause, containing {numbered placeholders} where query parts can be injectedparts
- TheQueryPart
objects that are rendered at the {numbered placeholder} locations- Returns:
- A query wrapping the plain SQL
- See Also:
-
fetch
Description copied from interface:DSLContext
Fetch all data from a JDBCResultSet
and transform it to a jOOQResult
.After fetching all data, the JDBC ResultSet will be closed.
Use
DSLContext.fetchLazy(ResultSet)
, to fetch oneRecord
at a time, instead of load the entireResultSet
into a jOOQResult
at once.- Specified by:
fetch
in interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data from- Returns:
- The resulting jOOQ Result. This will never be
null
.
-
fetch
Description copied from interface:DSLContext
Fetch all data from a JDBCResultSet
and transform it to a jOOQResult
.After fetching all data, the JDBC ResultSet will be closed.
Use
DSLContext.fetchLazy(ResultSet)
, to fetch oneRecord
at a time, instead of load the entireResultSet
into a jOOQResult
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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromfields
- The fields to use in the desired output- Returns:
- The resulting jOOQ Result. This will never be
null
.
-
fetch
Description copied from interface:DSLContext
Fetch all data from a JDBCResultSet
and transform it to a jOOQResult
.After fetching all data, the JDBC ResultSet will be closed.
Use
DSLContext.fetchLazy(ResultSet)
, to fetch oneRecord
at a time, instead of load the entireResultSet
into a jOOQResult
at once.The additional
types
argument is used by jOOQ to coerce data types to the desired output- Specified by:
fetch
in interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromtypes
- The data types to use in the desired output- Returns:
- The resulting jOOQ Result. This will never be
null
.
-
fetch
Description copied from interface:DSLContext
Fetch all data from a JDBCResultSet
and transform it to a jOOQResult
.After fetching all data, the JDBC ResultSet will be closed.
Use
DSLContext.fetchLazy(ResultSet)
, to fetch oneRecord
at a time, instead of load the entireResultSet
into a jOOQResult
at once.The additional
types
argument is used by jOOQ to coerce data types to the desired output- Specified by:
fetch
in interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromtypes
- The data types to use in the desired output- Returns:
- The resulting jOOQ Result. This will never be
null
.
-
fetchOne
Description copied from interface:DSLContext
Fetch a record from a JDBCResultSet
and transform it to a jOOQRecord
.This will internally fetch all records and throw an exception if there was more than one resulting record.
- Specified by:
fetchOne
in interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data from- Returns:
- The record or
null
, if no record was found.
-
fetchOne
Description copied from interface:DSLContext
Fetch a record from a JDBCResultSet
and transform it to a jOOQRecord
.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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromfields
- The fields to use in the desired output- Returns:
- The record or
null
, if no record was found.
-
fetchOne
Description copied from interface:DSLContext
Fetch a record from a JDBCResultSet
and transform it to a jOOQRecord
.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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromtypes
- The data types to use in the desired output- Returns:
- The record or
null
, if no record was found.
-
fetchOne
Description copied from interface:DSLContext
Fetch a record from a JDBCResultSet
and transform it to a jOOQRecord
.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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromtypes
- The data types to use in the desired output- Returns:
- The record. This is never
null
.
-
fetchSingle
Description copied from interface:DSLContext
Fetch a record from a JDBCResultSet
and transform it to a jOOQRecord
.This will internally fetch all records and throw an exception if there was more than one resulting record.
- Specified by:
fetchSingle
in interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data from- Returns:
- The record or
null
, if no record was found.
-
fetchSingle
Description copied from interface:DSLContext
Fetch a record from a JDBCResultSet
and transform it to a jOOQRecord
.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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromfields
- The fields to use in the desired output- Returns:
- The record. This is never
null
.
-
fetchSingle
Description copied from interface:DSLContext
Fetch a record from a JDBCResultSet
and transform it to a jOOQRecord
.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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromtypes
- The data types to use in the desired output- Returns:
- The record. This is never
null
.
-
fetchSingle
Description copied from interface:DSLContext
Fetch a record from a JDBCResultSet
and transform it to a jOOQRecord
.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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromtypes
- The data types to use in the desired output- Returns:
- The record. This is never
null
.
-
fetchOptional
Description copied from interface:DSLContext
Fetch a record from a JDBCResultSet
and transform it to a jOOQRecord
.This will internally fetch all records and throw an exception if there was more than one resulting record.
- Specified by:
fetchOptional
in interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data from- Returns:
- The resulting jOOQ record
-
fetchOptional
Description copied from interface:DSLContext
Fetch a record from a JDBCResultSet
and transform it to a jOOQRecord
.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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromfields
- The fields to use in the desired output- Returns:
- The resulting jOOQ record
-
fetchOptional
Description copied from interface:DSLContext
Fetch a record from a JDBCResultSet
and transform it to a jOOQRecord
.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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromtypes
- The data types to use in the desired output- Returns:
- The resulting jOOQ record
-
fetchOptional
Description copied from interface:DSLContext
Fetch a record from a JDBCResultSet
and transform it to a jOOQRecord
.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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromtypes
- The data types to use in the desired output- Returns:
- The resulting jOOQ record
-
fetchValue
Description copied from interface:DSLContext
Fetch a record from a JDBCResultSet
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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data from- Returns:
- The value or
null
, if no record was found.
-
fetchValue
Description copied from interface:DSLContext
Fetch a record from a JDBCResultSet
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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromfield
- The field to use in the desired output- Returns:
- The value or
null
, if no record was found.
-
fetchValue
Description copied from interface:DSLContext
Fetch a record from a JDBCResultSet
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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromtype
- The data type to use in the desired output- Returns:
- The value or
null
, if no record was found.
-
fetchValue
Description copied from interface:DSLContext
Fetch a record from a JDBCResultSet
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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromtype
- The data types to use in the desired output- Returns:
- The value or
null
, if no record was found.
-
fetchOptionalValue
Description copied from interface:DSLContext
Fetch a record from a JDBCResultSet
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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data from- Returns:
- The resulting value
-
fetchOptionalValue
Description copied from interface:DSLContext
Fetch a record from a JDBCResultSet
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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromfield
- The field to use in the desired output- Returns:
- The resulting value
-
fetchOptionalValue
Description copied from interface:DSLContext
Fetch a record from a JDBCResultSet
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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromtype
- The data type to use in the desired output- Returns:
- The resulting value
-
fetchOptionalValue
Description copied from interface:DSLContext
Fetch a record from a JDBCResultSet
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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromtype
- The data types to use in the desired output- Returns:
- The resulting value
-
fetchValues
Description copied from interface:DSLContext
Fetch a result from a JDBCResultSet
and return the only contained column's values.- Specified by:
fetchValues
in interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data from- Returns:
- The values. This will never be
null
.
-
fetchValues
Description copied from interface:DSLContext
Fetch a result from a JDBCResultSet
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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromfield
- The field to use in the desired output- Returns:
- The values. This will never be
null
.
-
fetchValues
Description copied from interface:DSLContext
Fetch a result from a JDBCResultSet
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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromtype
- The data type to use in the desired output- Returns:
- The values. This will never be
null
.
-
fetchValues
Description copied from interface:DSLContext
Fetch a result from a JDBCResultSet
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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromtype
- The data types to use in the desired output- Returns:
- The values. This will never be
null
.
-
fetchLazy
Description copied from interface:DSLContext
Wrap a JDBCResultSet
into a jOOQCursor
.Use
DSLContext.fetch(ResultSet)
, to load the entireResultSet
into a jOOQResult
at once.- Specified by:
fetchLazy
in interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data from- Returns:
- The cursor. This will never be
null
.
-
fetchLazy
Description copied from interface:DSLContext
Wrap a JDBCResultSet
into a jOOQCursor
.Use
DSLContext.fetch(ResultSet)
, to load the entireResultSet
into a jOOQResult
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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromfields
- The fields to use in the desired output- Returns:
- The cursor. This will never be
null
.
-
fetchLazy
Description copied from interface:DSLContext
Wrap a JDBCResultSet
into a jOOQCursor
.Use
DSLContext.fetch(ResultSet)
, to load the entireResultSet
into a jOOQResult
at once.The additional
types
argument is used by jOOQ to coerce data types to the desired output- Specified by:
fetchLazy
in interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromtypes
- The data types to use in the desired output- Returns:
- The cursor. This will never be
null
.
-
fetchLazy
Description copied from interface:DSLContext
Wrap a JDBCResultSet
into a jOOQCursor
.Use
DSLContext.fetch(ResultSet)
, to load the entireResultSet
into a jOOQResult
at once.The additional
types
argument is used by jOOQ to coerce data types to the desired output- Specified by:
fetchLazy
in interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromtypes
- The data types to use in the desired output- Returns:
- The cursor. This will never be
null
.
-
fetchAsync
Description copied from interface:DSLContext
Fetch results in a newCompletionStage
.The result is asynchronously completed by a task running in an
Executor
provided by theScope.configuration()
'sConfiguration.executorProvider()
.- Specified by:
fetchAsync
in interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data from- Returns:
- The completion stage. The completed result will never be
null
.
-
fetchAsync
Description copied from interface:DSLContext
Fetch results in a newCompletionStage
.The result is asynchronously completed by a task running in an
Executor
provided by theScope.configuration()
'sConfiguration.executorProvider()
.The additional
fields
argument is used by jOOQ to coerce field names and data types to the desired output- Specified by:
fetchAsync
in interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromfields
- The fields to use in the desired output- Returns:
- The completion stage. The completed result will never be
null
.
-
fetchAsync
Description copied from interface:DSLContext
Fetch results in a newCompletionStage
.The result is asynchronously completed by a task running in an
Executor
provided by theScope.configuration()
'sConfiguration.executorProvider()
.The additional
types
argument is used by jOOQ to coerce data types to the desired output- Specified by:
fetchAsync
in interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromtypes
- The data types to use in the desired output- Returns:
- The completion stage. The completed result will never be
null
.
-
fetchAsync
Description copied from interface:DSLContext
Fetch results in a newCompletionStage
.The result is asynchronously completed by a task running in an
Executor
provided by theScope.configuration()
'sConfiguration.executorProvider()
.The additional
types
argument is used by jOOQ to coerce data types to the desired output- Specified by:
fetchAsync
in interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromtypes
- The data types to use in the desired output- Returns:
- The completion stage. The completed result will never be
null
.
-
fetchAsync
Description copied from interface:DSLContext
Fetch results in a newCompletionStage
that is asynchronously completed by a task running in the given executor.- Specified by:
fetchAsync
in interfaceDSLContext
- 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(Executor executor, ResultSet rs, Field<?>... fields) Description copied from interface:DSLContext
Fetch results in a newCompletionStage
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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromfields
- 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 newCompletionStage
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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromtypes
- 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 newCompletionStage
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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromtypes
- The data types to use in the desired output- Returns:
- The completion stage. The completed result will never be
null
.
-
fetchStream
Description copied from interface:DSLContext
Wrap a JDBCResultSet
into a jOOQStream
.Use
DSLContext.fetch(ResultSet)
, to load the entireResultSet
into a jOOQResult
at once.- Specified by:
fetchStream
in interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data from- Returns:
- The resulting stream
-
fetchStream
Description copied from interface:DSLContext
Wrap a JDBCResultSet
into a jOOQStream
.Use
DSLContext.fetch(ResultSet)
, to load the entireResultSet
into a jOOQResult
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 interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromfields
- The fields to use in the desired output- Returns:
- The resulting stream
-
fetchStream
Description copied from interface:DSLContext
Wrap a JDBCResultSet
into a jOOQStream
.Use
DSLContext.fetch(ResultSet)
, to load the entireResultSet
into a jOOQResult
at once.The additional
types
argument is used by jOOQ to coerce data types to the desired output- Specified by:
fetchStream
in interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromtypes
- The data types to use in the desired output- Returns:
- The resulting stream
-
fetchStream
Description copied from interface:DSLContext
Wrap a JDBCResultSet
into a jOOQStream
.Use
DSLContext.fetch(ResultSet)
, to load the entireResultSet
into a jOOQResult
at once.The additional
types
argument is used by jOOQ to coerce data types to the desired output- Specified by:
fetchStream
in interfaceDSLContext
- Parameters:
rs
- The JDBC ResultSet to fetch data fromtypes
- The data types to use in the desired output- Returns:
- The resulting stream
-
fetchFromTXT
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 interfaceDSLContext
- Parameters:
string
- The formatted string- Returns:
- The transformed result. This will never be
null
. - See Also:
-
fetchFromTXT
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:
This method will decode the above formatted string according to the following rules:+-----+-----+--------------------------+ |COL1 |COL2 |COL3 containing whitespace| +-----+-----+--------------------------+ |val1 |1 |some text | |val2 | 2 | more text | +-----+-----+--------------------------+
- 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)
whereN = 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:
This method will decode the above formatted string according to the following rules:COL1 COL2 COL3 containing whitespace ----- ---- -------------------------- val1 1 some text val2 2 more text
- 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)
whereN = 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 interfaceDSLContext
- Parameters:
string
- The formatted stringnullLiteral
- The string literal to be used asnull
value.- Returns:
- The transformed result. This will never be
null
.
-
fetchFromHTML
Description copied from interface:DSLContext
Convert an HTML table into a jOOQResult
.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 interfaceDSLContext
- Parameters:
string
- The HTML-formatted string.- Returns:
- The transformed result. This will never be
null
.
- 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
-
fetchFromCSV
Description copied from interface:DSLContext
Fetch all data from a CSV string.This is the same as calling
fetchFromCSV(string, ',')
and the inverse of callingFormattable.formatCSV()
. The first row of the CSV data is required to hold field name information. Subsequent rows may contain data, which is interpreted asString
. Use the various conversion methods to retrieve other data types from theResult
: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 emptyStrings
- Specified by:
fetchFromCSV
in interfaceDSLContext
- Parameters:
string
- The CSV string- Returns:
- The transformed result. This will never be
null
. - See Also:
-
fetchFromCSV
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 asString
. Use the various conversion methods to retrieve other data types from theResult
: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 emptyStrings
- Specified by:
fetchFromCSV
in interfaceDSLContext
- Parameters:
string
- The CSV stringdelimiter
- The delimiter to expect between records- Returns:
- The transformed result. This will never be
null
. - See Also:
-
fetchFromCSV
Description copied from interface:DSLContext
Fetch all data from a CSV string.This is the same as calling
fetchFromCSV(string, ',')
and the inverse of callingFormattable.formatCSV(boolean)
. Rows may contain data, which is interpreted asString
. Use the various conversion methods to retrieve other data types from theResult
: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 emptyStrings
- Specified by:
fetchFromCSV
in interfaceDSLContext
- Parameters:
string
- The CSV stringheader
- Whether to parse the first line as a CSV header line- Returns:
- The transformed result. This will never be
null
. - See Also:
-
fetchFromCSV
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 asString
. Use the various conversion methods to retrieve other data types from theResult
: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 emptyStrings
- Specified by:
fetchFromCSV
in interfaceDSLContext
- Parameters:
string
- The CSV stringheader
- Whether to parse the first line as a CSV header linedelimiter
- The delimiter to expect between records- Returns:
- The transformed result. This will never be
null
. - See Also:
-
fetchFromJSON
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 theResult
:-
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 emptyStrings
- Specified by:
fetchFromJSON
in interfaceDSLContext
- Parameters:
string
- The JSON string- Returns:
- The transformed result. This will never be
null
.
-
-
fetchFromXML
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 theResult
:-
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 emptyStrings
- Specified by:
fetchFromXML
in interfaceDSLContext
- Parameters:
string
- The XML string- Returns:
- The transformed result. This will never be
null
.
-
-
fetchFromStringData
Description copied from interface:DSLContext
Fetch all data from a list of strings.This is used by methods such as
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 withnull
.- Specified by:
fetchFromStringData
in interfaceDSLContext
- Parameters:
strings
- The data to be transformed into aResult
- Returns:
- The transformed result. This will never be
null
. - See Also:
-
fetchFromStringData
Description copied from interface:DSLContext
Fetch all data from a list of strings.This is used by methods such as
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 withnull
.- Specified by:
fetchFromStringData
in interfaceDSLContext
- Parameters:
strings
- The data to be transformed into aResult
- Returns:
- The transformed result. This will never be
null
.
-
fetchFromStringData
Description copied from interface:DSLContext
Fetch all data from a list of strings.This is used by methods such as
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 withnull
.- Specified by:
fetchFromStringData
in interfaceDSLContext
- Parameters:
strings
- The data to be transformed into aResult
header
- Whether to interpret the first line as a set of column names.- Returns:
- The transformed result. This will never be
null
.
-
with
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String)
for strictly non-recursive CTE andDSLContext.withRecursive(String)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
with
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
with
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
with
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(Name)
for strictly non-recursive CTE andDSLContext.withRecursive(Name)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
with
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(Name, Name...)
for strictly non-recursive CTE andDSLContext.withRecursive(Name, Name...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
with
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(Name, Name...)
for strictly non-recursive CTE andDSLContext.withRecursive(Name, Name...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
with
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.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'sSelect
columns as input.- Specified by:
with
in interfaceDSLContext
-
with
public WithAsStep with(String alias, BiFunction<? super Field<?>, ? super Integer, ? extends String> fieldNameFunction) Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.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'sSelect
columns and their column indexes as input.- Specified by:
with
in interfaceDSLContext
-
with
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
with
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
with
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
with
public WithAsStep4 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4) Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
with
public WithAsStep5 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5) Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
with
public WithAsStep6 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6) Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
with
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
with
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
with
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
with
public WithAsStep4 with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4) Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
with
public WithAsStep5 with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5) Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
with
public WithAsStep6 with(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6) Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
with
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.Reusable
CommonTableExpression
types can be constructed throughThe
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 useDSLContext.with(CommonTableExpression...)
for strictly non-recursive CTE andDSLContext.withRecursive(CommonTableExpression...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
with
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.Reusable
CommonTableExpression
types can be constructed throughThe
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 useDSLContext.with(CommonTableExpression...)
for strictly non-recursive CTE andDSLContext.withRecursive(CommonTableExpression...)
for strictly recursive CTE.- Specified by:
with
in interfaceDSLContext
-
withRecursive
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String)
for strictly non-recursive CTE andDSLContext.withRecursive(String)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
withRecursive
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
withRecursive
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
withRecursive
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(Name)
for strictly non-recursive CTE andDSLContext.withRecursive(Name)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
withRecursive
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(Name, Name...)
for strictly non-recursive CTE andDSLContext.withRecursive(Name, Name...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
withRecursive
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(Name, Name...)
for strictly non-recursive CTE andDSLContext.withRecursive(Name, Name...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
withRecursive
public WithAsStep withRecursive(String alias, Function<? super Field<?>, ? extends String> fieldNameFunction) Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.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'sSelect
columns as input.- Specified by:
withRecursive
in interfaceDSLContext
-
withRecursive
public WithAsStep withRecursive(String alias, BiFunction<? super Field<?>, ? super Integer, ? extends String> fieldNameFunction) Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.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'sSelect
columns and their column indexes as input.- Specified by:
withRecursive
in interfaceDSLContext
-
withRecursive
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
withRecursive
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
withRecursive
public WithAsStep3 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3) Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
withRecursive
public WithAsStep4 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4) Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
withRecursive
public WithAsStep5 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5) Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
withRecursive
public WithAsStep6 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6) Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
withRecursive
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
withRecursive
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
withRecursive
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
withRecursive
public WithAsStep4 withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4) Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
withRecursive
public WithAsStep5 withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5) Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
withRecursive
public WithAsStep6 withRecursive(Name alias, Name fieldAlias1, Name fieldAlias2, Name fieldAlias3, Name fieldAlias4, Name fieldAlias5, Name fieldAlias6) Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
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 aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.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 useDSLContext.with(String, String...)
for strictly non-recursive CTE andDSLContext.withRecursive(String, String...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
withRecursive
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.Reusable
CommonTableExpression
types can be constructed throughThe
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 useDSLContext.with(CommonTableExpression...)
for strictly non-recursive CTE andDSLContext.withRecursive(CommonTableExpression...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
withRecursive
Description copied from interface:DSLContext
Create aWITH
clause to supply subsequentSELECT
,UPDATE
,INSERT
,DELETE
, andMERGE
statements withCommonTableExpression
s.Reusable
CommonTableExpression
types can be constructed throughThe
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 useDSLContext.with(CommonTableExpression...)
for strictly non-recursive CTE andDSLContext.withRecursive(CommonTableExpression...)
for strictly recursive CTE.- Specified by:
withRecursive
in interfaceDSLContext
-
selectFrom
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 usingDSL.table(String)
), thenSELECT *
is projected.Example:
SELECT table.col1, table.col2 FROM table
- Specified by:
selectFrom
in interfaceDSLContext
-
selectFrom
Description copied from interface:DSLContext
Create a new DSL select statement, projecting*
.Without knowing any columns from the argument table (see
DSLContext.selectFrom(TableLike)
), this will projectSELECT *
.Example:
SELECT * FROM table
- Specified by:
selectFrom
in interfaceDSLContext
- See Also:
-
selectFrom
Description copied from interface:DSLContext
Create a new DSL select statement, projecting*
.Without knowing any columns from the argument table (see
DSLContext.selectFrom(TableLike)
), this will projectSELECT *
.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 interfaceDSLContext
- See Also:
-
selectFrom
Description copied from interface:DSLContext
Create a new DSL select statement, projecting*
.Without knowing any columns from the argument table (see
DSLContext.selectFrom(TableLike)
), this will projectSELECT *
.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 interfaceDSLContext
- See Also:
-
selectFrom
Description copied from interface:DSLContext
Create a new DSL select statement, projecting*
.Without knowing any columns from the argument table (see
DSLContext.selectFrom(TableLike)
), this will projectSELECT *
.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 interfaceDSLContext
- See Also:
-
selectFrom
Description copied from interface:DSLContext
Create a new DSL select statement, projecting*
.Without knowing any columns from the argument table (see
DSLContext.selectFrom(TableLike)
), this will projectSELECT *
.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 interfaceDSLContext
- See Also:
-
select
Description copied from interface:DSLContext
Create a new DSL select statement.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
- Renders
-
select
Description copied from interface:DSLContext
Create a new DSL select statement.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
- Renders
-
select
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 byField.in(Select)
,Field.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
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 byRow2.in(Select)
,Row2.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
select
public <T1,T2, SelectSelectStep<Record3<T1,T3> T2, selectT3>> (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 byRow3.in(Select)
,Row3.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
select
public <T1,T2, SelectSelectStep<Record4<T1,T3, T4> T2, selectT3, T4>> (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 byRow4.in(Select)
,Row4.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
select
public <T1,T2, SelectSelectStep<Record5<T1,T3, T4, T5> T2, selectT3, T4, T5>> (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 byRow5.in(Select)
,Row5.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
select
public <T1,T2, SelectSelectStep<Record6<T1,T3, T4, T5, T6> T2, selectT3, T4, T5, T6>> (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 byRow6.in(Select)
,Row6.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
select
public <T1,T2, SelectSelectStep<Record7<T1,T3, T4, T5, T6, T7> T2, selectT3, T4, T5, T6, T7>> (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 byRow7.in(Select)
,Row7.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
select
public <T1,T2, SelectSelectStep<Record8<T1,T3, T4, T5, T6, T7, T8> T2, selectT3, T4, T5, T6, T7, T8>> (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 byRow8.in(Select)
,Row8.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
select
public <T1,T2, SelectSelectStep<Record9<T1,T3, T4, T5, T6, T7, T8, T9> T2, selectT3, T4, T5, T6, T7, T8, T9>> (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 byRow9.in(Select)
,Row9.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
select
public <T1,T2, SelectSelectStep<Record10<T1,T3, T4, T5, T6, T7, T8, T9, T10> T2, selectT3, T4, T5, T6, T7, T8, T9, T10>> (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 byRow10.in(Select)
,Row10.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
select
public <T1,T2, SelectSelectStep<Record11<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11> T2, selectT3, T4, T5, T6, T7, T8, T9, T10, T11>> (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 byRow11.in(Select)
,Row11.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
select
public <T1,T2, SelectSelectStep<Record12<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12> T2, selectT3, T4, T5, T6, T7, T8, T9, T10, T11, T12>> (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 byRow12.in(Select)
,Row12.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
select
public <T1,T2, SelectSelectStep<Record13<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13> T2, selectT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13>> (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 byRow13.in(Select)
,Row13.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
select
public <T1,T2, SelectSelectStep<Record14<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14> T2, selectT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14>> (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 byRow14.in(Select)
,Row14.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
select
public <T1,T2, SelectSelectStep<Record15<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15> T2, selectT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15>> (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 byRow15.in(Select)
,Row15.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
select
public <T1,T2, SelectSelectStep<Record16<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16> T2, selectT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16>> (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 byRow16.in(Select)
,Row16.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
select
public <T1,T2, SelectSelectStep<Record17<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17> T2, selectT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17>> (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 byRow17.in(Select)
,Row17.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
select
public <T1,T2, SelectSelectStep<Record18<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18> T2, selectT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18>> (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 byRow18.in(Select)
,Row18.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
select
public <T1,T2, SelectSelectStep<Record19<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19> T2, selectT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19>> (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 byRow19.in(Select)
,Row19.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
select
public <T1,T2, SelectSelectStep<Record20<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20> T2, selectT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20>> (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 byRow20.in(Select)
,Row20.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
select
public <T1,T2, SelectSelectStep<Record21<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21> T2, selectT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21>> (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 byRow21.in(Select)
,Row21.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
select
public <T1,T2, SelectSelectStep<Record22<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21, T22> T2, selectT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21, T22>> (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 byRow22.in(Select)
,Row22.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectDistinct
Description copied from interface:DSLContext
Create a new DSL select statement.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
- Renders
-
selectDistinct
Description copied from interface:DSLContext
Create a new DSL select statement.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
- Renders
-
selectDistinct
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 byField.in(Select)
,Field.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
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 byRow2.in(Select)
,Row2.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectDistinct
public <T1,T2, SelectSelectStep<Record3<T1,T3> T2, selectDistinctT3>> (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 byRow3.in(Select)
,Row3.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectDistinct
public <T1,T2, SelectSelectStep<Record4<T1,T3, T4> T2, selectDistinctT3, T4>> (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 byRow4.in(Select)
,Row4.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectDistinct
public <T1,T2, SelectSelectStep<Record5<T1,T3, T4, T5> T2, selectDistinctT3, T4, T5>> (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 byRow5.in(Select)
,Row5.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectDistinct
public <T1,T2, SelectSelectStep<Record6<T1,T3, T4, T5, T6> T2, selectDistinctT3, T4, T5, T6>> (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 byRow6.in(Select)
,Row6.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectDistinct
public <T1,T2, SelectSelectStep<Record7<T1,T3, T4, T5, T6, T7> T2, selectDistinctT3, T4, T5, T6, T7>> (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 byRow7.in(Select)
,Row7.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectDistinct
public <T1,T2, SelectSelectStep<Record8<T1,T3, T4, T5, T6, T7, T8> T2, selectDistinctT3, T4, T5, T6, T7, T8>> (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 byRow8.in(Select)
,Row8.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectDistinct
public <T1,T2, SelectSelectStep<Record9<T1,T3, T4, T5, T6, T7, T8, T9> T2, selectDistinctT3, T4, T5, T6, T7, T8, T9>> (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 byRow9.in(Select)
,Row9.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectDistinct
public <T1,T2, SelectSelectStep<Record10<T1,T3, T4, T5, T6, T7, T8, T9, T10> T2, selectDistinctT3, T4, T5, T6, T7, T8, T9, T10>> (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 byRow10.in(Select)
,Row10.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectDistinct
public <T1,T2, SelectSelectStep<Record11<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11> T2, selectDistinctT3, T4, T5, T6, T7, T8, T9, T10, T11>> (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 byRow11.in(Select)
,Row11.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectDistinct
public <T1,T2, SelectSelectStep<Record12<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12> T2, selectDistinctT3, T4, T5, T6, T7, T8, T9, T10, T11, T12>> (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 byRow12.in(Select)
,Row12.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectDistinct
public <T1,T2, SelectSelectStep<Record13<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13> T2, selectDistinctT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13>> (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 byRow13.in(Select)
,Row13.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectDistinct
public <T1,T2, SelectSelectStep<Record14<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14> T2, selectDistinctT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14>> (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 byRow14.in(Select)
,Row14.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectDistinct
public <T1,T2, SelectSelectStep<Record15<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15> T2, selectDistinctT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15>> (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 byRow15.in(Select)
,Row15.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectDistinct
public <T1,T2, SelectSelectStep<Record16<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16> T2, selectDistinctT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16>> (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 byRow16.in(Select)
,Row16.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectDistinct
public <T1,T2, SelectSelectStep<Record17<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17> T2, selectDistinctT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17>> (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 byRow17.in(Select)
,Row17.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectDistinct
public <T1,T2, SelectSelectStep<Record18<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18> T2, selectDistinctT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18>> (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 byRow18.in(Select)
,Row18.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectDistinct
public <T1,T2, SelectSelectStep<Record19<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19> T2, selectDistinctT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19>> (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 byRow19.in(Select)
,Row19.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectDistinct
public <T1,T2, SelectSelectStep<Record20<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20> T2, selectDistinctT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20>> (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 byRow20.in(Select)
,Row20.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectDistinct
public <T1,T2, SelectSelectStep<Record21<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21> T2, selectDistinctT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21>> (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 byRow21.in(Select)
,Row21.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectDistinct
public <T1,T2, SelectSelectStep<Record22<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21, T22> T2, selectDistinctT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21, T22>> (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 byRow22.in(Select)
,Row22.equal(Select)
and other predicate building methods taking subselect arguments.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectZero
Description copied from interface:DSLContext
Create a new DSL select statement for a constant0
literal.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectOne
Description copied from interface:DSLContext
Create a new DSL select statement for a constant1
literal.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectCount
Description copied from interface:DSLContext
Create a new DSL select statement forCOUNT(*)
.This creates an attached, renderable and executable
SELECT
statement from thisDSLContext
. If you don't need to render or execute thisSELECT
statement (e.g. because you want to create a subselect), consider using the staticDSL.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 interfaceDSLContext
- See Also:
-
selectQuery
Description copied from interface:DSLContext
Create a newSelectQuery
- Specified by:
selectQuery
in interfaceDSLContext
-
selectQuery
Description copied from interface:DSLContext
Create a newSelectQuery
- Specified by:
selectQuery
in interfaceDSLContext
- Parameters:
table
- The table to select data from- Returns:
- The new
SelectQuery
-
insertQuery
Description copied from interface:DSLContext
Create a newInsertQuery
- Specified by:
insertQuery
in interfaceDSLContext
- Parameters:
into
- The table to insert data into- Returns:
- The new
InsertQuery
-
insertInto
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'sSET 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 interfaceDSLContext
-
insertInto
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 interfaceDSLContext
-
insertInto
public <R extends Record,T1, InsertValuesStep2<R,T2> T1, insertIntoT2> (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 interfaceDSLContext
-
insertInto
public <R extends Record,T1, InsertValuesStep3<R,T2, T3> T1, insertIntoT2, T3> (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 interfaceDSLContext
-
insertInto
public <R extends Record,T1, InsertValuesStep4<R,T2, T3, T4> T1, insertIntoT2, T3, T4> (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 interfaceDSLContext
-
insertInto
public <R extends Record,T1, InsertValuesStep5<R,T2, T3, T4, T5> T1, insertIntoT2, T3, T4, T5> (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 interfaceDSLContext
-
insertInto
public <R extends Record,T1, InsertValuesStep6<R,T2, T3, T4, T5, T6> T1, insertIntoT2, T3, T4, T5, T6> (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 interfaceDSLContext
-
insertInto
public <R extends Record,T1, InsertValuesStep7<R,T2, T3, T4, T5, T6, T7> T1, insertIntoT2, T3, T4, T5, T6, T7> (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 interfaceDSLContext
-
insertInto
public <R extends Record,T1, InsertValuesStep8<R,T2, T3, T4, T5, T6, T7, T8> T1, insertIntoT2, T3, T4, T5, T6, T7, T8> (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 interfaceDSLContext
-
insertInto
public <R extends Record,T1, InsertValuesStep9<R,T2, T3, T4, T5, T6, T7, T8, T9> T1, insertIntoT2, T3, T4, T5, T6, T7, T8, T9> (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 interfaceDSLContext
-
insertInto
public <R extends Record,T1, InsertValuesStep10<R,T2, T3, T4, T5, T6, T7, T8, T9, T10> T1, insertIntoT2, T3, T4, T5, T6, T7, T8, T9, T10> (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 interfaceDSLContext
-
insertInto
public <R extends Record,T1, InsertValuesStep11<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11> T1, insertIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11> (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 interfaceDSLContext
-
insertInto
public <R extends Record,T1, InsertValuesStep12<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12> T1, insertIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12> (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 interfaceDSLContext
-
insertInto
public <R extends Record,T1, InsertValuesStep13<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13> T1, insertIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13> (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 interfaceDSLContext
-
insertInto
public <R extends Record,T1, InsertValuesStep14<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14> T1, insertIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14> (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 interfaceDSLContext
-
insertInto
public <R extends Record,T1, InsertValuesStep15<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15> T1, insertIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15> (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 interfaceDSLContext
-
insertInto
public <R extends Record,T1, InsertValuesStep16<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16> T1, insertIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16> (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 interfaceDSLContext
-
insertInto
public <R extends Record,T1, InsertValuesStep17<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17> T1, insertIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17> (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 interfaceDSLContext
-
insertInto
public <R extends Record,T1, InsertValuesStep18<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18> T1, insertIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18> (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 interfaceDSLContext
-
insertInto
public <R extends Record,T1, InsertValuesStep19<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19> T1, insertIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19> (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 interfaceDSLContext
-
insertInto
public <R extends Record,T1, InsertValuesStep20<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20> T1, insertIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20> (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 interfaceDSLContext
-
insertInto
public <R extends Record,T1, InsertValuesStep21<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21> T1, insertIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21> (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 interfaceDSLContext
-
insertInto
public <R extends Record,T1, InsertValuesStep22<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21, T22> T1, insertIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21, T22> (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 interfaceDSLContext
-
insertInto
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 interfaceDSLContext
-
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 interfaceDSLContext
-
updateQuery
Description copied from interface:DSLContext
Create a newUpdateQuery
- Specified by:
updateQuery
in interfaceDSLContext
- Parameters:
table
- The table to update data into- Returns:
- The new
UpdateQuery
-
update
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 interfaceDSLContext
-
mergeInto
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 interfaceDSLContext
-
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, viamergeInto(Table)
Description copied from interface:DSLContext
- Specified by:
mergeInto
in interfaceDSLContext
- See Also:
-
mergeInto
@Deprecated(forRemoval=true, since="3.14") public <R extends Record,T1, MergeKeyStep2<R,T2> T1, mergeIntoT2> (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, viamergeInto(Table)
Description copied from interface:DSLContext
- Specified by:
mergeInto
in interfaceDSLContext
- See Also:
-
mergeInto
@Deprecated(forRemoval=true, since="3.14") public <R extends Record,T1, MergeKeyStep3<R,T2, T3> T1, mergeIntoT2, T3> (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, viamergeInto(Table)
Description copied from interface:DSLContext
- Specified by:
mergeInto
in interfaceDSLContext
- See Also:
-
mergeInto
@Deprecated(forRemoval=true, since="3.14") public <R extends Record,T1, MergeKeyStep4<R,T2, T3, T4> T1, mergeIntoT2, T3, T4> (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, viamergeInto(Table)
Description copied from interface:DSLContext
- Specified by:
mergeInto
in interfaceDSLContext
- See Also:
-
mergeInto
@Deprecated(forRemoval=true, since="3.14") public <R extends Record,T1, MergeKeyStep5<R,T2, T3, T4, T5> T1, mergeIntoT2, T3, T4, T5> (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, viamergeInto(Table)
Description copied from interface:DSLContext
- Specified by:
mergeInto
in interfaceDSLContext
- See Also:
-
mergeInto
@Deprecated(forRemoval=true, since="3.14") public <R extends Record,T1, MergeKeyStep6<R,T2, T3, T4, T5, T6> T1, mergeIntoT2, T3, T4, T5, T6> (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, viamergeInto(Table)
Description copied from interface:DSLContext
- Specified by:
mergeInto
in interfaceDSLContext
- See Also:
-
mergeInto
@Deprecated(forRemoval=true, since="3.14") public <R extends Record,T1, MergeKeyStep7<R,T2, T3, T4, T5, T6, T7> T1, mergeIntoT2, T3, T4, T5, T6, T7> (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, viamergeInto(Table)
Description copied from interface:DSLContext
- Specified by:
mergeInto
in interfaceDSLContext
- See Also:
-
mergeInto
@Deprecated(forRemoval=true, since="3.14") public <R extends Record,T1, MergeKeyStep8<R,T2, T3, T4, T5, T6, T7, T8> T1, mergeIntoT2, T3, T4, T5, T6, T7, T8> (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, viamergeInto(Table)
Description copied from interface:DSLContext
- Specified by:
mergeInto
in interfaceDSLContext
- See Also:
-
mergeInto
@Deprecated(forRemoval=true, since="3.14") public <R extends Record,T1, MergeKeyStep9<R,T2, T3, T4, T5, T6, T7, T8, T9> T1, mergeIntoT2, T3, T4, T5, T6, T7, T8, T9> (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, viamergeInto(Table)
Description copied from interface:DSLContext
- Specified by:
mergeInto
in interfaceDSLContext
- See Also:
-
mergeInto
@Deprecated(forRemoval=true, since="3.14") public <R extends Record,T1, MergeKeyStep10<R,T2, T3, T4, T5, T6, T7, T8, T9, T10> T1, mergeIntoT2, T3, T4, T5, T6, T7, T8, T9, T10> (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, viamergeInto(Table)
Description copied from interface:DSLContext
- Specified by:
mergeInto
in interfaceDSLContext
- See Also:
-
mergeInto
@Deprecated(forRemoval=true, since="3.14") public <R extends Record,T1, MergeKeyStep11<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11> T1, mergeIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11> (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, viamergeInto(Table)
Description copied from interface:DSLContext
- Specified by:
mergeInto
in interfaceDSLContext
- See Also:
-
mergeInto
@Deprecated(forRemoval=true, since="3.14") public <R extends Record,T1, MergeKeyStep12<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12> T1, mergeIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12> (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, viamergeInto(Table)
Description copied from interface:DSLContext
- Specified by:
mergeInto
in interfaceDSLContext
- See Also:
-
mergeInto
@Deprecated(forRemoval=true, since="3.14") public <R extends Record,T1, MergeKeyStep13<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13> T1, mergeIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13> (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, viamergeInto(Table)
Description copied from interface:DSLContext
- Specified by:
mergeInto
in interfaceDSLContext
- See Also:
-
mergeInto
@Deprecated(forRemoval=true, since="3.14") public <R extends Record,T1, MergeKeyStep14<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14> T1, mergeIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14> (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, viamergeInto(Table)
Description copied from interface:DSLContext
- Specified by:
mergeInto
in interfaceDSLContext
- See Also:
-
mergeInto
@Deprecated(forRemoval=true, since="3.14") public <R extends Record,T1, MergeKeyStep15<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15> T1, mergeIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15> (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, viamergeInto(Table)
Description copied from interface:DSLContext
- Specified by:
mergeInto
in interfaceDSLContext
- See Also:
-
mergeInto
@Deprecated(forRemoval=true, since="3.14") public <R extends Record,T1, MergeKeyStep16<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16> T1, mergeIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16> (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, viamergeInto(Table)
Description copied from interface:DSLContext
- Specified by:
mergeInto
in interfaceDSLContext
- See Also:
-
mergeInto
@Deprecated(forRemoval=true, since="3.14") public <R extends Record,T1, MergeKeyStep17<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17> T1, mergeIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17> (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, viamergeInto(Table)
Description copied from interface:DSLContext
- Specified by:
mergeInto
in interfaceDSLContext
- See Also:
-
mergeInto
@Deprecated(forRemoval=true, since="3.14") public <R extends Record,T1, MergeKeyStep18<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18> T1, mergeIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18> (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, viamergeInto(Table)
Description copied from interface:DSLContext
- Specified by:
mergeInto
in interfaceDSLContext
- See Also:
-
mergeInto
@Deprecated(forRemoval=true, since="3.14") public <R extends Record,T1, MergeKeyStep19<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19> T1, mergeIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19> (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, viamergeInto(Table)
Description copied from interface:DSLContext
- Specified by:
mergeInto
in interfaceDSLContext
- See Also:
-
mergeInto
@Deprecated(forRemoval=true, since="3.14") public <R extends Record,T1, MergeKeyStep20<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20> T1, mergeIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20> (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, viamergeInto(Table)
Description copied from interface:DSLContext
- Specified by:
mergeInto
in interfaceDSLContext
- See Also:
-
mergeInto
@Deprecated(forRemoval=true, since="3.14") public <R extends Record,T1, MergeKeyStep21<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21> T1, mergeIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21> (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, viamergeInto(Table)
Description copied from interface:DSLContext
- Specified by:
mergeInto
in interfaceDSLContext
- See Also:
-
mergeInto
@Deprecated(forRemoval=true, since="3.14") public <R extends Record,T1, MergeKeyStep22<R,T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21, T22> T1, mergeIntoT2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21, T22> (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, viamergeInto(Table)
Description copied from interface:DSLContext
- Specified by:
mergeInto
in interfaceDSLContext
- See Also:
-
mergeInto
Description copied from interface:DSLContext
Create a new DSL UPSERT statement (SQLDialect.H2
MERGE
) orSQLDialect.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 interfaceDSLContext
-
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 interfaceDSLContext
- See Also:
-
deleteQuery
Description copied from interface:DSLContext
Create a newDeleteQuery
- Specified by:
deleteQuery
in interfaceDSLContext
- Parameters:
table
- The table to delete data from- Returns:
- The new
DeleteQuery
-
delete
Description copied from interface:DSLContext
Create a new DSL delete statement.This is an alias for
DSLContext.deleteFrom(Table)
- Specified by:
delete
in interfaceDSLContext
-
deleteFrom
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 interfaceDSLContext
-
batched
Description copied from interface:DSLContext
Run aBatchedRunnable
on aBatchedConnection
, delaying execution as long as possible before batching.- Specified by:
batched
in interfaceDSLContext
- See Also:
-
batchedResult
Description copied from interface:DSLContext
Run aBatchedRunnable
on aBatchedConnection
, delaying execution as long as possible before batching.- Specified by:
batchedResult
in interfaceDSLContext
- See Also:
-
batch
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 interfaceDSLContext
- See Also:
-
batch
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 interfaceDSLContext
- See Also:
-
batch
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 interfaceDSLContext
- See Also:
-
batch
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 interfaceDSLContext
- See Also:
-
batch
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 withSettings.getStatementType()
==StatementType.STATIC_STATEMENT
- Specified by:
batch
in interfaceDSLContext
- See Also:
-
batch
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 interfaceDSLContext
- See Also:
-
batch
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 usingBatchBindStep.bind(Object...)
Note: bind values will be inlined to a static batch query as in
DSLContext.batch(Query...)
, if you choose to execute queries withSettings.getStatementType()
==StatementType.STATIC_STATEMENT
- Specified by:
batch
in interfaceDSLContext
- See Also:
-
batch
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 interfaceDSLContext
- See Also:
-
batchStore
Description copied from interface:DSLContext
Create a batch statement to execute a set ofINSERT
andUPDATE
queries in batch mode (with bind values) according toUpdatableRecord.store()
semantics.This batch operation can be executed in two modes:
With
(the default)Settings.getStatementType()
==StatementType.PREPARED_STATEMENT
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:
The above results in// 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();
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 actualUPSERT
orMERGE
statement, which delegates the decision of whether toINSERT
orUPDATE
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 interfaceDSLContext
- See Also:
-
batchStore
Description copied from interface:DSLContext
Create a batch statement to execute a set ofINSERT
andUPDATE
queries in batch mode (with bind values) according toUpdatableRecord.store()
semantics.- Specified by:
batchStore
in interfaceDSLContext
- See Also:
-
batchInsert
Description copied from interface:DSLContext
Create a batch statement to execute a set ofINSERT
queries in batch mode (with bind values) according toTableRecord.insert()
semantics.- Specified by:
batchInsert
in interfaceDSLContext
- See Also:
-
batchInsert
Description copied from interface:DSLContext
Create a batch statement to execute a set ofINSERT
queries in batch mode (with bind values) according toTableRecord.insert()
semantics.- Specified by:
batchInsert
in interfaceDSLContext
- See Also:
-
batchUpdate
Description copied from interface:DSLContext
Create a batch statement to execute a set ofUPDATE
queries in batch mode (with bind values) according toUpdatableRecord.update()
semantics.- Specified by:
batchUpdate
in interfaceDSLContext
- See Also:
-
batchUpdate
Description copied from interface:DSLContext
Create a batch statement to execute a set ofUPDATE
queries in batch mode (with bind values) according toUpdatableRecord.update()
semantics.- Specified by:
batchUpdate
in interfaceDSLContext
- See Also:
-
batchMerge
Description copied from interface:DSLContext
Create a batch statement to execute a set ofMERGE
queries in batch mode (with bind values) according toUpdatableRecord.merge()
semantics.- Specified by:
batchMerge
in interfaceDSLContext
- See Also:
-
batchMerge
Description copied from interface:DSLContext
Create a batch statement to execute a set ofMERGE
queries in batch mode (with bind values) according toUpdatableRecord.merge()
semantics.- Specified by:
batchMerge
in interfaceDSLContext
- See Also:
-
batchDelete
Description copied from interface:DSLContext
Create a batch statement to execute a set ofDELETE
queries in batch mode (with bind values) according toUpdatableRecord.delete()
sematics.This batch operation can be executed in two modes:
With
(the default)Settings.getStatementType()
==StatementType.PREPARED_STATEMENT
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:
The above results in// 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();
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 interfaceDSLContext
- See Also:
-
batchDelete
Description copied from interface:DSLContext
Create a batch statement to execute a set ofDELETE
queries in batch mode (with bind values) according toUpdatableRecord.delete()
sematics.- Specified by:
batchDelete
in interfaceDSLContext
- See Also:
-
alterDatabase
Description copied from interface:DSLContext
TheALTER DATABASE
statement.- Specified by:
alterDatabase
in interfaceDSLContext
- See Also:
-
alterDatabase
Description copied from interface:DSLContext
TheALTER DATABASE
statement.- Specified by:
alterDatabase
in interfaceDSLContext
- See Also:
-
alterDatabase
Description copied from interface:DSLContext
TheALTER DATABASE
statement.- Specified by:
alterDatabase
in interfaceDSLContext
- See Also:
-
alterDatabaseIfExists
Description copied from interface:DSLContext
TheALTER DATABASE IF EXISTS
statement.- Specified by:
alterDatabaseIfExists
in interfaceDSLContext
- See Also:
-
alterDatabaseIfExists
Description copied from interface:DSLContext
TheALTER DATABASE IF EXISTS
statement.- Specified by:
alterDatabaseIfExists
in interfaceDSLContext
- See Also:
-
alterDatabaseIfExists
Description copied from interface:DSLContext
TheALTER DATABASE IF EXISTS
statement.- Specified by:
alterDatabaseIfExists
in interfaceDSLContext
- See Also:
-
alterDomain
Description copied from interface:DSLContext
TheALTER DOMAIN
statement.- Specified by:
alterDomain
in interfaceDSLContext
- See Also:
-
alterDomain
Description copied from interface:DSLContext
TheALTER DOMAIN
statement.- Specified by:
alterDomain
in interfaceDSLContext
- See Also:
-
alterDomain
Description copied from interface:DSLContext
TheALTER DOMAIN
statement.- Specified by:
alterDomain
in interfaceDSLContext
- See Also:
-
alterDomainIfExists
Description copied from interface:DSLContext
TheALTER DOMAIN IF EXISTS
statement.- Specified by:
alterDomainIfExists
in interfaceDSLContext
- See Also:
-
alterDomainIfExists
Description copied from interface:DSLContext
TheALTER DOMAIN IF EXISTS
statement.- Specified by:
alterDomainIfExists
in interfaceDSLContext
- See Also:
-
alterDomainIfExists
Description copied from interface:DSLContext
TheALTER DOMAIN IF EXISTS
statement.- Specified by:
alterDomainIfExists
in interfaceDSLContext
- See Also:
-
alterIndex
Description copied from interface:DSLContext
TheALTER INDEX
statement.- Specified by:
alterIndex
in interfaceDSLContext
- See Also:
-
alterIndex
Description copied from interface:DSLContext
TheALTER INDEX
statement.- Specified by:
alterIndex
in interfaceDSLContext
- See Also:
-
alterIndex
Description copied from interface:DSLContext
TheALTER INDEX
statement.- Specified by:
alterIndex
in interfaceDSLContext
- See Also:
-
alterIndexIfExists
Description copied from interface:DSLContext
TheALTER INDEX IF EXISTS
statement.- Specified by:
alterIndexIfExists
in interfaceDSLContext
- See Also:
-
alterIndexIfExists
Description copied from interface:DSLContext
TheALTER INDEX IF EXISTS
statement.- Specified by:
alterIndexIfExists
in interfaceDSLContext
- See Also:
-
alterIndexIfExists
Description copied from interface:DSLContext
TheALTER INDEX IF EXISTS
statement.- Specified by:
alterIndexIfExists
in interfaceDSLContext
- See Also:
-
alterSchema
Description copied from interface:DSLContext
TheALTER SCHEMA
statement.- Specified by:
alterSchema
in interfaceDSLContext
- See Also:
-
alterSchema
Description copied from interface:DSLContext
TheALTER SCHEMA
statement.- Specified by:
alterSchema
in interfaceDSLContext
- See Also:
-
alterSchema
Description copied from interface:DSLContext
TheALTER SCHEMA
statement.- Specified by:
alterSchema
in interfaceDSLContext
- See Also:
-
alterSchemaIfExists
Description copied from interface:DSLContext
TheALTER SCHEMA IF EXISTS
statement.- Specified by:
alterSchemaIfExists
in interfaceDSLContext
- See Also:
-
alterSchemaIfExists
Description copied from interface:DSLContext
TheALTER SCHEMA IF EXISTS
statement.- Specified by:
alterSchemaIfExists
in interfaceDSLContext
- See Also:
-
alterSchemaIfExists
Description copied from interface:DSLContext
TheALTER SCHEMA IF EXISTS
statement.- Specified by:
alterSchemaIfExists
in interfaceDSLContext
- See Also:
-
alterSequence
Description copied from interface:DSLContext
TheALTER SEQUENCE
statement.- Specified by:
alterSequence
in interfaceDSLContext
- See Also:
-
alterSequence
Description copied from interface:DSLContext
TheALTER SEQUENCE
statement.- Specified by:
alterSequence
in interfaceDSLContext
- See Also:
-
alterSequence
Description copied from interface:DSLContext
TheALTER SEQUENCE
statement.- Specified by:
alterSequence
in interfaceDSLContext
- See Also:
-
alterSequenceIfExists
Description copied from interface:DSLContext
TheALTER SEQUENCE IF EXISTS
statement.- Specified by:
alterSequenceIfExists
in interfaceDSLContext
- See Also:
-
alterSequenceIfExists
Description copied from interface:DSLContext
TheALTER SEQUENCE IF EXISTS
statement.- Specified by:
alterSequenceIfExists
in interfaceDSLContext
- See Also:
-
alterSequenceIfExists
Description copied from interface:DSLContext
TheALTER SEQUENCE IF EXISTS
statement.- Specified by:
alterSequenceIfExists
in interfaceDSLContext
- See Also:
-
alterType
Description copied from interface:DSLContext
TheALTER TYPE
statement.- Specified by:
alterType
in interfaceDSLContext
- See Also:
-
alterType
Description copied from interface:DSLContext
TheALTER TYPE
statement.- Specified by:
alterType
in interfaceDSLContext
- See Also:
-
alterTypeIfExists
Description copied from interface:DSLContext
TheALTER TYPE IF EXISTS
statement.- Specified by:
alterTypeIfExists
in interfaceDSLContext
- See Also:
-
alterTypeIfExists
Description copied from interface:DSLContext
TheALTER TYPE IF EXISTS
statement.- Specified by:
alterTypeIfExists
in interfaceDSLContext
- See Also:
-
alterView
Description copied from interface:DSLContext
TheALTER VIEW
statement.- Specified by:
alterView
in interfaceDSLContext
- See Also:
-
alterView
Description copied from interface:DSLContext
TheALTER VIEW
statement.- Specified by:
alterView
in interfaceDSLContext
- See Also:
-
alterView
Description copied from interface:DSLContext
TheALTER VIEW
statement.- Specified by:
alterView
in interfaceDSLContext
- See Also:
-
alterViewIfExists
Description copied from interface:DSLContext
TheALTER VIEW IF EXISTS
statement.- Specified by:
alterViewIfExists
in interfaceDSLContext
- See Also:
-
alterViewIfExists
Description copied from interface:DSLContext
TheALTER VIEW IF EXISTS
statement.- Specified by:
alterViewIfExists
in interfaceDSLContext
- See Also:
-
alterViewIfExists
Description copied from interface:DSLContext
TheALTER VIEW IF EXISTS
statement.- Specified by:
alterViewIfExists
in interfaceDSLContext
- See Also:
-
alterMaterializedView
Description copied from interface:DSLContext
TheALTER MATERIALIZED VIEW
statement.- Specified by:
alterMaterializedView
in interfaceDSLContext
- See Also:
-
alterMaterializedView
Description copied from interface:DSLContext
TheALTER MATERIALIZED VIEW
statement.- Specified by:
alterMaterializedView
in interfaceDSLContext
- See Also:
-
alterMaterializedView
Description copied from interface:DSLContext
TheALTER MATERIALIZED VIEW
statement.- Specified by:
alterMaterializedView
in interfaceDSLContext
- See Also:
-
alterMaterializedViewIfExists
Description copied from interface:DSLContext
TheALTER MATERIALIZED VIEW IF EXISTS
statement.- Specified by:
alterMaterializedViewIfExists
in interfaceDSLContext
- See Also:
-
alterMaterializedViewIfExists
Description copied from interface:DSLContext
TheALTER MATERIALIZED VIEW IF EXISTS
statement.- Specified by:
alterMaterializedViewIfExists
in interfaceDSLContext
- See Also:
-
alterMaterializedViewIfExists
Description copied from interface:DSLContext
TheALTER MATERIALIZED VIEW IF EXISTS
statement.- Specified by:
alterMaterializedViewIfExists
in interfaceDSLContext
- See Also:
-
alterView
Description copied from interface:DSLContext
TheALTER VIEW
statement.- Specified by:
alterView
in interfaceDSLContext
- See Also:
-
alterView
Description copied from interface:DSLContext
TheALTER VIEW
statement.- Specified by:
alterView
in interfaceDSLContext
- See Also:
-
commentOnTable
Description copied from interface:DSLContext
TheCOMMENT ON TABLE
statement.- Specified by:
commentOnTable
in interfaceDSLContext
- See Also:
-
commentOnTable
Description copied from interface:DSLContext
TheCOMMENT ON TABLE
statement.- Specified by:
commentOnTable
in interfaceDSLContext
- See Also:
-
commentOnTable
Description copied from interface:DSLContext
TheCOMMENT ON TABLE
statement.- Specified by:
commentOnTable
in interfaceDSLContext
- See Also:
-
commentOnView
Description copied from interface:DSLContext
TheCOMMENT ON VIEW
statement.- Specified by:
commentOnView
in interfaceDSLContext
- See Also:
-
commentOnView
Description copied from interface:DSLContext
TheCOMMENT ON VIEW
statement.- Specified by:
commentOnView
in interfaceDSLContext
- See Also:
-
commentOnView
Description copied from interface:DSLContext
TheCOMMENT ON VIEW
statement.- Specified by:
commentOnView
in interfaceDSLContext
- See Also:
-
commentOnMaterializedView
Description copied from interface:DSLContext
TheCOMMENT ON MATERIALIZED VIEW
statement.- Specified by:
commentOnMaterializedView
in interfaceDSLContext
- See Also:
-
commentOnMaterializedView
Description copied from interface:DSLContext
TheCOMMENT ON MATERIALIZED VIEW
statement.- Specified by:
commentOnMaterializedView
in interfaceDSLContext
- See Also:
-
commentOnMaterializedView
Description copied from interface:DSLContext
TheCOMMENT ON MATERIALIZED VIEW
statement.- Specified by:
commentOnMaterializedView
in interfaceDSLContext
- See Also:
-
commentOnColumn
Description copied from interface:DSLContext
TheCOMMENT ON COLUMN
statement.- Specified by:
commentOnColumn
in interfaceDSLContext
- See Also:
-
commentOnColumn
Description copied from interface:DSLContext
TheCOMMENT ON COLUMN
statement.- Specified by:
commentOnColumn
in interfaceDSLContext
- See Also:
-
commentOnColumn
Description copied from interface:DSLContext
TheCOMMENT ON COLUMN
statement.- Specified by:
commentOnColumn
in interfaceDSLContext
- See Also:
-
createDatabase
Description copied from interface:DSLContext
TheCREATE DATABASE
statement.- Specified by:
createDatabase
in interfaceDSLContext
- See Also:
-
createDatabase
Description copied from interface:DSLContext
TheCREATE DATABASE
statement.- Specified by:
createDatabase
in interfaceDSLContext
- See Also:
-
createDatabase
Description copied from interface:DSLContext
TheCREATE DATABASE
statement.- Specified by:
createDatabase
in interfaceDSLContext
- See Also:
-
createDatabaseIfNotExists
Description copied from interface:DSLContext
TheCREATE DATABASE IF NOT EXISTS
statement.- Specified by:
createDatabaseIfNotExists
in interfaceDSLContext
- See Also:
-
createDatabaseIfNotExists
Description copied from interface:DSLContext
TheCREATE DATABASE IF NOT EXISTS
statement.- Specified by:
createDatabaseIfNotExists
in interfaceDSLContext
- See Also:
-
createDatabaseIfNotExists
Description copied from interface:DSLContext
TheCREATE DATABASE IF NOT EXISTS
statement.- Specified by:
createDatabaseIfNotExists
in interfaceDSLContext
- See Also:
-
createDomain
Description copied from interface:DSLContext
TheCREATE DOMAIN
statement.- Specified by:
createDomain
in interfaceDSLContext
- See Also:
-
createDomain
Description copied from interface:DSLContext
TheCREATE DOMAIN
statement.- Specified by:
createDomain
in interfaceDSLContext
- See Also:
-
createDomain
Description copied from interface:DSLContext
TheCREATE DOMAIN
statement.- Specified by:
createDomain
in interfaceDSLContext
- See Also:
-
createDomainIfNotExists
Description copied from interface:DSLContext
TheCREATE DOMAIN IF NOT EXISTS
statement.- Specified by:
createDomainIfNotExists
in interfaceDSLContext
- See Also:
-
createDomainIfNotExists
Description copied from interface:DSLContext
TheCREATE DOMAIN IF NOT EXISTS
statement.- Specified by:
createDomainIfNotExists
in interfaceDSLContext
- See Also:
-
createDomainIfNotExists
Description copied from interface:DSLContext
TheCREATE DOMAIN IF NOT EXISTS
statement.- Specified by:
createDomainIfNotExists
in interfaceDSLContext
- See Also:
-
createFunction
Description copied from interface:DSLContext
TheCREATE FUNCTION
statement.- Specified by:
createFunction
in interfaceDSLContext
- See Also:
-
createFunction
Description copied from interface:DSLContext
TheCREATE FUNCTION
statement.- Specified by:
createFunction
in interfaceDSLContext
- See Also:
-
createOrReplaceFunction
Description copied from interface:DSLContext
TheCREATE OR REPLACE FUNCTION
statement.- Specified by:
createOrReplaceFunction
in interfaceDSLContext
- See Also:
-
createOrReplaceFunction
Description copied from interface:DSLContext
TheCREATE OR REPLACE FUNCTION
statement.- Specified by:
createOrReplaceFunction
in interfaceDSLContext
- See Also:
-
createIndex
Description copied from interface:DSLContext
TheCREATE INDEX
statement.- Specified by:
createIndex
in interfaceDSLContext
- See Also:
-
createIndex
Description copied from interface:DSLContext
TheCREATE INDEX
statement.- Specified by:
createIndex
in interfaceDSLContext
- See Also:
-
createIndex
Description copied from interface:DSLContext
TheCREATE INDEX
statement.- Specified by:
createIndex
in interfaceDSLContext
- See Also:
-
createIndex
Description copied from interface:DSLContext
TheCREATE INDEX
statement.- Specified by:
createIndex
in interfaceDSLContext
- See Also:
-
createIndexIfNotExists
Description copied from interface:DSLContext
TheCREATE INDEX IF NOT EXISTS
statement.- Specified by:
createIndexIfNotExists
in interfaceDSLContext
- See Also:
-
createIndexIfNotExists
Description copied from interface:DSLContext
TheCREATE INDEX IF NOT EXISTS
statement.- Specified by:
createIndexIfNotExists
in interfaceDSLContext
- See Also:
-
createIndexIfNotExists
Description copied from interface:DSLContext
TheCREATE INDEX IF NOT EXISTS
statement.- Specified by:
createIndexIfNotExists
in interfaceDSLContext
- See Also:
-
createIndexIfNotExists
Description copied from interface:DSLContext
TheCREATE INDEX IF NOT EXISTS
statement.- Specified by:
createIndexIfNotExists
in interfaceDSLContext
- See Also:
-
createUniqueIndex
Description copied from interface:DSLContext
TheCREATE UNIQUE INDEX
statement.- Specified by:
createUniqueIndex
in interfaceDSLContext
- See Also:
-
createUniqueIndex
Description copied from interface:DSLContext
TheCREATE UNIQUE INDEX
statement.- Specified by:
createUniqueIndex
in interfaceDSLContext
- See Also:
-
createUniqueIndex
Description copied from interface:DSLContext
TheCREATE UNIQUE INDEX
statement.- Specified by:
createUniqueIndex
in interfaceDSLContext
- See Also:
-
createUniqueIndex
Description copied from interface:DSLContext
TheCREATE UNIQUE INDEX
statement.- Specified by:
createUniqueIndex
in interfaceDSLContext
- See Also:
-
createUniqueIndexIfNotExists
Description copied from interface:DSLContext
TheCREATE UNIQUE INDEX IF NOT EXISTS
statement.- Specified by:
createUniqueIndexIfNotExists
in interfaceDSLContext
- See Also:
-
createUniqueIndexIfNotExists
Description copied from interface:DSLContext
TheCREATE UNIQUE INDEX IF NOT EXISTS
statement.- Specified by:
createUniqueIndexIfNotExists
in interfaceDSLContext
- See Also:
-
createUniqueIndexIfNotExists
Description copied from interface:DSLContext
TheCREATE UNIQUE INDEX IF NOT EXISTS
statement.- Specified by:
createUniqueIndexIfNotExists
in interfaceDSLContext
- See Also:
-
createUniqueIndexIfNotExists
Description copied from interface:DSLContext
TheCREATE UNIQUE INDEX IF NOT EXISTS
statement.- Specified by:
createUniqueIndexIfNotExists
in interfaceDSLContext
- See Also:
-
createProcedure
Description copied from interface:DSLContext
TheCREATE PROCEDURE
statement.- Specified by:
createProcedure
in interfaceDSLContext
- See Also:
-
createProcedure
Description copied from interface:DSLContext
TheCREATE PROCEDURE
statement.- Specified by:
createProcedure
in interfaceDSLContext
- See Also:
-
createOrReplaceProcedure
Description copied from interface:DSLContext
TheCREATE OR REPLACE PROCEDURE
statement.- Specified by:
createOrReplaceProcedure
in interfaceDSLContext
- See Also:
-
createOrReplaceProcedure
Description copied from interface:DSLContext
TheCREATE OR REPLACE PROCEDURE
statement.- Specified by:
createOrReplaceProcedure
in interfaceDSLContext
- See Also:
-
createTable
Description copied from interface:DSLContext
TheCREATE TABLE
statement.- Specified by:
createTable
in interfaceDSLContext
- See Also:
-
createTable
Description copied from interface:DSLContext
TheCREATE TABLE
statement.- Specified by:
createTable
in interfaceDSLContext
- See Also:
-
createTable
Description copied from interface:DSLContext
TheCREATE TABLE
statement.- Specified by:
createTable
in interfaceDSLContext
- See Also:
-
createTableIfNotExists
Description copied from interface:DSLContext
TheCREATE TABLE IF NOT EXISTS
statement.- Specified by:
createTableIfNotExists
in interfaceDSLContext
- See Also:
-
createTableIfNotExists
Description copied from interface:DSLContext
TheCREATE TABLE IF NOT EXISTS
statement.- Specified by:
createTableIfNotExists
in interfaceDSLContext
- See Also:
-
createTableIfNotExists
Description copied from interface:DSLContext
TheCREATE TABLE IF NOT EXISTS
statement.- Specified by:
createTableIfNotExists
in interfaceDSLContext
- See Also:
-
createTemporaryTable
Description copied from interface:DSLContext
TheCREATE TEMPORARY TABLE
statement.- Specified by:
createTemporaryTable
in interfaceDSLContext
- See Also:
-
createTemporaryTable
Description copied from interface:DSLContext
TheCREATE TEMPORARY TABLE
statement.- Specified by:
createTemporaryTable
in interfaceDSLContext
- See Also:
-
createTemporaryTable
Description copied from interface:DSLContext
TheCREATE TEMPORARY TABLE
statement.- Specified by:
createTemporaryTable
in interfaceDSLContext
- See Also:
-
createTemporaryTableIfNotExists
Description copied from interface:DSLContext
TheCREATE TEMPORARY TABLE IF NOT EXISTS
statement.- Specified by:
createTemporaryTableIfNotExists
in interfaceDSLContext
- See Also:
-
createTemporaryTableIfNotExists
Description copied from interface:DSLContext
TheCREATE TEMPORARY TABLE IF NOT EXISTS
statement.- Specified by:
createTemporaryTableIfNotExists
in interfaceDSLContext
- See Also:
-
createTemporaryTableIfNotExists
Description copied from interface:DSLContext
TheCREATE TEMPORARY TABLE IF NOT EXISTS
statement.- Specified by:
createTemporaryTableIfNotExists
in interfaceDSLContext
- See Also:
-
createGlobalTemporaryTable
Description copied from interface:DSLContext
TheCREATE GLOBAL TEMPORARY TABLE
statement.- Specified by:
createGlobalTemporaryTable
in interfaceDSLContext
- See Also:
-
createGlobalTemporaryTable
Description copied from interface:DSLContext
TheCREATE GLOBAL TEMPORARY TABLE
statement.- Specified by:
createGlobalTemporaryTable
in interfaceDSLContext
- See Also:
-
createGlobalTemporaryTable
Description copied from interface:DSLContext
TheCREATE GLOBAL TEMPORARY TABLE
statement.- Specified by:
createGlobalTemporaryTable
in interfaceDSLContext
- See Also:
-
createGlobalTemporaryTableIfNotExists
Description copied from interface:DSLContext
TheCREATE GLOBAL TEMPORARY TABLE IF NOT EXISTS
statement.- Specified by:
createGlobalTemporaryTableIfNotExists
in interfaceDSLContext
- See Also:
-
createGlobalTemporaryTableIfNotExists
Description copied from interface:DSLContext
TheCREATE GLOBAL TEMPORARY TABLE IF NOT EXISTS
statement.- Specified by:
createGlobalTemporaryTableIfNotExists
in interfaceDSLContext
- See Also:
-
createGlobalTemporaryTableIfNotExists
Description copied from interface:DSLContext
TheCREATE GLOBAL TEMPORARY TABLE IF NOT EXISTS
statement.- Specified by:
createGlobalTemporaryTableIfNotExists
in interfaceDSLContext
- See Also:
-
createView
Description copied from interface:DSLContext
TheCREATE VIEW
statement.- Specified by:
createView
in interfaceDSLContext
- See Also:
-
createView
Description copied from interface:DSLContext
TheCREATE VIEW
statement.- Specified by:
createView
in interfaceDSLContext
- See Also:
-
createView
Description copied from interface:DSLContext
TheCREATE VIEW
statement.- Specified by:
createView
in interfaceDSLContext
- See Also:
-
createView
Description copied from interface:DSLContext
TheCREATE VIEW
statement.- Specified by:
createView
in interfaceDSLContext
- See Also:
-
createView
Description copied from interface:DSLContext
TheCREATE VIEW
statement.- Specified by:
createView
in interfaceDSLContext
- See Also:
-
createView
Description copied from interface:DSLContext
TheCREATE VIEW
statement.- Specified by:
createView
in interfaceDSLContext
- See Also:
-
createViewIfNotExists
Description copied from interface:DSLContext
TheCREATE VIEW IF NOT EXISTS
statement.- Specified by:
createViewIfNotExists
in interfaceDSLContext
- See Also:
-
createViewIfNotExists
Description copied from interface:DSLContext
TheCREATE VIEW IF NOT EXISTS
statement.- Specified by:
createViewIfNotExists
in interfaceDSLContext
- See Also:
-
createViewIfNotExists
Description copied from interface:DSLContext
TheCREATE VIEW IF NOT EXISTS
statement.- Specified by:
createViewIfNotExists
in interfaceDSLContext
- See Also:
-
createViewIfNotExists
public CreateViewAsStep<Record> createViewIfNotExists(@Name String view, Collection<? extends String> fields) Description copied from interface:DSLContext
TheCREATE VIEW IF NOT EXISTS
statement.- Specified by:
createViewIfNotExists
in interfaceDSLContext
- See Also:
-
createViewIfNotExists
Description copied from interface:DSLContext
TheCREATE VIEW IF NOT EXISTS
statement.- Specified by:
createViewIfNotExists
in interfaceDSLContext
- See Also:
-
createViewIfNotExists
public CreateViewAsStep<Record> createViewIfNotExists(Table<?> view, Collection<? extends Field<?>> fields) Description copied from interface:DSLContext
TheCREATE VIEW IF NOT EXISTS
statement.- Specified by:
createViewIfNotExists
in interfaceDSLContext
- See Also:
-
createOrReplaceView
Description copied from interface:DSLContext
TheCREATE OR REPLACE VIEW
statement.- Specified by:
createOrReplaceView
in interfaceDSLContext
- See Also:
-
createOrReplaceView
Description copied from interface:DSLContext
TheCREATE OR REPLACE VIEW
statement.- Specified by:
createOrReplaceView
in interfaceDSLContext
- See Also:
-
createOrReplaceView
Description copied from interface:DSLContext
TheCREATE OR REPLACE VIEW
statement.- Specified by:
createOrReplaceView
in interfaceDSLContext
- See Also:
-
createOrReplaceView
public CreateViewAsStep<Record> createOrReplaceView(@Name String view, Collection<? extends String> fields) Description copied from interface:DSLContext
TheCREATE OR REPLACE VIEW
statement.- Specified by:
createOrReplaceView
in interfaceDSLContext
- See Also:
-
createOrReplaceView
Description copied from interface:DSLContext
TheCREATE OR REPLACE VIEW
statement.- Specified by:
createOrReplaceView
in interfaceDSLContext
- See Also:
-
createOrReplaceView
public CreateViewAsStep<Record> createOrReplaceView(Table<?> view, Collection<? extends Field<?>> fields) Description copied from interface:DSLContext
TheCREATE OR REPLACE VIEW
statement.- Specified by:
createOrReplaceView
in interfaceDSLContext
- See Also:
-
createMaterializedView
Description copied from interface:DSLContext
TheCREATE MATERIALIZED VIEW
statement.- Specified by:
createMaterializedView
in interfaceDSLContext
- See Also:
-
createMaterializedView
Description copied from interface:DSLContext
TheCREATE MATERIALIZED VIEW
statement.- Specified by:
createMaterializedView
in interfaceDSLContext
- See Also:
-
createMaterializedView
Description copied from interface:DSLContext
TheCREATE MATERIALIZED VIEW
statement.- Specified by:
createMaterializedView
in interfaceDSLContext
- See Also:
-
createMaterializedView
public CreateViewAsStep<Record> createMaterializedView(@Name String view, Collection<? extends String> fields) Description copied from interface:DSLContext
TheCREATE MATERIALIZED VIEW
statement.- Specified by:
createMaterializedView
in interfaceDSLContext
- See Also:
-
createMaterializedView
public CreateViewAsStep<Record> createMaterializedView(Name view, Collection<? extends Name> fields) Description copied from interface:DSLContext
TheCREATE MATERIALIZED VIEW
statement.- Specified by:
createMaterializedView
in interfaceDSLContext
- See Also:
-
createMaterializedView
public CreateViewAsStep<Record> createMaterializedView(Table<?> view, Collection<? extends Field<?>> fields) Description copied from interface:DSLContext
TheCREATE MATERIALIZED VIEW
statement.- Specified by:
createMaterializedView
in interfaceDSLContext
- See Also:
-
createMaterializedViewIfNotExists
public CreateViewAsStep<Record> createMaterializedViewIfNotExists(@Name String view, @Name String... fields) Description copied from interface:DSLContext
TheCREATE MATERIALIZED VIEW IF NOT EXISTS
statement.- Specified by:
createMaterializedViewIfNotExists
in interfaceDSLContext
- See Also:
-
createMaterializedViewIfNotExists
Description copied from interface:DSLContext
TheCREATE MATERIALIZED VIEW IF NOT EXISTS
statement.- Specified by:
createMaterializedViewIfNotExists
in interfaceDSLContext
- See Also:
-
createMaterializedViewIfNotExists
public CreateViewAsStep<Record> createMaterializedViewIfNotExists(Table<?> view, Field<?>... fields) Description copied from interface:DSLContext
TheCREATE MATERIALIZED VIEW IF NOT EXISTS
statement.- Specified by:
createMaterializedViewIfNotExists
in interfaceDSLContext
- See Also:
-
createMaterializedViewIfNotExists
public CreateViewAsStep<Record> createMaterializedViewIfNotExists(@Name String view, Collection<? extends String> fields) Description copied from interface:DSLContext
TheCREATE MATERIALIZED VIEW IF NOT EXISTS
statement.- Specified by:
createMaterializedViewIfNotExists
in interfaceDSLContext
- See Also:
-
createMaterializedViewIfNotExists
public CreateViewAsStep<Record> createMaterializedViewIfNotExists(Name view, Collection<? extends Name> fields) Description copied from interface:DSLContext
TheCREATE MATERIALIZED VIEW IF NOT EXISTS
statement.- Specified by:
createMaterializedViewIfNotExists
in interfaceDSLContext
- See Also:
-
createMaterializedViewIfNotExists
public CreateViewAsStep<Record> createMaterializedViewIfNotExists(Table<?> view, Collection<? extends Field<?>> fields) Description copied from interface:DSLContext
TheCREATE MATERIALIZED VIEW IF NOT EXISTS
statement.- Specified by:
createMaterializedViewIfNotExists
in interfaceDSLContext
- See Also:
-
createOrReplaceMaterializedView
public CreateViewAsStep<Record> createOrReplaceMaterializedView(@Name String view, @Name String... fields) Description copied from interface:DSLContext
TheCREATE OR REPLACE MATERIALIZED VIEW
statement.- Specified by:
createOrReplaceMaterializedView
in interfaceDSLContext
- See Also:
-
createOrReplaceMaterializedView
Description copied from interface:DSLContext
TheCREATE OR REPLACE MATERIALIZED VIEW
statement.- Specified by:
createOrReplaceMaterializedView
in interfaceDSLContext
- See Also:
-
createOrReplaceMaterializedView
Description copied from interface:DSLContext
TheCREATE OR REPLACE MATERIALIZED VIEW
statement.- Specified by:
createOrReplaceMaterializedView
in interfaceDSLContext
- See Also:
-
createOrReplaceMaterializedView
public CreateViewAsStep<Record> createOrReplaceMaterializedView(@Name String view, Collection<? extends String> fields) Description copied from interface:DSLContext
TheCREATE OR REPLACE MATERIALIZED VIEW
statement.- Specified by:
createOrReplaceMaterializedView
in interfaceDSLContext
- See Also:
-
createOrReplaceMaterializedView
public CreateViewAsStep<Record> createOrReplaceMaterializedView(Name view, Collection<? extends Name> fields) Description copied from interface:DSLContext
TheCREATE OR REPLACE MATERIALIZED VIEW
statement.- Specified by:
createOrReplaceMaterializedView
in interfaceDSLContext
- See Also:
-
createOrReplaceMaterializedView
public CreateViewAsStep<Record> createOrReplaceMaterializedView(Table<?> view, Collection<? extends Field<?>> fields) Description copied from interface:DSLContext
TheCREATE OR REPLACE MATERIALIZED VIEW
statement.- Specified by:
createOrReplaceMaterializedView
in interfaceDSLContext
- See Also:
-
createTrigger
Description copied from interface:DSLContext
TheCREATE TRIGGER
statement.- Specified by:
createTrigger
in interfaceDSLContext
- See Also:
-
createTrigger
Description copied from interface:DSLContext
TheCREATE TRIGGER
statement.- Specified by:
createTrigger
in interfaceDSLContext
- See Also:
-
createTrigger
Description copied from interface:DSLContext
TheCREATE TRIGGER
statement.- Specified by:
createTrigger
in interfaceDSLContext
- See Also:
-
createOrReplaceTrigger
Description copied from interface:DSLContext
TheCREATE OR REPLACE TRIGGER
statement.- Specified by:
createOrReplaceTrigger
in interfaceDSLContext
- See Also:
-
createOrReplaceTrigger
Description copied from interface:DSLContext
TheCREATE OR REPLACE TRIGGER
statement.- Specified by:
createOrReplaceTrigger
in interfaceDSLContext
- See Also:
-
createOrReplaceTrigger
Description copied from interface:DSLContext
TheCREATE OR REPLACE TRIGGER
statement.- Specified by:
createOrReplaceTrigger
in interfaceDSLContext
- See Also:
-
createType
Description copied from interface:DSLContext
TheCREATE TYPE
statement.- Specified by:
createType
in interfaceDSLContext
- See Also:
-
createType
Description copied from interface:DSLContext
TheCREATE TYPE
statement.- Specified by:
createType
in interfaceDSLContext
- See Also:
-
createType
Description copied from interface:DSLContext
TheCREATE TYPE
statement.- Specified by:
createType
in interfaceDSLContext
- See Also:
-
createTypeIfNotExists
Description copied from interface:DSLContext
TheCREATE TYPE IF NOT EXISTS
statement.- Specified by:
createTypeIfNotExists
in interfaceDSLContext
- See Also:
-
createTypeIfNotExists
Description copied from interface:DSLContext
TheCREATE TYPE IF NOT EXISTS
statement.- Specified by:
createTypeIfNotExists
in interfaceDSLContext
- See Also:
-
createTypeIfNotExists
Description copied from interface:DSLContext
TheCREATE TYPE IF NOT EXISTS
statement.- Specified by:
createTypeIfNotExists
in interfaceDSLContext
- See Also:
-
createSchema
Description copied from interface:DSLContext
TheCREATE SCHEMA
statement.- Specified by:
createSchema
in interfaceDSLContext
- See Also:
-
createSchema
Description copied from interface:DSLContext
TheCREATE SCHEMA
statement.- Specified by:
createSchema
in interfaceDSLContext
- See Also:
-
createSchema
Description copied from interface:DSLContext
TheCREATE SCHEMA
statement.- Specified by:
createSchema
in interfaceDSLContext
- See Also:
-
createSchemaIfNotExists
Description copied from interface:DSLContext
TheCREATE SCHEMA IF NOT EXISTS
statement.- Specified by:
createSchemaIfNotExists
in interfaceDSLContext
- See Also:
-
createSchemaIfNotExists
Description copied from interface:DSLContext
TheCREATE SCHEMA IF NOT EXISTS
statement.- Specified by:
createSchemaIfNotExists
in interfaceDSLContext
- See Also:
-
createSchemaIfNotExists
Description copied from interface:DSLContext
TheCREATE SCHEMA IF NOT EXISTS
statement.- Specified by:
createSchemaIfNotExists
in interfaceDSLContext
- See Also:
-
createSequence
Description copied from interface:DSLContext
TheCREATE SEQUENCE
statement.- Specified by:
createSequence
in interfaceDSLContext
- See Also:
-
createSequence
Description copied from interface:DSLContext
TheCREATE SEQUENCE
statement.- Specified by:
createSequence
in interfaceDSLContext
- See Also:
-
createSequence
Description copied from interface:DSLContext
TheCREATE SEQUENCE
statement.- Specified by:
createSequence
in interfaceDSLContext
- See Also:
-
createSequenceIfNotExists
Description copied from interface:DSLContext
TheCREATE SEQUENCE IF NOT EXISTS
statement.- Specified by:
createSequenceIfNotExists
in interfaceDSLContext
- See Also:
-
createSequenceIfNotExists
Description copied from interface:DSLContext
TheCREATE SEQUENCE IF NOT EXISTS
statement.- Specified by:
createSequenceIfNotExists
in interfaceDSLContext
- See Also:
-
createSequenceIfNotExists
Description copied from interface:DSLContext
TheCREATE SEQUENCE IF NOT EXISTS
statement.- Specified by:
createSequenceIfNotExists
in interfaceDSLContext
- See Also:
-
dropDatabase
Description copied from interface:DSLContext
TheDROP DATABASE
statement.- Specified by:
dropDatabase
in interfaceDSLContext
- See Also:
-
dropDatabase
Description copied from interface:DSLContext
TheDROP DATABASE
statement.- Specified by:
dropDatabase
in interfaceDSLContext
- See Also:
-
dropDatabase
Description copied from interface:DSLContext
TheDROP DATABASE
statement.- Specified by:
dropDatabase
in interfaceDSLContext
- See Also:
-
dropDatabaseIfExists
Description copied from interface:DSLContext
TheDROP DATABASE IF EXISTS
statement.- Specified by:
dropDatabaseIfExists
in interfaceDSLContext
- See Also:
-
dropDatabaseIfExists
Description copied from interface:DSLContext
TheDROP DATABASE IF EXISTS
statement.- Specified by:
dropDatabaseIfExists
in interfaceDSLContext
- See Also:
-
dropDatabaseIfExists
Description copied from interface:DSLContext
TheDROP DATABASE IF EXISTS
statement.- Specified by:
dropDatabaseIfExists
in interfaceDSLContext
- See Also:
-
dropDomain
Description copied from interface:DSLContext
TheDROP DOMAIN
statement.- Specified by:
dropDomain
in interfaceDSLContext
- See Also:
-
dropDomain
Description copied from interface:DSLContext
TheDROP DOMAIN
statement.- Specified by:
dropDomain
in interfaceDSLContext
- See Also:
-
dropDomain
Description copied from interface:DSLContext
TheDROP DOMAIN
statement.- Specified by:
dropDomain
in interfaceDSLContext
- See Also:
-
dropDomainIfExists
Description copied from interface:DSLContext
TheDROP DOMAIN IF EXISTS
statement.- Specified by:
dropDomainIfExists
in interfaceDSLContext
- See Also:
-
dropDomainIfExists
Description copied from interface:DSLContext
TheDROP DOMAIN IF EXISTS
statement.- Specified by:
dropDomainIfExists
in interfaceDSLContext
- See Also:
-
dropDomainIfExists
Description copied from interface:DSLContext
TheDROP DOMAIN IF EXISTS
statement.- Specified by:
dropDomainIfExists
in interfaceDSLContext
- See Also:
-
dropFunction
Description copied from interface:DSLContext
TheDROP FUNCTION
statement.- Specified by:
dropFunction
in interfaceDSLContext
- See Also:
-
dropFunction
Description copied from interface:DSLContext
TheDROP FUNCTION
statement.- Specified by:
dropFunction
in interfaceDSLContext
- See Also:
-
dropFunctionIfExists
Description copied from interface:DSLContext
TheDROP FUNCTION IF EXISTS
statement.- Specified by:
dropFunctionIfExists
in interfaceDSLContext
- See Also:
-
dropFunctionIfExists
Description copied from interface:DSLContext
TheDROP FUNCTION IF EXISTS
statement.- Specified by:
dropFunctionIfExists
in interfaceDSLContext
- See Also:
-
dropIndex
Description copied from interface:DSLContext
TheDROP INDEX
statement.- Specified by:
dropIndex
in interfaceDSLContext
- See Also:
-
dropIndex
Description copied from interface:DSLContext
TheDROP INDEX
statement.- Specified by:
dropIndex
in interfaceDSLContext
- See Also:
-
dropIndex
Description copied from interface:DSLContext
TheDROP INDEX
statement.- Specified by:
dropIndex
in interfaceDSLContext
- See Also:
-
dropIndexIfExists
Description copied from interface:DSLContext
TheDROP INDEX IF EXISTS
statement.- Specified by:
dropIndexIfExists
in interfaceDSLContext
- See Also:
-
dropIndexIfExists
Description copied from interface:DSLContext
TheDROP INDEX IF EXISTS
statement.- Specified by:
dropIndexIfExists
in interfaceDSLContext
- See Also:
-
dropIndexIfExists
Description copied from interface:DSLContext
TheDROP INDEX IF EXISTS
statement.- Specified by:
dropIndexIfExists
in interfaceDSLContext
- See Also:
-
dropProcedure
Description copied from interface:DSLContext
TheDROP PROCEDURE
statement.- Specified by:
dropProcedure
in interfaceDSLContext
- See Also:
-
dropProcedure
Description copied from interface:DSLContext
TheDROP PROCEDURE
statement.- Specified by:
dropProcedure
in interfaceDSLContext
- See Also:
-
dropProcedureIfExists
Description copied from interface:DSLContext
TheDROP PROCEDURE IF EXISTS
statement.- Specified by:
dropProcedureIfExists
in interfaceDSLContext
- See Also:
-
dropProcedureIfExists
Description copied from interface:DSLContext
TheDROP PROCEDURE IF EXISTS
statement.- Specified by:
dropProcedureIfExists
in interfaceDSLContext
- See Also:
-
dropSchema
Description copied from interface:DSLContext
TheDROP SCHEMA
statement.- Specified by:
dropSchema
in interfaceDSLContext
- See Also:
-
dropSchema
Description copied from interface:DSLContext
TheDROP SCHEMA
statement.- Specified by:
dropSchema
in interfaceDSLContext
- See Also:
-
dropSchema
Description copied from interface:DSLContext
TheDROP SCHEMA
statement.- Specified by:
dropSchema
in interfaceDSLContext
- See Also:
-
dropSchemaIfExists
Description copied from interface:DSLContext
TheDROP SCHEMA IF EXISTS
statement.- Specified by:
dropSchemaIfExists
in interfaceDSLContext
- See Also:
-
dropSchemaIfExists
Description copied from interface:DSLContext
TheDROP SCHEMA IF EXISTS
statement.- Specified by:
dropSchemaIfExists
in interfaceDSLContext
- See Also:
-
dropSchemaIfExists
Description copied from interface:DSLContext
TheDROP SCHEMA IF EXISTS
statement.- Specified by:
dropSchemaIfExists
in interfaceDSLContext
- See Also:
-
dropSequence
Description copied from interface:DSLContext
TheDROP SEQUENCE
statement.- Specified by:
dropSequence
in interfaceDSLContext
- See Also:
-
dropSequence
Description copied from interface:DSLContext
TheDROP SEQUENCE
statement.- Specified by:
dropSequence
in interfaceDSLContext
- See Also:
-
dropSequence
Description copied from interface:DSLContext
TheDROP SEQUENCE
statement.- Specified by:
dropSequence
in interfaceDSLContext
- See Also:
-
dropSequenceIfExists
Description copied from interface:DSLContext
TheDROP SEQUENCE IF EXISTS
statement.- Specified by:
dropSequenceIfExists
in interfaceDSLContext
- See Also:
-
dropSequenceIfExists
Description copied from interface:DSLContext
TheDROP SEQUENCE IF EXISTS
statement.- Specified by:
dropSequenceIfExists
in interfaceDSLContext
- See Also:
-
dropSequenceIfExists
Description copied from interface:DSLContext
TheDROP SEQUENCE IF EXISTS
statement.- Specified by:
dropSequenceIfExists
in interfaceDSLContext
- See Also:
-
dropTable
Description copied from interface:DSLContext
TheDROP TABLE
statement.- Specified by:
dropTable
in interfaceDSLContext
- See Also:
-
dropTable
Description copied from interface:DSLContext
TheDROP TABLE
statement.- Specified by:
dropTable
in interfaceDSLContext
- See Also:
-
dropTable
Description copied from interface:DSLContext
TheDROP TABLE
statement.- Specified by:
dropTable
in interfaceDSLContext
- See Also:
-
dropTableIfExists
Description copied from interface:DSLContext
TheDROP TABLE IF EXISTS
statement.- Specified by:
dropTableIfExists
in interfaceDSLContext
- See Also:
-
dropTableIfExists
Description copied from interface:DSLContext
TheDROP TABLE IF EXISTS
statement.- Specified by:
dropTableIfExists
in interfaceDSLContext
- See Also:
-
dropTableIfExists
Description copied from interface:DSLContext
TheDROP TABLE IF EXISTS
statement.- Specified by:
dropTableIfExists
in interfaceDSLContext
- See Also:
-
dropTemporaryTable
Description copied from interface:DSLContext
TheDROP TEMPORARY TABLE
statement.- Specified by:
dropTemporaryTable
in interfaceDSLContext
- See Also:
-
dropTemporaryTable
Description copied from interface:DSLContext
TheDROP TEMPORARY TABLE
statement.- Specified by:
dropTemporaryTable
in interfaceDSLContext
- See Also:
-
dropTemporaryTable
Description copied from interface:DSLContext
TheDROP TEMPORARY TABLE
statement.- Specified by:
dropTemporaryTable
in interfaceDSLContext
- See Also:
-
dropTemporaryTableIfExists
Description copied from interface:DSLContext
TheDROP TEMPORARY TABLE IF EXISTS
statement.- Specified by:
dropTemporaryTableIfExists
in interfaceDSLContext
- See Also:
-
dropTemporaryTableIfExists
Description copied from interface:DSLContext
TheDROP TEMPORARY TABLE IF EXISTS
statement.- Specified by:
dropTemporaryTableIfExists
in interfaceDSLContext
- See Also:
-
dropTemporaryTableIfExists
Description copied from interface:DSLContext
TheDROP TEMPORARY TABLE IF EXISTS
statement.- Specified by:
dropTemporaryTableIfExists
in interfaceDSLContext
- See Also:
-
dropTrigger
Description copied from interface:DSLContext
TheDROP TRIGGER
statement.- Specified by:
dropTrigger
in interfaceDSLContext
- See Also:
-
dropTrigger
Description copied from interface:DSLContext
TheDROP TRIGGER
statement.- Specified by:
dropTrigger
in interfaceDSLContext
- See Also:
-
dropTrigger
Description copied from interface:DSLContext
TheDROP TRIGGER
statement.- Specified by:
dropTrigger
in interfaceDSLContext
- See Also:
-
dropTriggerIfExists
Description copied from interface:DSLContext
TheDROP TRIGGER IF EXISTS
statement.- Specified by:
dropTriggerIfExists
in interfaceDSLContext
- See Also:
-
dropTriggerIfExists
Description copied from interface:DSLContext
TheDROP TRIGGER IF EXISTS
statement.- Specified by:
dropTriggerIfExists
in interfaceDSLContext
- See Also:
-
dropTriggerIfExists
Description copied from interface:DSLContext
TheDROP TRIGGER IF EXISTS
statement.- Specified by:
dropTriggerIfExists
in interfaceDSLContext
- See Also:
-
dropType
Description copied from interface:DSLContext
TheDROP TYPE
statement.- Specified by:
dropType
in interfaceDSLContext
- See Also:
-
dropType
Description copied from interface:DSLContext
TheDROP TYPE
statement.- Specified by:
dropType
in interfaceDSLContext
- See Also:
-
dropType
Description copied from interface:DSLContext
TheDROP TYPE
statement.- Specified by:
dropType
in interfaceDSLContext
- See Also:
-
dropType
Description copied from interface:DSLContext
TheDROP TYPE
statement.- Specified by:
dropType
in interfaceDSLContext
- See Also:
-
dropType
Description copied from interface:DSLContext
TheDROP TYPE
statement.- Specified by:
dropType
in interfaceDSLContext
- See Also:
-
dropType
Description copied from interface:DSLContext
TheDROP TYPE
statement.- Specified by:
dropType
in interfaceDSLContext
- See Also:
-
dropType
Description copied from interface:DSLContext
TheDROP TYPE
statement.- Specified by:
dropType
in interfaceDSLContext
- See Also:
-
dropTypeIfExists
Description copied from interface:DSLContext
TheDROP TYPE IF EXISTS
statement.- Specified by:
dropTypeIfExists
in interfaceDSLContext
- See Also:
-
dropTypeIfExists
Description copied from interface:DSLContext
TheDROP TYPE IF EXISTS
statement.- Specified by:
dropTypeIfExists
in interfaceDSLContext
- See Also:
-
dropTypeIfExists
Description copied from interface:DSLContext
TheDROP TYPE IF EXISTS
statement.- Specified by:
dropTypeIfExists
in interfaceDSLContext
- See Also:
-
dropTypeIfExists
Description copied from interface:DSLContext
TheDROP TYPE IF EXISTS
statement.- Specified by:
dropTypeIfExists
in interfaceDSLContext
- See Also:
-
dropTypeIfExists
Description copied from interface:DSLContext
TheDROP TYPE IF EXISTS
statement.- Specified by:
dropTypeIfExists
in interfaceDSLContext
- See Also:
-
dropTypeIfExists
Description copied from interface:DSLContext
TheDROP TYPE IF EXISTS
statement.- Specified by:
dropTypeIfExists
in interfaceDSLContext
- See Also:
-
dropTypeIfExists
Description copied from interface:DSLContext
TheDROP TYPE IF EXISTS
statement.- Specified by:
dropTypeIfExists
in interfaceDSLContext
- See Also:
-
dropView
Description copied from interface:DSLContext
TheDROP VIEW
statement.- Specified by:
dropView
in interfaceDSLContext
- See Also:
-
dropView
Description copied from interface:DSLContext
TheDROP VIEW
statement.- Specified by:
dropView
in interfaceDSLContext
- See Also:
-
dropView
Description copied from interface:DSLContext
TheDROP VIEW
statement.- Specified by:
dropView
in interfaceDSLContext
- See Also:
-
dropViewIfExists
Description copied from interface:DSLContext
TheDROP VIEW IF EXISTS
statement.- Specified by:
dropViewIfExists
in interfaceDSLContext
- See Also:
-
dropViewIfExists
Description copied from interface:DSLContext
TheDROP VIEW IF EXISTS
statement.- Specified by:
dropViewIfExists
in interfaceDSLContext
- See Also:
-
dropViewIfExists
Description copied from interface:DSLContext
TheDROP VIEW IF EXISTS
statement.- Specified by:
dropViewIfExists
in interfaceDSLContext
- See Also:
-
dropMaterializedView
Description copied from interface:DSLContext
TheDROP MATERIALIZED VIEW
statement.- Specified by:
dropMaterializedView
in interfaceDSLContext
- See Also:
-
dropMaterializedView
Description copied from interface:DSLContext
TheDROP MATERIALIZED VIEW
statement.- Specified by:
dropMaterializedView
in interfaceDSLContext
- See Also:
-
dropMaterializedView
Description copied from interface:DSLContext
TheDROP MATERIALIZED VIEW
statement.- Specified by:
dropMaterializedView
in interfaceDSLContext
- See Also:
-
dropMaterializedViewIfExists
Description copied from interface:DSLContext
TheDROP MATERIALIZED VIEW IF EXISTS
statement.- Specified by:
dropMaterializedViewIfExists
in interfaceDSLContext
- See Also:
-
dropMaterializedViewIfExists
Description copied from interface:DSLContext
TheDROP MATERIALIZED VIEW IF EXISTS
statement.- Specified by:
dropMaterializedViewIfExists
in interfaceDSLContext
- See Also:
-
dropMaterializedViewIfExists
Description copied from interface:DSLContext
TheDROP MATERIALIZED VIEW IF EXISTS
statement.- Specified by:
dropMaterializedViewIfExists
in interfaceDSLContext
- See Also:
-
grant
Description copied from interface:DSLContext
TheGRANT
statement.- Specified by:
grant
in interfaceDSLContext
- See Also:
-
grant
Description copied from interface:DSLContext
TheGRANT
statement.- Specified by:
grant
in interfaceDSLContext
- See Also:
-
grant
Description copied from interface:DSLContext
TheGRANT
statement.- Specified by:
grant
in interfaceDSLContext
- See Also:
-
revoke
Description copied from interface:DSLContext
TheREVOKE
statement.- Specified by:
revoke
in interfaceDSLContext
- See Also:
-
revoke
Description copied from interface:DSLContext
TheREVOKE
statement.- Specified by:
revoke
in interfaceDSLContext
- See Also:
-
revoke
Description copied from interface:DSLContext
TheREVOKE
statement.- Specified by:
revoke
in interfaceDSLContext
- See Also:
-
revokeGrantOptionFor
Description copied from interface:DSLContext
TheREVOKE GRANT OPTION FOR
statement.- Specified by:
revokeGrantOptionFor
in interfaceDSLContext
- See Also:
-
revokeGrantOptionFor
Description copied from interface:DSLContext
TheREVOKE GRANT OPTION FOR
statement.- Specified by:
revokeGrantOptionFor
in interfaceDSLContext
- See Also:
-
revokeGrantOptionFor
Description copied from interface:DSLContext
TheREVOKE GRANT OPTION FOR
statement.- Specified by:
revokeGrantOptionFor
in interfaceDSLContext
- See Also:
-
set
Description copied from interface:DSLContext
TheSET
statement.Set a vendor specific session configuration to a new value.
- Specified by:
set
in interfaceDSLContext
- See Also:
-
set
Description copied from interface:DSLContext
TheSET
statement.Set a vendor specific session configuration to a new value.
- Specified by:
set
in interfaceDSLContext
- See Also:
-
setLocal
Description copied from interface:DSLContext
TheSET LOCAL
statement.Set a vendor specific transaction-local configuration to a new value.
- Specified by:
setLocal
in interfaceDSLContext
- See Also:
-
setLocal
Description copied from interface:DSLContext
TheSET LOCAL
statement.Set a vendor specific transaction-local configuration to a new value.
- Specified by:
setLocal
in interfaceDSLContext
- See Also:
-
setCatalog
Description copied from interface:DSLContext
TheSET CATALOG
statement.Set the current catalog to a new value.
- Specified by:
setCatalog
in interfaceDSLContext
- See Also:
-
setCatalog
Description copied from interface:DSLContext
TheSET CATALOG
statement.Set the current catalog to a new value.
- Specified by:
setCatalog
in interfaceDSLContext
- See Also:
-
setCatalog
Description copied from interface:DSLContext
TheSET CATALOG
statement.Set the current catalog to a new value.
- Specified by:
setCatalog
in interfaceDSLContext
- See Also:
-
setSchema
Description copied from interface:DSLContext
TheSET SCHEMA
statement.Set the current schema to a new value.
- Specified by:
setSchema
in interfaceDSLContext
- See Also:
-
setSchema
Description copied from interface:DSLContext
TheSET SCHEMA
statement.Set the current schema to a new value.
- Specified by:
setSchema
in interfaceDSLContext
- See Also:
-
setSchema
Description copied from interface:DSLContext
TheSET SCHEMA
statement.Set the current schema to a new value.
- Specified by:
setSchema
in interfaceDSLContext
- See Also:
-
truncate
Description copied from interface:DSLContext
TheTRUNCATE
statement.- Specified by:
truncate
in interfaceDSLContext
- See Also:
-
truncate
Description copied from interface:DSLContext
TheTRUNCATE
statement.- Specified by:
truncate
in interfaceDSLContext
- See Also:
-
truncate
Description copied from interface:DSLContext
TheTRUNCATE
statement.- Specified by:
truncate
in interfaceDSLContext
- See Also:
-
truncate
Description copied from interface:DSLContext
TheTRUNCATE
statement.- Specified by:
truncate
in interfaceDSLContext
- See Also:
-
truncate
Description copied from interface:DSLContext
TheTRUNCATE
statement.- Specified by:
truncate
in interfaceDSLContext
- See Also:
-
truncate
Description copied from interface:DSLContext
TheTRUNCATE
statement.- Specified by:
truncate
in interfaceDSLContext
- See Also:
-
truncate
Description copied from interface:DSLContext
TheTRUNCATE
statement.- Specified by:
truncate
in interfaceDSLContext
- See Also:
-
truncateTable
Description copied from interface:DSLContext
TheTRUNCATE TABLE
statement.- Specified by:
truncateTable
in interfaceDSLContext
- See Also:
-
truncateTable
Description copied from interface:DSLContext
TheTRUNCATE TABLE
statement.- Specified by:
truncateTable
in interfaceDSLContext
- See Also:
-
truncateTable
Description copied from interface:DSLContext
TheTRUNCATE TABLE
statement.- Specified by:
truncateTable
in interfaceDSLContext
- See Also:
-
truncateTable
Description copied from interface:DSLContext
TheTRUNCATE TABLE
statement.- Specified by:
truncateTable
in interfaceDSLContext
- See Also:
-
truncateTable
Description copied from interface:DSLContext
TheTRUNCATE TABLE
statement.- Specified by:
truncateTable
in interfaceDSLContext
- See Also:
-
truncateTable
Description copied from interface:DSLContext
TheTRUNCATE TABLE
statement.- Specified by:
truncateTable
in interfaceDSLContext
- See Also:
-
truncateTable
Description copied from interface:DSLContext
TheTRUNCATE TABLE
statement.- Specified by:
truncateTable
in interfaceDSLContext
- See Also:
-
call
Description copied from interface:DSLContext
TheCALL
statement.Call a stored procedure.
- Specified by:
call
in interfaceDSLContext
- See Also:
-
call
Description copied from interface:DSLContext
TheCALL
statement.Call a stored procedure.
- Specified by:
call
in interfaceDSLContext
- See Also:
-
startTransaction
Description copied from interface:DSLContext
TheSTART TRANSACTION
statement.Start a transaction
- Specified by:
startTransaction
in interfaceDSLContext
- See Also:
-
savepoint
Description copied from interface:DSLContext
TheSAVEPOINT
statement.Specify a savepoint
- Specified by:
savepoint
in interfaceDSLContext
- See Also:
-
savepoint
Description copied from interface:DSLContext
TheSAVEPOINT
statement.Specify a savepoint
- Specified by:
savepoint
in interfaceDSLContext
- See Also:
-
releaseSavepoint
Description copied from interface:DSLContext
TheRELEASE SAVEPOINT
statement.Release a savepoint
- Specified by:
releaseSavepoint
in interfaceDSLContext
- See Also:
-
releaseSavepoint
Description copied from interface:DSLContext
TheRELEASE SAVEPOINT
statement.Release a savepoint
- Specified by:
releaseSavepoint
in interfaceDSLContext
- See Also:
-
commit
Description copied from interface:DSLContext
TheCOMMIT
statement.Commit a transaction
- Specified by:
commit
in interfaceDSLContext
- See Also:
-
rollback
Description copied from interface:DSLContext
TheROLLBACK
statement.Rollback a transaction
- Specified by:
rollback
in interfaceDSLContext
- See Also:
-
ddl
Description copied from interface:DSLContext
Convenience method forMeta.ddl()
.- Specified by:
ddl
in interfaceDSLContext
- See Also:
-
ddl
Description copied from interface:DSLContext
Convenience method forMeta.ddl(DDLExportConfiguration)
.- Specified by:
ddl
in interfaceDSLContext
- See Also:
-
ddl
Description copied from interface:DSLContext
Convenience method forMeta.ddl(DDLExportConfiguration)
.- Specified by:
ddl
in interfaceDSLContext
- See Also:
-
ddl
Description copied from interface:DSLContext
Convenience method forMeta.ddl()
.- Specified by:
ddl
in interfaceDSLContext
- See Also:
-
ddl
Description copied from interface:DSLContext
Convenience method forMeta.ddl(DDLExportConfiguration)
.- Specified by:
ddl
in interfaceDSLContext
- See Also:
-
ddl
Description copied from interface:DSLContext
Convenience method forMeta.ddl(DDLExportConfiguration)
.- Specified by:
ddl
in interfaceDSLContext
- See Also:
-
ddl
Description copied from interface:DSLContext
Convenience method forMeta.ddl()
.- Specified by:
ddl
in interfaceDSLContext
- See Also:
-
ddl
Description copied from interface:DSLContext
Convenience method forMeta.ddl(DDLExportConfiguration)
.- Specified by:
ddl
in interfaceDSLContext
- See Also:
-
ddl
Description copied from interface:DSLContext
Convenience method forMeta.ddl(DDLExportConfiguration)
.- Specified by:
ddl
in interfaceDSLContext
- See Also:
-
ddl
Description copied from interface:DSLContext
Convenience method forMeta.ddl()
.- Specified by:
ddl
in interfaceDSLContext
- See Also:
-
ddl
Description copied from interface:DSLContext
Convenience method forMeta.ddl(DDLExportConfiguration)
.- Specified by:
ddl
in interfaceDSLContext
- See Also:
-
ddl
Description copied from interface:DSLContext
Convenience method forMeta.ddl(DDLExportConfiguration)
.- Specified by:
ddl
in interfaceDSLContext
- See Also:
-
ddl
Description copied from interface:DSLContext
Convenience method forMeta.ddl()
.- Specified by:
ddl
in interfaceDSLContext
- See Also:
-
ddl
Description copied from interface:DSLContext
Convenience method forMeta.ddl(DDLExportConfiguration)
.- Specified by:
ddl
in interfaceDSLContext
- See Also:
-
ddl
public Queries ddl(Collection<? extends Table<?>> tables, DDLExportConfiguration exportConfiguration) Description copied from interface:DSLContext
Convenience method forMeta.ddl(DDLExportConfiguration)
.- Specified by:
ddl
in interfaceDSLContext
- See Also:
-
createView
public CreateViewAsStep<Record> createView(String view, Function<? super Field<?>, ? extends String> fieldNameFunction) Description copied from interface:DSLContext
Create a new DSLCREATE VIEW
statement.This works like
DSLContext.createView(String, String...)
except that the view's field names are derived from the view'sSelect
statement using a function.- Specified by:
createView
in interfaceDSLContext
- See Also:
-
createView
public CreateViewAsStep<Record> createView(String view, BiFunction<? super Field<?>, ? super Integer, ? extends String> fieldNameFunction) Description copied from interface:DSLContext
Create a new DSLCREATE VIEW
statement.This works like
DSLContext.createView(String, String...)
except that the view's field names are derived from the view'sSelect
statement using a function.- Specified by:
createView
in interfaceDSLContext
- See Also:
-
createView
public CreateViewAsStep<Record> createView(Name view, Function<? super Field<?>, ? extends Name> fieldNameFunction) Description copied from interface:DSLContext
Create a new DSLCREATE VIEW
statement.This works like
DSLContext.createView(Name, Name...)
except that the view's field names are derived from the view'sSelect
statement using a function.- Specified by:
createView
in interfaceDSLContext
- See Also:
-
createView
public CreateViewAsStep<Record> createView(Name view, BiFunction<? super Field<?>, ? super Integer, ? extends Name> fieldNameFunction) Description copied from interface:DSLContext
Create a new DSLCREATE VIEW
statement.This works like
DSLContext.createView(Name, Name...)
except that the view's field names are derived from the view'sSelect
statement using a function.- Specified by:
createView
in interfaceDSLContext
- See Also:
-
createView
public CreateViewAsStep<Record> createView(Table<?> view, Function<? super Field<?>, ? extends Field<?>> fieldNameFunction) Description copied from interface:DSLContext
Create a new DSLCREATE VIEW
statement.This works like
DSLContext.createView(Table, Field...)
except that the view's field names are derived from the view'sSelect
statement using a function.- Specified by:
createView
in interfaceDSLContext
- See Also:
-
createView
public CreateViewAsStep<Record> createView(Table<?> view, BiFunction<? super Field<?>, ? super Integer, ? extends Field<?>> fieldNameFunction) Description copied from interface:DSLContext
Create a new DSLCREATE VIEW
statement.This works like
DSLContext.createView(Table, Field...)
except that the view's field names are derived from the view'sSelect
statement using a function.- Specified by:
createView
in interfaceDSLContext
- See Also:
-
createOrReplaceView
public CreateViewAsStep<Record> createOrReplaceView(String view, Function<? super Field<?>, ? extends String> fieldNameFunction) Description copied from interface:DSLContext
Create a new DSLCREATE OR REPLACE VIEW
statement.This works like
DSLContext.createOrReplaceView(String, String...)
except that the view's field names are derived from the view'sSelect
statement using a function.- Specified by:
createOrReplaceView
in interfaceDSLContext
- See Also:
-
createOrReplaceView
public CreateViewAsStep<Record> createOrReplaceView(String view, BiFunction<? super Field<?>, ? super Integer, ? extends String> fieldNameFunction) Description copied from interface:DSLContext
Create a new DSLCREATE OR REPLACE VIEW
statement.This works like
DSLContext.createOrReplaceView(String, String...)
except that the view's field names are derived from the view'sSelect
statement using a function.- Specified by:
createOrReplaceView
in interfaceDSLContext
- See Also:
-
createOrReplaceView
public CreateViewAsStep<Record> createOrReplaceView(Name view, Function<? super Field<?>, ? extends Name> fieldNameFunction) Description copied from interface:DSLContext
Create a new DSLCREATE OR REPLACE VIEW
statement.This works like
DSLContext.createOrReplaceView(Name, Name...)
except that the view's field names are derived from the view'sSelect
statement using a function.- Specified by:
createOrReplaceView
in interfaceDSLContext
- See Also:
-
createOrReplaceView
public CreateViewAsStep<Record> createOrReplaceView(Name view, BiFunction<? super Field<?>, ? super Integer, ? extends Name> fieldNameFunction) Description copied from interface:DSLContext
Create a new DSLCREATE OR REPLACE VIEW
statement.This works like
DSLContext.createOrReplaceView(Name, Name...)
except that the view's field names are derived from the view'sSelect
statement using a function.- Specified by:
createOrReplaceView
in interfaceDSLContext
- See Also:
-
createOrReplaceView
public CreateViewAsStep<Record> createOrReplaceView(Table<?> view, Function<? super Field<?>, ? extends Field<?>> fieldNameFunction) Description copied from interface:DSLContext
Create a new DSLCREATE OR REPLACE VIEW
statement.This works like
DSLContext.createOrReplaceView(Table, Field...)
except that the view's field names are derived from the view'sSelect
statement using a function.- Specified by:
createOrReplaceView
in interfaceDSLContext
- See Also:
-
createOrReplaceView
public CreateViewAsStep<Record> createOrReplaceView(Table<?> view, BiFunction<? super Field<?>, ? super Integer, ? extends Field<?>> fieldNameFunction) Description copied from interface:DSLContext
Create a new DSLCREATE OR REPLACE VIEW
statement.This works like
DSLContext.createOrReplaceView(Table, Field...)
except that the view's field names are derived from the view'sSelect
statement using a function.- Specified by:
createOrReplaceView
in interfaceDSLContext
- See Also:
-
createViewIfNotExists
public CreateViewAsStep<Record> createViewIfNotExists(String view, Function<? super Field<?>, ? extends String> fieldNameFunction) Description copied from interface:DSLContext
Create a new DSLCREATE VIEW
statement.This works like
DSLContext.createViewIfNotExists(String, String...)
except that the view's field names are derived from the view'sSelect
statement using a function.- Specified by:
createViewIfNotExists
in interfaceDSLContext
- See Also:
-
createViewIfNotExists
public CreateViewAsStep<Record> createViewIfNotExists(String view, BiFunction<? super Field<?>, ? super Integer, ? extends String> fieldNameFunction) Description copied from interface:DSLContext
Create a new DSLCREATE VIEW
statement.This works like
DSLContext.createViewIfNotExists(String, String...)
except that the view's field names are derived from the view'sSelect
statement using a function.- Specified by:
createViewIfNotExists
in interfaceDSLContext
- See Also:
-
createViewIfNotExists
public CreateViewAsStep<Record> createViewIfNotExists(Name view, Function<? super Field<?>, ? extends Name> fieldNameFunction) Description copied from interface:DSLContext
Create a new DSLCREATE VIEW
statement.This works like
DSLContext.createViewIfNotExists(Name, Name...)
except that the view's field names are derived from the view'sSelect
statement using a function.- Specified by:
createViewIfNotExists
in interfaceDSLContext
- See Also:
-
createViewIfNotExists
public CreateViewAsStep<Record> createViewIfNotExists(Name view, BiFunction<? super Field<?>, ? super Integer, ? extends Name> fieldNameFunction) Description copied from interface:DSLContext
Create a new DSLCREATE VIEW
statement.This works like
DSLContext.createViewIfNotExists(Name, Name...)
except that the view's field names are derived from the view'sSelect
statement using a function.- Specified by:
createViewIfNotExists
in interfaceDSLContext
- See Also:
-
createViewIfNotExists
public CreateViewAsStep<Record> createViewIfNotExists(Table<?> view, Function<? super Field<?>, ? extends Field<?>> fieldNameFunction) Description copied from interface:DSLContext
Create a new DSLCREATE VIEW
statement.This works like
DSLContext.createViewIfNotExists(Table, Field...)
except that the view's field names are derived from the view'sSelect
statement using a function.- Specified by:
createViewIfNotExists
in interfaceDSLContext
- See Also:
-
createViewIfNotExists
public CreateViewAsStep<Record> createViewIfNotExists(Table<?> view, BiFunction<? super Field<?>, ? super Integer, ? extends Field<?>> fieldNameFunction) Description copied from interface:DSLContext
Create a new DSLCREATE VIEW
statement.This works like
DSLContext.createViewIfNotExists(Table, Field...)
except that the view's field names are derived from the view'sSelect
statement using a function.- Specified by:
createViewIfNotExists
in interfaceDSLContext
- See Also:
-
alterTable
Description copied from interface:DSLContext
Create a new DSLALTER TABLE
statement.- Specified by:
alterTable
in interfaceDSLContext
- See Also:
-
alterTable
Description copied from interface:DSLContext
Create a new DSLALTER TABLE
statement.- Specified by:
alterTable
in interfaceDSLContext
- See Also:
-
alterTable
Description copied from interface:DSLContext
Create a new DSLALTER TABLE
statement.- Specified by:
alterTable
in interfaceDSLContext
- See Also:
-
alterTableIfExists
Description copied from interface:DSLContext
Create a new DSLALTER TABLE
statement.- Specified by:
alterTableIfExists
in interfaceDSLContext
- See Also:
-
alterTableIfExists
Description copied from interface:DSLContext
Create a new DSLALTER TABLE
statement.- Specified by:
alterTableIfExists
in interfaceDSLContext
- See Also:
-
alterTableIfExists
Description copied from interface:DSLContext
Create a new DSLALTER TABLE
statement.- Specified by:
alterTableIfExists
in interfaceDSLContext
- See Also:
-
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
: Usingidentity_val_local()
SQLDialect.HSQLDB
: Usingidentity()
SQLDialect.INFORMIX
: Usingdbinfo('sqlca.sqlerrd1')
SQLDialect.INGRES
: Usinglast_identity()
SQLDialect.MARIADB
: Usinglast_insert_id()
SQLDialect.MYSQL
: Usinglast_insert_id()
SQLDialect.POSTGRES
: Usinglastval()
SQLDialect.SQLITE
: Usinglast_insert_rowid()
SQLDialect.SQLSERVER
: Using@@identity
SQLDialect.SYBASE
: Using@@identity
SQLDialect.VERTICA
: Usinglast_insert_id()
- Specified by:
lastID
in interfaceDSLContext
- Returns:
- The last inserted ID. This may be
null
in some dialects, if no such number is available.
-
nextval
Description copied from interface:DSLContext
Convenience method to fetch the NEXTVAL for a sequence directly from thisDSLContext
's underlying JDBCConnection
.- Specified by:
nextval
in interfaceDSLContext
-
nextval
Description copied from interface:DSLContext
Convenience method to fetch the NEXTVAL for a sequence directly from thisDSLContext
's underlying JDBCConnection
.- Specified by:
nextval
in interfaceDSLContext
-
nextval
Description copied from interface:DSLContext
Convenience method to fetch the NEXTVAL for a sequence directly from thisDSLContext
's underlying JDBCConnection
.- Specified by:
nextval
in interfaceDSLContext
-
nextvals
Description copied from interface:DSLContext
Convenience method to fetch several NEXTVAL for a sequence directly from thisDSLContext
's underlying JDBCConnection
.This is done using
DSL.generateSeries(int, int)
.- Specified by:
nextvals
in interfaceDSLContext
-
currval
Description copied from interface:DSLContext
Convenience method to fetch the CURRVAL for a sequence directly from thisDSLContext
's underlying JDBCConnection
.- Specified by:
currval
in interfaceDSLContext
-
currval
Description copied from interface:DSLContext
Convenience method to fetch the CURRVAL for a sequence directly from thisDSLContext
's underlying JDBCConnection
.- Specified by:
currval
in interfaceDSLContext
-
currval
Description copied from interface:DSLContext
Convenience method to fetch the CURRVAL for a sequence directly from thisDSLContext
's underlying JDBCConnection
.- Specified by:
currval
in interfaceDSLContext
-
newRecord
Description copied from interface:DSLContext
Create a new emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Parameters:
fields
- The fields defining theRecord
type- Returns:
- The new record
-
newRecord
Description copied from interface:DSLContext
Create a new emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Parameters:
fields
- The fields defining theRecord
type- Returns:
- The new record
-
newRecord
Description copied from interface:DSLContext
Create a new emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Returns:
- The new record
-
newRecord
Description copied from interface:DSLContext
Create a new emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Returns:
- The new record
-
newRecord
public <T1,T2, Record3<T1,T3> T2, newRecordT3> (Field<T1> field1, Field<T2> field2, Field<T3> field3) Description copied from interface:DSLContext
Create a new emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Returns:
- The new record
-
newRecord
public <T1,T2, Record4<T1,T3, T4> T2, newRecordT3, T4> (Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4) Description copied from interface:DSLContext
Create a new emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Returns:
- The new record
-
newRecord
public <T1,T2, Record5<T1,T3, T4, T5> T2, newRecordT3, T4, T5> (Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5) Description copied from interface:DSLContext
Create a new emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Returns:
- The new record
-
newRecord
public <T1,T2, Record6<T1,T3, T4, T5, T6> T2, newRecordT3, T4, T5, T6> (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 emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Returns:
- The new record
-
newRecord
public <T1,T2, Record7<T1,T3, T4, T5, T6, T7> T2, newRecordT3, T4, T5, T6, T7> (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 emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Returns:
- The new record
-
newRecord
public <T1,T2, Record8<T1,T3, T4, T5, T6, T7, T8> T2, newRecordT3, T4, T5, T6, T7, T8> (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 emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Returns:
- The new record
-
newRecord
public <T1,T2, Record9<T1,T3, T4, T5, T6, T7, T8, T9> T2, newRecordT3, T4, T5, T6, T7, T8, T9> (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 emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Returns:
- The new record
-
newRecord
public <T1,T2, Record10<T1,T3, T4, T5, T6, T7, T8, T9, T10> T2, newRecordT3, T4, T5, T6, T7, T8, T9, T10> (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 emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Returns:
- The new record
-
newRecord
public <T1,T2, Record11<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11> T2, newRecordT3, T4, T5, T6, T7, T8, T9, T10, T11> (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 emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Returns:
- The new record
-
newRecord
public <T1,T2, Record12<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12> T2, newRecordT3, T4, T5, T6, T7, T8, T9, T10, T11, T12> (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 emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Returns:
- The new record
-
newRecord
public <T1,T2, Record13<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13> T2, newRecordT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13> (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 emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Returns:
- The new record
-
newRecord
public <T1,T2, Record14<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14> T2, newRecordT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14> (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 emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Returns:
- The new record
-
newRecord
public <T1,T2, Record15<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15> T2, newRecordT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15> (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 emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Returns:
- The new record
-
newRecord
public <T1,T2, Record16<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16> T2, newRecordT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16> (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 emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Returns:
- The new record
-
newRecord
public <T1,T2, Record17<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17> T2, newRecordT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17> (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 emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Returns:
- The new record
-
newRecord
public <T1,T2, Record18<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18> T2, newRecordT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18> (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 emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Returns:
- The new record
-
newRecord
public <T1,T2, Record19<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19> T2, newRecordT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19> (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 emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Returns:
- The new record
-
newRecord
public <T1,T2, Record20<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20> T2, newRecordT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20> (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 emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Returns:
- The new record
-
newRecord
public <T1,T2, Record21<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21> T2, newRecordT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21> (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 emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Returns:
- The new record
-
newRecord
public <T1,T2, Record22<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21, T22> T2, newRecordT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21, T22> (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 emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Returns:
- The new record
-
newRecord
Description copied from interface:DSLContext
Create a newUDTRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Type Parameters:
R
- The generic record type- Parameters:
type
- The UDT describing records of type <R>- Returns:
- The new record
-
newRecord
Description copied from interface:DSLContext
Create a newRecord
that can be inserted into the corresponding table.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- Type Parameters:
R
- The generic record type- Parameters:
table
- The table holding records of type <R>- Returns:
- The new record
-
newRecord
Description copied from interface:DSLContext
Create a new pre-filledRecord
that can be inserted into the corresponding table.This is convenience for calling
DSLContext.newRecord(Table)
and thenRecord.from(Object)
on the resulting record. The record unmapping implementation is governed byConfiguration.recordUnmapperProvider()
.The resulting record will have its internal "changed" flags set to true for all values. This means that
UpdatableRecord.store()
will perform anINSERT
statement. If you wish to store the record using anUPDATE
statement, useDSLContext.executeUpdate(UpdatableRecord)
instead.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newRecord
in interfaceDSLContext
- 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:
-
newResult
Description copied from interface:DSLContext
Create a new emptyResult
.The result is attached to this
Configuration
by default. This result can be used as a container for records.- Specified by:
newResult
in interfaceDSLContext
- Type Parameters:
R
- The generic record type- Parameters:
table
- The table holding records of type <R>- Returns:
- The new result
-
newResult
Description copied from interface:DSLContext
Create a new emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Parameters:
fields
- The fields defining theRecord
type- Returns:
- The new record
-
newResult
Description copied from interface:DSLContext
Create a new emptyRecord
.The resulting record is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Parameters:
fields
- The fields defining theRecord
type- Returns:
- The new record
-
newResult
Description copied from interface:DSLContext
Create a new emptyResult
.The resulting result is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Returns:
- The new result
-
newResult
Description copied from interface:DSLContext
Create a new emptyResult
.The resulting result is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Returns:
- The new result
-
newResult
public <T1,T2, Result<Record3<T1,T3> T2, newResultT3>> (Field<T1> field1, Field<T2> field2, Field<T3> field3) Description copied from interface:DSLContext
Create a new emptyResult
.The resulting result is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Returns:
- The new result
-
newResult
public <T1,T2, Result<Record4<T1,T3, T4> T2, newResultT3, T4>> (Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4) Description copied from interface:DSLContext
Create a new emptyResult
.The resulting result is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Returns:
- The new result
-
newResult
public <T1,T2, Result<Record5<T1,T3, T4, T5> T2, newResultT3, T4, T5>> (Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5) Description copied from interface:DSLContext
Create a new emptyResult
.The resulting result is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Returns:
- The new result
-
newResult
public <T1,T2, Result<Record6<T1,T3, T4, T5, T6> T2, newResultT3, T4, T5, T6>> (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 emptyResult
.The resulting result is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Returns:
- The new result
-
newResult
public <T1,T2, Result<Record7<T1,T3, T4, T5, T6, T7> T2, newResultT3, T4, T5, T6, T7>> (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 emptyResult
.The resulting result is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Returns:
- The new result
-
newResult
public <T1,T2, Result<Record8<T1,T3, T4, T5, T6, T7, T8> T2, newResultT3, T4, T5, T6, T7, T8>> (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 emptyResult
.The resulting result is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Returns:
- The new result
-
newResult
public <T1,T2, Result<Record9<T1,T3, T4, T5, T6, T7, T8, T9> T2, newResultT3, T4, T5, T6, T7, T8, T9>> (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 emptyResult
.The resulting result is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Returns:
- The new result
-
newResult
public <T1,T2, Result<Record10<T1,T3, T4, T5, T6, T7, T8, T9, T10> T2, newResultT3, T4, T5, T6, T7, T8, T9, T10>> (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 emptyResult
.The resulting result is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Returns:
- The new result
-
newResult
public <T1,T2, Result<Record11<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11> T2, newResultT3, T4, T5, T6, T7, T8, T9, T10, T11>> (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 emptyResult
.The resulting result is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Returns:
- The new result
-
newResult
public <T1,T2, Result<Record12<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12> T2, newResultT3, T4, T5, T6, T7, T8, T9, T10, T11, T12>> (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 emptyResult
.The resulting result is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Returns:
- The new result
-
newResult
public <T1,T2, Result<Record13<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13> T2, newResultT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13>> (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 emptyResult
.The resulting result is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Returns:
- The new result
-
newResult
public <T1,T2, Result<Record14<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14> T2, newResultT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14>> (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 emptyResult
.The resulting result is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Returns:
- The new result
-
newResult
public <T1,T2, Result<Record15<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15> T2, newResultT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15>> (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 emptyResult
.The resulting result is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Returns:
- The new result
-
newResult
public <T1,T2, Result<Record16<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16> T2, newResultT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16>> (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 emptyResult
.The resulting result is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Returns:
- The new result
-
newResult
public <T1,T2, Result<Record17<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17> T2, newResultT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17>> (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 emptyResult
.The resulting result is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Returns:
- The new result
-
newResult
public <T1,T2, Result<Record18<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18> T2, newResultT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18>> (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 emptyResult
.The resulting result is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Returns:
- The new result
-
newResult
public <T1,T2, Result<Record19<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19> T2, newResultT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19>> (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 emptyResult
.The resulting result is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Returns:
- The new result
-
newResult
public <T1,T2, Result<Record20<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20> T2, newResultT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20>> (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 emptyResult
.The resulting result is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Returns:
- The new result
-
newResult
public <T1,T2, Result<Record21<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21> T2, newResultT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21>> (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 emptyResult
.The resulting result is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Returns:
- The new result
-
newResult
public <T1,T2, Result<Record22<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21, T22> T2, newResultT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21, T22>> (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 emptyResult
.The resulting result is attached to this
Configuration
by default. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
newResult
in interfaceDSLContext
- Returns:
- The new result
-
fetch
Description copied from interface:DSLContext
Execute aResultQuery
in the context of thisDSLContext
and return results.- Specified by:
fetch
in interfaceDSLContext
- Parameters:
query
- The query to execute- Returns:
- The result. This will never be
null
. - See Also:
-
fetchLazy
Description copied from interface:DSLContext
Execute aResultQuery
in the context of thisDSLContext
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 runResultQuery.fetchLazy()
instead, or specifySettings.setFetchSize(Integer)
prior to calling this method.Client code is responsible for closing the cursor after use.
- Specified by:
fetchLazy
in interfaceDSLContext
- Parameters:
query
- The query to execute- Returns:
- The cursor. This will never be
null
. - See Also:
-
fetchAsync
Description copied from interface:DSLContext
Fetch results in a newCompletionStage
.The result is asynchronously completed by a task running in an
Executor
provided by theScope.configuration()
'sConfiguration.executorProvider()
.- Specified by:
fetchAsync
in interfaceDSLContext
- Parameters:
query
- The query to execute- Returns:
- The completion stage. The completed result will never be
null
. - See Also:
-
fetchAsync
public <R extends Record> CompletionStage<Result<R>> fetchAsync(Executor executor, ResultQuery<R> query) Description copied from interface:DSLContext
Fetch results in a newCompletionStage
that is asynchronously completed by a task running in the given executor.- Specified by:
fetchAsync
in interfaceDSLContext
- Parameters:
query
- The query to execute- Returns:
- The completion stage. The completed result will never be
null
. - See Also:
-
fetchStream
Description copied from interface:DSLContext
Execute aResultQuery
in the context of thisDSLContext
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 runResultQuery.fetchStream()
instead, or specifySettings.setFetchSize(Integer)
prior to calling this method.Client code is responsible for closing the stream after use.
- Specified by:
fetchStream
in interfaceDSLContext
- Parameters:
query
- The query to execute- Returns:
- The stream
- See Also:
-
fetchMany
Description copied from interface:DSLContext
Execute aResultQuery
in the context of thisDSLContext
and return a cursor.- Specified by:
fetchMany
in interfaceDSLContext
- Parameters:
query
- The query to execute- Returns:
- The results. This will never be
null
. - See Also:
-
fetchOne
Description copied from interface:DSLContext
Execute aResultQuery
in the context of thisDSLContext
and return a record.- Specified by:
fetchOne
in interfaceDSLContext
- Parameters:
query
- The query to execute- Returns:
- The record or
null
, if no record was found. - See Also:
-
fetchSingle
Description copied from interface:DSLContext
Execute aResultQuery
in the context of thisDSLContext
and return a record.- Specified by:
fetchSingle
in interfaceDSLContext
- Parameters:
query
- The query to execute- Returns:
- The record. This is never
null
. - See Also:
-
fetchOptional
Description copied from interface:DSLContext
Execute aResultQuery
in the context of thisDSLContext
and return a record.- Specified by:
fetchOptional
in interfaceDSLContext
- Parameters:
query
- The query to execute- Returns:
- The record
- See Also:
-
fetchValue
Description copied from interface:DSLContext
Fetch a single value from a single column table.- Specified by:
fetchValue
in interfaceDSLContext
- Parameters:
table
- The table from which to fetch a value- Returns:
- The value or
null
, if no record was found.
-
fetchValue
Description copied from interface:DSLContext
Execute aResultQuery
in the context of thisDSLContext
and return a single value.- Specified by:
fetchValue
in interfaceDSLContext
- Parameters:
query
- The query to execute- Returns:
- The value or
null
, if no record was found.
-
fetchValue
Description copied from interface:DSLContext
Execute aResultQuery
in the context of thisDSLContext
and return a single value.- Specified by:
fetchValue
in interfaceDSLContext
- Parameters:
field
- The field for which to fetch a single value.- Returns:
- The value or
null
, if no record was found.
-
fetchValue
Description copied from interface:DSLContext
Execute aResultQuery
in the context of thisDSLContext
and return a single value.- Specified by:
fetchValue
in interfaceDSLContext
- Parameters:
field
- The field for which to fetch a single value.condition
- The condition for which to fetch a single value.- Returns:
- The value or
null
, if no record was found.
-
fetchValue
Description copied from interface:DSLContext
Execute aResultQuery
in the context of thisDSLContext
and return a single value.- Specified by:
fetchValue
in interfaceDSLContext
- Parameters:
field
- The field for which to fetch a single value.- Returns:
- The value or
null
, if no record was found.
-
fetchOptionalValue
Description copied from interface:DSLContext
Execute aResultQuery
in the context of thisDSLContext
and return a single value.- Specified by:
fetchOptionalValue
in interfaceDSLContext
- Parameters:
query
- The query to execute- Returns:
- The value.
-
fetchOptionalValue
Description copied from interface:DSLContext
Execute aResultQuery
in the context of thisDSLContext
and return a single value.- Specified by:
fetchOptionalValue
in interfaceDSLContext
- Parameters:
field
- The field for which to fetch a single value.- Returns:
- The value.
-
fetchOptionalValue
Description copied from interface:DSLContext
Execute aResultQuery
in the context of thisDSLContext
and return a single value.- Specified by:
fetchOptionalValue
in interfaceDSLContext
- Parameters:
field
- The field for which to fetch a single value.condition
- The condition for which to fetch a single value.- Returns:
- The value.
-
fetchValues
Description copied from interface:DSLContext
Fetch all values from a single column table.- Specified by:
fetchValues
in interfaceDSLContext
- Parameters:
table
- The table from which to fetch values- Returns:
- The values. This will never be
null
.
-
fetchValues
Description copied from interface:DSLContext
Execute aResultQuery
in the context of thisDSLContext
and return all values for the only column.- Specified by:
fetchValues
in interfaceDSLContext
- Parameters:
query
- The query to execute- Returns:
- The values. This will never be
null
.
-
fetchValues
Description copied from interface:DSLContext
Fetch all values in a givenTable
'sTableField
.- Specified by:
fetchValues
in interfaceDSLContext
- Parameters:
field
- The field for which to fetch all values.- Returns:
- The values. This will never be
null
.
-
fetchValues
Description copied from interface:DSLContext
Fetch all values in a givenTable
'sTableField
.- Specified by:
fetchValues
in interfaceDSLContext
- Parameters:
field
- The field for which to fetch values.condition
- The condition for which to fetch values.- Returns:
- The values. This will never be
null
.
-
fetchMap
Description copied from interface:DSLContext
Execute the query and return aMap
with the first column as the map key and the second column as the map value.An exception is thrown, if the keys turn out to be non-unique in the result set. Use
DSLContext.fetchGroups(ResultQuery)
instead, if your keys are non-unique.Whether this fetches an intermediate
Result
(accessible byExecuteListener
implementations), or streams records directly to the collector producing the result is governed bySettings.getFetchIntermediateResult()
.The resulting map is iteration order preserving.
- Specified by:
fetchMap
in interfaceDSLContext
- Returns:
- A Map containing grouped results. This will never be
null
. - See Also:
-
fetchGroups
Description copied from interface:DSLContext
Execute the query and return aMap
with the first column as the map key and the second column as the map values.Unlike
DSLContext.fetchMap(ResultQuery)
, this method allows for non-unique keys in the result set.Whether this fetches an intermediate
Result
(accessible byExecuteListener
implementations), or streams records directly to the collector producing the result is governed bySettings.getFetchIntermediateResult()
.The resulting map is iteration order preserving.
- Specified by:
fetchGroups
in interfaceDSLContext
- Returns:
- A Map containing grouped results. This will never be
null
. - See Also:
-
fetchByExample
Description copied from interface:DSLContext
Execute a "Query by Example" (QBE) based on an example record.- Specified by:
fetchByExample
in interfaceDSLContext
- Parameters:
example
- The example record- Returns:
- The resulting records matching the example record.
- See Also:
-
fetchCount
Description copied from interface:DSLContext
Execute aSelect
query in the context of thisDSLContext
and return aCOUNT(*)
value.This wraps a pre-existing
SELECT
query in another one to calculate theCOUNT(*)
value, without modifying the originalSELECT
. An example:
This is particularly useful for those databases that do not support the-- 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%' )
COUNT(*) OVER()
window function to calculate total results in paged queries.- Specified by:
fetchCount
in interfaceDSLContext
- Parameters:
query
- The wrapped query- Returns:
- The
COUNT(*)
result
-
fetchCount
Description copied from interface:DSLContext
Count the number of records in a table.This executes
SELECT COUNT(*) FROM table
- Specified by:
fetchCount
in interfaceDSLContext
- Parameters:
table
- The table whose records to count- Returns:
- The number of records in the table
-
fetchCount
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 interfaceDSLContext
- Parameters:
table
- The table whose records to countcondition
- The condition to apply- Returns:
- The number of records in the table that satisfy a condition
-
fetchCount
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)
withDSL.and(Condition...)
.- Specified by:
fetchCount
in interfaceDSLContext
- Parameters:
table
- The table whose records to countconditions
- The conditions to apply- Returns:
- The number of records in the table that satisfy a condition
-
fetchCount
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)
withDSL.and(Collection)
.- Specified by:
fetchCount
in interfaceDSLContext
- Parameters:
table
- The table whose records to countconditions
- The conditions to apply- Returns:
- The number of records in the table that satisfy a condition
-
fetchExists
Description copied from interface:DSLContext
Check if aSelect
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 originalSELECT
. 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 interfaceDSLContext
- Parameters:
query
- The wrapped query- Returns:
- The
EXISTS(…)
result
-
fetchExists
Description copied from interface:DSLContext
Check if a table has any records.This executes
SELECT EXISTS(SELECT * FROM table)
- Specified by:
fetchExists
in interfaceDSLContext
- Parameters:
table
- The table whose records to count- Returns:
- Whether the table contains any records
-
fetchExists
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 interfaceDSLContext
- Parameters:
table
- The table whose records to count- Returns:
- Whether the table contains any records that satisfy a condition
-
fetchExists
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)
withDSL.and(Condition...)
.- Specified by:
fetchExists
in interfaceDSLContext
- Parameters:
table
- The table whose records to count- Returns:
- Whether the table contains any records that satisfy a condition
-
fetchExists
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)
withDSL.and(Collection)
.- Specified by:
fetchExists
in interfaceDSLContext
- Parameters:
table
- The table whose records to count- Returns:
- Whether the table contains any records that satisfy a condition
-
execute
Description copied from interface:DSLContext
Execute aQuery
in the context of thisDSLContext
.- Specified by:
execute
in interfaceDSLContext
- Parameters:
query
- The query to execute- Returns:
- The number of affected rows
- See Also:
-
fetch
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. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
fetch
in interfaceDSLContext
- Returns:
- The results from the executed query. This will never be
null
.
-
fetch
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. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
fetch
in interfaceDSLContext
- Returns:
- The results from the executed query. This will never be
null
.
-
fetch
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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetch(Table, Condition)
withDSL.and(Condition...)
.- Specified by:
fetch
in interfaceDSLContext
- 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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetch(Table, Condition)
withDSL.and(Collection)
.- Specified by:
fetch
in interfaceDSLContext
- Returns:
- The results from the executed query. This will never be
null
.
-
fetchOne
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. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
fetchOne
in interfaceDSLContext
- Returns:
- The record or
null
, if no record was found.
-
fetchOne
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. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
fetchOne
in interfaceDSLContext
- Returns:
- The record or
null
, if no record was found.
-
fetchOne
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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchOne(Table, Condition)
withDSL.and(Condition...)
.- Specified by:
fetchOne
in interfaceDSLContext
- Returns:
- The record or
null
, if no record was found.
-
fetchOne
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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchOne(Table, Condition)
withDSL.and(Collection)
.- Specified by:
fetchOne
in interfaceDSLContext
- Returns:
- The record or
null
, if no record was found.
-
fetchSingle
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. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
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. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(Table, Condition)
withDSL.and(Condition...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(Table, Condition)
withDSL.and(Collection)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
. - Throws:
DataAccessException
- if something went wrong executing the query
-
fetchSingle
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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
. - Throws:
DataAccessException
- if something went wrong executing the query
-
fetchSingle
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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <T1,T2, Record3<T1,T3> T2, fetchSingleT3> (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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <T1,T2, Record4<T1,T3, T4> T2, fetchSingleT3, T4> (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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <T1,T2, Record5<T1,T3, T4, T5> T2, fetchSingleT3, T4, T5> (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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <T1,T2, Record6<T1,T3, T4, T5, T6> T2, fetchSingleT3, T4, T5, T6> (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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <T1,T2, Record7<T1,T3, T4, T5, T6, T7> T2, fetchSingleT3, T4, T5, T6, T7> (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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <T1,T2, Record8<T1,T3, T4, T5, T6, T7, T8> T2, fetchSingleT3, T4, T5, T6, T7, T8> (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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <T1,T2, Record9<T1,T3, T4, T5, T6, T7, T8, T9> T2, fetchSingleT3, T4, T5, T6, T7, T8, T9> (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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <T1,T2, Record10<T1,T3, T4, T5, T6, T7, T8, T9, T10> T2, fetchSingleT3, T4, T5, T6, T7, T8, T9, T10> (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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <T1,T2, Record11<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11> T2, fetchSingleT3, T4, T5, T6, T7, T8, T9, T10, T11> (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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <T1,T2, Record12<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12> T2, fetchSingleT3, T4, T5, T6, T7, T8, T9, T10, T11, T12> (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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <T1,T2, Record13<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13> T2, fetchSingleT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13> (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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <T1,T2, Record14<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14> T2, fetchSingleT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14> (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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <T1,T2, Record15<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15> T2, fetchSingleT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15> (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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <T1,T2, Record16<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16> T2, fetchSingleT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16> (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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <T1,T2, Record17<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17> T2, fetchSingleT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17> (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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <T1,T2, Record18<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18> T2, fetchSingleT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18> (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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <T1,T2, Record19<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19> T2, fetchSingleT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19> (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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <T1,T2, Record20<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20> T2, fetchSingleT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20> (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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <T1,T2, Record21<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21> T2, fetchSingleT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21> (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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <T1,T2, Record22<T1,T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21, T22> T2, fetchSingleT3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21, T22> (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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchSingle(ResultQuery)
withDSL.select(SelectFieldOrAsterisk...)
.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
Description copied from interface:DSLContext
Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.Since jOOQ 3.17,
Table
extendsSelectField
, andCondition
extendsField
. As such, there is an overload conflict betweenDSLContext.fetchSingle(Table, Condition...)
andDSLContext.fetchSingle(SelectField, SelectField)
, which can be resolved backwards compatibly with this method.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
Description copied from interface:DSLContext
Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.Since jOOQ 3.17,
Table
extendsSelectField
, andCondition
extendsField
. As such, there is an overload conflict betweenDSLContext.fetchSingle(Table, Condition...)
andDSLContext.fetchSingle(SelectField, SelectField, SelectField)
, which can be resolved backwards compatibly with this method.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <R extends Record> R fetchSingle(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4) Description copied from interface:DSLContext
Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.Since jOOQ 3.17,
Table
extendsSelectField
, andCondition
extendsField
. As such, there is an overload conflict betweenDSLContext.fetchSingle(Table, Condition...)
andDSLContext.fetchSingle(SelectField, SelectField, SelectField, SelectField)
, which can be resolved backwards compatibly with this method.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <R extends Record> R fetchSingle(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5) Description copied from interface:DSLContext
Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.Since jOOQ 3.17,
Table
extendsSelectField
, andCondition
extendsField
. As such, there is an overload conflict betweenDSLContext.fetchSingle(Table, Condition...)
andDSLContext.fetchSingle(SelectField, SelectField, SelectField, SelectField, SelectField)
, which can be resolved backwards compatibly with this method.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <R extends Record> R fetchSingle(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6) Description copied from interface:DSLContext
Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.Since jOOQ 3.17,
Table
extendsSelectField
, andCondition
extendsField
. As such, there is an overload conflict betweenDSLContext.fetchSingle(Table, Condition...)
andDSLContext.fetchSingle(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField)
, which can be resolved backwards compatibly with this method.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <R extends Record> R fetchSingle(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7) Description copied from interface:DSLContext
Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.Since jOOQ 3.17,
Table
extendsSelectField
, andCondition
extendsField
. As such, there is an overload conflict betweenDSLContext.fetchSingle(Table, Condition...)
andDSLContext.fetchSingle(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField)
, which can be resolved backwards compatibly with this method.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <R extends Record> R fetchSingle(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8) Description copied from interface:DSLContext
Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.Since jOOQ 3.17,
Table
extendsSelectField
, andCondition
extendsField
. As such, there is an overload conflict betweenDSLContext.fetchSingle(Table, Condition...)
andDSLContext.fetchSingle(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField)
, which can be resolved backwards compatibly with this method.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <R extends Record> R fetchSingle(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9) Description copied from interface:DSLContext
Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.Since jOOQ 3.17,
Table
extendsSelectField
, andCondition
extendsField
. As such, there is an overload conflict betweenDSLContext.fetchSingle(Table, Condition...)
andDSLContext.fetchSingle(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField)
, which can be resolved backwards compatibly with this method.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <R extends Record> R fetchSingle(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10) Description copied from interface:DSLContext
Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.Since jOOQ 3.17,
Table
extendsSelectField
, andCondition
extendsField
. As such, there is an overload conflict betweenDSLContext.fetchSingle(Table, Condition...)
andDSLContext.fetchSingle(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField)
, which can be resolved backwards compatibly with this method.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <R extends Record> R fetchSingle(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11) Description copied from interface:DSLContext
Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.Since jOOQ 3.17,
Table
extendsSelectField
, andCondition
extendsField
. As such, there is an overload conflict betweenDSLContext.fetchSingle(Table, Condition...)
andDSLContext.fetchSingle(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField)
, which can be resolved backwards compatibly with this method.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <R extends Record> R fetchSingle(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11, Condition c12) Description copied from interface:DSLContext
Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.Since jOOQ 3.17,
Table
extendsSelectField
, andCondition
extendsField
. As such, there is an overload conflict betweenDSLContext.fetchSingle(Table, Condition...)
andDSLContext.fetchSingle(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField)
, which can be resolved backwards compatibly with this method.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <R extends Record> R fetchSingle(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11, Condition c12, Condition c13) Description copied from interface:DSLContext
Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.Since jOOQ 3.17,
Table
extendsSelectField
, andCondition
extendsField
. As such, there is an overload conflict betweenDSLContext.fetchSingle(Table, Condition...)
andDSLContext.fetchSingle(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField)
, which can be resolved backwards compatibly with this method.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <R extends Record> R fetchSingle(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11, Condition c12, Condition c13, Condition c14) Description copied from interface:DSLContext
Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.Since jOOQ 3.17,
Table
extendsSelectField
, andCondition
extendsField
. As such, there is an overload conflict betweenDSLContext.fetchSingle(Table, Condition...)
andDSLContext.fetchSingle(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField)
, which can be resolved backwards compatibly with this method.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <R extends Record> R fetchSingle(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11, Condition c12, Condition c13, Condition c14, Condition c15) Description copied from interface:DSLContext
Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.Since jOOQ 3.17,
Table
extendsSelectField
, andCondition
extendsField
. As such, there is an overload conflict betweenDSLContext.fetchSingle(Table, Condition...)
andDSLContext.fetchSingle(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField)
, which can be resolved backwards compatibly with this method.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <R extends Record> R fetchSingle(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11, Condition c12, Condition c13, Condition c14, Condition c15, Condition c16) Description copied from interface:DSLContext
Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.Since jOOQ 3.17,
Table
extendsSelectField
, andCondition
extendsField
. As such, there is an overload conflict betweenDSLContext.fetchSingle(Table, Condition...)
andDSLContext.fetchSingle(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField)
, which can be resolved backwards compatibly with this method.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <R extends Record> R fetchSingle(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11, Condition c12, Condition c13, Condition c14, Condition c15, Condition c16, Condition c17) Description copied from interface:DSLContext
Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.Since jOOQ 3.17,
Table
extendsSelectField
, andCondition
extendsField
. As such, there is an overload conflict betweenDSLContext.fetchSingle(Table, Condition...)
andDSLContext.fetchSingle(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField)
, which can be resolved backwards compatibly with this method.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <R extends Record> R fetchSingle(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11, Condition c12, Condition c13, Condition c14, Condition c15, Condition c16, Condition c17, Condition c18) Description copied from interface:DSLContext
Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.Since jOOQ 3.17,
Table
extendsSelectField
, andCondition
extendsField
. As such, there is an overload conflict betweenDSLContext.fetchSingle(Table, Condition...)
andDSLContext.fetchSingle(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField)
, which can be resolved backwards compatibly with this method.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <R extends Record> R fetchSingle(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11, Condition c12, Condition c13, Condition c14, Condition c15, Condition c16, Condition c17, Condition c18, Condition c19) Description copied from interface:DSLContext
Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.Since jOOQ 3.17,
Table
extendsSelectField
, andCondition
extendsField
. As such, there is an overload conflict betweenDSLContext.fetchSingle(Table, Condition...)
andDSLContext.fetchSingle(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField)
, which can be resolved backwards compatibly with this method.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <R extends Record> R fetchSingle(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11, Condition c12, Condition c13, Condition c14, Condition c15, Condition c16, Condition c17, Condition c18, Condition c19, Condition c20) Description copied from interface:DSLContext
Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.Since jOOQ 3.17,
Table
extendsSelectField
, andCondition
extendsField
. As such, there is an overload conflict betweenDSLContext.fetchSingle(Table, Condition...)
andDSLContext.fetchSingle(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField)
, which can be resolved backwards compatibly with this method.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <R extends Record> R fetchSingle(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11, Condition c12, Condition c13, Condition c14, Condition c15, Condition c16, Condition c17, Condition c18, Condition c19, Condition c20, Condition c21) Description copied from interface:DSLContext
Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.Since jOOQ 3.17,
Table
extendsSelectField
, andCondition
extendsField
. As such, there is an overload conflict betweenDSLContext.fetchSingle(Table, Condition...)
andDSLContext.fetchSingle(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField)
, which can be resolved backwards compatibly with this method.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchSingle
public <R extends Record> R fetchSingle(Table<R> table, Condition c1, Condition c2, Condition c3, Condition c4, Condition c5, Condition c6, Condition c7, Condition c8, Condition c9, Condition c10, Condition c11, Condition c12, Condition c13, Condition c14, Condition c15, Condition c16, Condition c17, Condition c18, Condition c19, Condition c20, Condition c21, Condition c22) Description copied from interface:DSLContext
Disambiguation overload ofDSLContext.fetchSingle(Table, Condition...)
.Since jOOQ 3.17,
Table
extendsSelectField
, andCondition
extendsField
. As such, there is an overload conflict betweenDSLContext.fetchSingle(Table, Condition...)
andDSLContext.fetchSingle(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField)
, which can be resolved backwards compatibly with this method.- Specified by:
fetchSingle
in interfaceDSLContext
- Returns:
- The record. This is never
null
.
-
fetchOptional
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. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
fetchOptional
in interfaceDSLContext
- Returns:
- The record
-
fetchOptional
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. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
fetchOptional
in interfaceDSLContext
- Returns:
- The record
-
fetchOptional
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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchOptional(Table, Condition)
withDSL.and(Condition...)
.- Specified by:
fetchOptional
in interfaceDSLContext
- 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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchOptional(Table, Condition)
withDSL.and(Collection)
.- Specified by:
fetchOptional
in interfaceDSLContext
- Returns:
- The record
-
fetchAny
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. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
fetchAny
in interfaceDSLContext
- Returns:
- The record or
null
if no record was returned
-
fetchAny
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. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
fetchAny
in interfaceDSLContext
- Returns:
- The record or
null
if no record was returned
-
fetchAny
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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchAny(Table, Condition)
withDSL.and(Condition...)
.- Specified by:
fetchAny
in interfaceDSLContext
- Returns:
- The record or
null
if no record was returned
-
fetchAny
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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchAny(Table, Condition)
withDSL.and(Collection)
.- Specified by:
fetchAny
in interfaceDSLContext
- Returns:
- The record or
null
if no record was returned
-
fetchLazy
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. UseSettings.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 runResultQuery.fetchLazy()
instead, or specifySettings.setFetchSize(Integer)
prior to calling this method.Client code is responsible for closing the cursor after use.
- Specified by:
fetchLazy
in interfaceDSLContext
- Returns:
- The cursor. This will never be
null
.
-
fetchLazy
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. UseSettings.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 runResultQuery.fetchLazy()
instead, or specifySettings.setFetchSize(Integer)
prior to calling this method.Client code is responsible for closing the cursor after use.
- Specified by:
fetchLazy
in interfaceDSLContext
- Returns:
- The cursor. This will never be
null
.
-
fetchLazy
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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchLazy(Table, Condition)
withDSL.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 runResultQuery.fetchLazy()
instead, or specifySettings.setFetchSize(Integer)
prior to calling this method.Client code is responsible for closing the cursor after use.
- Specified by:
fetchLazy
in interfaceDSLContext
- 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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchLazy(Table, Condition)
withDSL.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 runResultQuery.fetchLazy()
instead, or specifySettings.setFetchSize(Integer)
prior to calling this method.Client code is responsible for closing the cursor after use.
- Specified by:
fetchLazy
in interfaceDSLContext
- Returns:
- The cursor. This will never be
null
.
-
fetchAsync
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. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
fetchAsync
in interfaceDSLContext
- 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. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
fetchAsync
in interfaceDSLContext
- 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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchAsync(Table, Condition)
withDSL.and(Condition...)
.- Specified by:
fetchAsync
in interfaceDSLContext
- 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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchAsync(Table, Condition)
withDSL.and(Collection)
.- Specified by:
fetchAsync
in interfaceDSLContext
- Returns:
- The completion stage. The completed result will never be
null
.
-
fetchAsync
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. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
fetchAsync
in interfaceDSLContext
- 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. UseSettings.isAttachRecords()
to override this behaviour.- Specified by:
fetchAsync
in interfaceDSLContext
- 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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchAsync(Executor, Table, Condition)
withDSL.and(Condition...)
.- Specified by:
fetchAsync
in interfaceDSLContext
- 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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchAsync(Executor, Table, Condition)
withDSL.and(Collection)
.- Specified by:
fetchAsync
in interfaceDSLContext
- Returns:
- The completion stage. The completed result will never be
null
.
-
fetchStream
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. UseSettings.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 runResultQuery.fetchStream()
instead, or specifySettings.setFetchSize(Integer)
prior to calling this method.Client code is responsible for closing the stream after use.
- Specified by:
fetchStream
in interfaceDSLContext
-
fetchStream
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. UseSettings.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 runResultQuery.fetchStream()
instead, or specifySettings.setFetchSize(Integer)
prior to calling this method.Client code is responsible for closing the stream after use.
- Specified by:
fetchStream
in interfaceDSLContext
-
fetchStream
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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchStream(Table, Condition)
withDSL.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 runResultQuery.fetchStream()
instead, or specifySettings.setFetchSize(Integer)
prior to calling this method.Client code is responsible for closing the stream after use.
- Specified by:
fetchStream
in interfaceDSLContext
-
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. UseSettings.isAttachRecords()
to override this behaviour.Convenience API for calling
DSLContext.fetchStream(Table, Condition)
withDSL.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 runResultQuery.fetchStream()
instead, or specifySettings.setFetchSize(Integer)
prior to calling this method.Client code is responsible for closing the stream after use.
- Specified by:
fetchStream
in interfaceDSLContext
-
executeInsert
Description copied from interface:DSLContext
Insert one record.This executes the following statement:
INSERT INTO [table] ([modified columns in record]) VALUES ([modified values in record])
Unlike
UpdatableRecord.insert()
, this does not change any of the argumentrecord
's internal "changed" flags, such that a subsequent call toUpdatableRecord.insert()
might lead to anotherINSERT
statement being executed.Also any optimistic locking related
Settings
do not apply for this method.- Specified by:
executeInsert
in interfaceDSLContext
- Returns:
- The number of inserted records
-
executeUpdate
Description copied from interface:DSLContext
Update a table.This executes the following statement:
UPDATE [table] SET [modified values in record] WHERE [record is supplied record]
Any optimistic locking related
Settings
do not apply for this method.- Specified by:
executeUpdate
in interfaceDSLContext
- Returns:
- The number of updated records
-
executeUpdate
Description copied from interface:DSLContext
Update a table.This executes the following statement:
UPDATE [table] SET [modified values in record] WHERE [condition]
Any optimistic locking related
Settings
do not apply for this method.- Specified by:
executeUpdate
in interfaceDSLContext
- Returns:
- The number of updated records
-
executeDelete
Description copied from interface:DSLContext
Delete a record from a table.This executes the following statement:
DELETE FROM [table] WHERE [record is supplied record]
Any optimistic locking related
Settings
do not apply for this method.- Specified by:
executeDelete
in interfaceDSLContext
- Returns:
- The number of deleted records
-
executeDelete
Description copied from interface:DSLContext
Delete a record from a table.This executes the following statement:
DELETE FROM [table] WHERE [condition]
Any optimistic locking related
Settings
do not apply for this method.- Specified by:
executeDelete
in interfaceDSLContext
- Returns:
- The number of deleted records
-
toString
-
creationTime
Description copied from interface:Scope
The time, according toConfiguration.clock()
, when thisScope
was created.- Specified by:
creationTime
in interfaceScope
-
configuration
Description copied from interface:Scope
The configuration of the current scope.- Specified by:
configuration
in interfaceScope
-
dsl
Description copied from interface:Scope
Wrap theScope.configuration()
in aDSLContext
, providing access to the configuration-contextual DSL to construct executable queries. -
settings
Description copied from interface:Scope
The settings wrapped by this context.This method is a convenient way of accessing
configuration().settings()
. -
dialect
Description copied from interface:Scope
TheSQLDialect
wrapped by this context.This method is a convenient way of accessing
configuration().dialect()
. -
family
Description copied from interface:Scope
TheSQLDialect.family()
wrapped by this context.This method is a convenient way of accessing
configuration().family()
. -
data
Description copied from interface:Scope
Get all custom data from thisScope
.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 toQueryPart
objects for a givenScope
. -
data
Description copied from interface:Scope
Get some custom data from thisScope
.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 toQueryPart
objects for a givenScope
-
data
Description copied from interface:Scope
Set some custom data to thisScope
.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 toQueryPart
objects for a givenScope
.
-
mergeInto(Table)