public class DefaultDSLContext extends Object implements DSLContext, Serializable
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.
| Constructor and Description |
|---|
DefaultDSLContext(Configuration configuration) |
DefaultDSLContext(ConnectionProvider connectionProvider,
SQLDialect dialect) |
DefaultDSLContext(ConnectionProvider connectionProvider,
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(SQLDialect dialect) |
DefaultDSLContext(SQLDialect dialect,
Settings settings) |
| Modifier and Type | Method and Description |
|---|---|
AlterIndexStep |
alterIndex(Name index)
Create a new DSL
ALTER INDEX statement. |
AlterIndexStep |
alterIndex(String index)
Create a new DSL
ALTER INDEX statement. |
AlterIndexStep |
alterIndexIfExists(Name index)
Create a new DSL
ALTER INDEX statement. |
AlterIndexStep |
alterIndexIfExists(String index)
Create a new DSL
ALTER INDEX statement. |
AlterSchemaStep |
alterSchema(Name schema)
Create a new DSL
ALTER SCHEMA statement. |
AlterSchemaStep |
alterSchema(Schema schema)
Create a new DSL
ALTER SCHEMA statement. |
AlterSchemaStep |
alterSchema(String schema)
Create a new DSL
ALTER SCHEMA statement. |
AlterSchemaStep |
alterSchemaIfExists(Name schema)
Create a new DSL
ALTER SCHEMA statement. |
AlterSchemaStep |
alterSchemaIfExists(Schema schema)
Create a new DSL
ALTER SCHEMA statement. |
AlterSchemaStep |
alterSchemaIfExists(String schema)
Create a new DSL
ALTER SCHEMA statement. |
AlterSequenceStep<BigInteger> |
alterSequence(Name sequence)
Create a new DSL
ALTER SEQUENCE statement. |
<T extends Number> |
alterSequence(Sequence<T> sequence)
Create a new DSL
ALTER SEQUENCE statement. |
AlterSequenceStep<BigInteger> |
alterSequence(String sequence)
Create a new DSL
ALTER SEQUENCE statement. |
AlterSequenceStep<BigInteger> |
alterSequenceIfExists(Name sequence)
Create a new DSL
ALTER SEQUENCE statement. |
<T extends Number> |
alterSequenceIfExists(Sequence<T> sequence)
Create a new DSL
ALTER SEQUENCE statement. |
AlterSequenceStep<BigInteger> |
alterSequenceIfExists(String sequence)
Create a new DSL
ALTER SEQUENCE statement. |
AlterTableStep |
alterTable(Name table)
Create a new DSL
ALTER TABLE statement. |
AlterTableStep |
alterTable(String table)
Create a new DSL
ALTER TABLE statement. |
AlterTableStep |
alterTable(Table<?> table)
Create a new DSL
ALTER TABLE statement. |
AlterTableStep |
alterTableIfExists(Name table)
Create a new DSL
ALTER TABLE statement. |
AlterTableStep |
alterTableIfExists(String table)
Create a new DSL
ALTER TABLE statement. |
AlterTableStep |
alterTableIfExists(Table<?> table)
Create a new DSL
ALTER TABLE statement. |
AlterViewStep |
alterView(Name table)
Create a new DSL
ALTER VIEW statement. |
AlterViewStep |
alterView(String table)
Create a new DSL
ALTER VIEW statement. |
AlterViewStep |
alterView(Table<?> table)
Create a new DSL
ALTER VIEW statement. |
AlterViewStep |
alterViewIfExists(Name table)
Create a new DSL
ALTER VIEW statement. |
AlterViewStep |
alterViewIfExists(String table)
Create a new DSL
ALTER VIEW statement. |
AlterViewStep |
alterViewIfExists(Table<?> table)
Create a new DSL
ALTER VIEW statement. |
void |
attach(Attachable... attachables)
Attach this
DSLContext's underlying Scope.configuration()
to some attachables. |
void |
attach(Collection<? extends Attachable> attachables)
Attach this
DSLContext's underlying Scope.configuration()
to some attachables. |
Batch |
batch(Collection<? extends Query> queries)
Create a batch statement to execute a set of queries in batch mode
(without bind values).
|
Batch |
batch(Queries queries)
Create a batch statement to execute a set of queries in batch mode
(without bind values).
|
Batch |
batch(Query... queries)
Create a batch statement to execute a set of queries in batch mode
(without bind values).
|
BatchBindStep |
batch(Query query)
Create a batch statement to execute a set of queries in batch mode (with
bind values).
|
Batch |
batch(Query query,
Object[]... bindings)
Create a batch statement to execute a set of queries in batch mode (with
bind values).
|
Batch |
batch(String... queries)
Create a batch statement to execute a set of queries in batch mode
(without bind values).
|
BatchBindStep |
batch(String sql)
Create a batch statement to execute a set of queries in batch mode (with
bind values).
|
Batch |
batch(String sql,
Object[]... bindings)
Create a batch statement to execute a set of queries in batch mode (with
bind values).
|
Batch |
batchDelete(Collection<? extends UpdatableRecord<?>> records)
Create a batch statement to execute a set of
DELETE queries
in batch mode (with bind values) according to
UpdatableRecord.delete() sematics. |
Batch |
batchDelete(UpdatableRecord<?>... records)
Create a batch statement to execute a set of
DELETE queries
in batch mode (with bind values) according to
UpdatableRecord.delete() sematics. |
Batch |
batchInsert(Collection<? extends TableRecord<?>> records)
Create a batch statement to execute a set of
INSERT queries
in batch mode (with bind values) according to
TableRecord.insert() semantics. |
Batch |
batchInsert(TableRecord<?>... records)
Create a batch statement to execute a set of
INSERT queries
in batch mode (with bind values) according to
TableRecord.insert() semantics. |
Batch |
batchStore(Collection<? extends UpdatableRecord<?>> records)
Create a batch statement to execute a set of
INSERT and
UPDATE queries in batch mode (with bind values) according to
UpdatableRecord.store() semantics. |
Batch |
batchStore(UpdatableRecord<?>... records)
Create a batch statement to execute a set of
INSERT and
UPDATE queries in batch mode (with bind values) according to
UpdatableRecord.store() semantics. |
Batch |
batchUpdate(Collection<? extends UpdatableRecord<?>> records)
Create a batch statement to execute a set of
UPDATE queries
in batch mode (with bind values) according to
UpdatableRecord.update() semantics. |
Batch |
batchUpdate(UpdatableRecord<?>... records)
Create a batch statement to execute a set of
UPDATE queries
in batch mode (with bind values) according to
UpdatableRecord.update() semantics. |
int |
bind(QueryPart part,
PreparedStatement stmt)
Deprecated.
|
BindContext |
bindContext(PreparedStatement stmt)
Get a new
BindContext for the context of this DSLContext. |
void |
close()
Close the underlying resources, if any resources have been allocated when
constructing this
DSLContext. |
Configuration |
configuration()
The configuration of the current scope.
|
void |
connection(ConnectionRunnable runnable)
Run a
ConnectionRunnable in the context of this
DSLContext's underlying Scope.configuration()'s
Configuration.connectionProvider(). |
<T> T |
connectionResult(ConnectionCallable<T> callable)
Run a
ConnectionCallable in the context of this
DSLContext's underlying Scope.configuration()'s
Configuration.connectionProvider(). |
CreateTableAsStep<Record> |
createGlobalTemporaryTable(Name table)
Create a new DSL
CREATE GLOBAL TEMPORARY TABLE statement. |
CreateTableAsStep<Record> |
createGlobalTemporaryTable(String table)
Create a new DSL
CREATE GLOBAL TEMPORARY TABLE statement. |
CreateTableAsStep<Record> |
createGlobalTemporaryTable(Table<?> table)
Create a new DSL
CREATE GLOBAL TEMPORARY TABLE statement. |
CreateIndexStep |
createIndex(Name index)
Create a new DSL
CREATE INDEX statement. |
CreateIndexStep |
createIndex(String index)
Create a new DSL
CREATE INDEX statement. |
CreateIndexStep |
createIndexIfNotExists(Name index)
Create a new DSL
CREATE INDEX IF NOT EXISTS statement. |
CreateIndexStep |
createIndexIfNotExists(String index)
Create a new DSL
CREATE INDEX IF NOT EXISTS statement. |
CreateSchemaFinalStep |
createSchema(Name schema)
Create a new DSL
CREATE SCHEMA statement. |
CreateSchemaFinalStep |
createSchema(Schema schema)
Create a new DSL
CREATE SCHEMA statement. |
CreateSchemaFinalStep |
createSchema(String schema)
Create a new DSL
CREATE SCHEMA statement. |
CreateSchemaFinalStep |
createSchemaIfNotExists(Name schema)
Create a new DSL
CREATE SCHEMA statement. |
CreateSchemaFinalStep |
createSchemaIfNotExists(Schema schema)
Create a new DSL
CREATE SCHEMA statement. |
CreateSchemaFinalStep |
createSchemaIfNotExists(String schema)
Create a new DSL
CREATE SCHEMA statement. |
CreateSequenceFinalStep |
createSequence(Name sequence)
Create a new DSL
CREATE SEQUENCE statement. |
CreateSequenceFinalStep |
createSequence(Sequence<?> sequence)
Create a new DSL
CREATE SEQUENCE statement. |
CreateSequenceFinalStep |
createSequence(String sequence)
Create a new DSL
CREATE SEQUENCE statement. |
CreateSequenceFinalStep |
createSequenceIfNotExists(Name sequence)
Create a new DSL
CREATE SEQUENCE statement. |
CreateSequenceFinalStep |
createSequenceIfNotExists(Sequence<?> sequence)
Create a new DSL
CREATE SEQUENCE statement. |
CreateSequenceFinalStep |
createSequenceIfNotExists(String sequence)
Create a new DSL
CREATE SEQUENCE statement. |
CreateTableAsStep<Record> |
createTable(Name table)
Create a new DSL
CREATE TABLE statement. |
CreateTableAsStep<Record> |
createTable(String table)
Create a new DSL
CREATE TABLE statement. |
CreateTableAsStep<Record> |
createTable(Table<?> table)
Create a new DSL
CREATE TABLE statement. |
CreateTableAsStep<Record> |
createTableIfNotExists(Name table)
Create a new DSL
CREATE TABLE statement. |
CreateTableAsStep<Record> |
createTableIfNotExists(String table)
Create a new DSL
CREATE TABLE statement. |
CreateTableAsStep<Record> |
createTableIfNotExists(Table<?> table)
Create a new DSL
CREATE TABLE statement. |
CreateTableAsStep<Record> |
createTemporaryTable(Name table)
Create a new DSL
CREATE TEMPORARY TABLE statement. |
CreateTableAsStep<Record> |
createTemporaryTable(String table)
Create a new DSL
CREATE TEMPORARY TABLE statement. |
CreateTableAsStep<Record> |
createTemporaryTable(Table<?> table)
Create a new DSL
CREATE TEMPORARY TABLE statement. |
CreateIndexStep |
createUniqueIndex(Name index)
Create a new DSL
CREATE UNIQUE INDEX statement. |
CreateIndexStep |
createUniqueIndex(String index)
Create a new DSL
CREATE UNIQUE INDEX statement. |
CreateIndexStep |
createUniqueIndexIfNotExists(Name index)
Create a new DSL
CREATE UNIQUE INDEX statement. |
CreateIndexStep |
createUniqueIndexIfNotExists(String index)
Create a new DSL
CREATE UNIQUE INDEX statement. |
CreateViewAsStep<Record> |
createView(Name view,
java.util.function.BiFunction<? super Field<?>,? super Integer,? extends Name> fieldNameFunction)
Create a new DSL
CREATE VIEW statement. |
CreateViewAsStep<Record> |
createView(Name view,
java.util.function.Function<? super Field<?>,? extends Name> fieldNameFunction)
Create a new DSL
CREATE VIEW statement. |
CreateViewAsStep<Record> |
createView(Name view,
Name... fields)
Create a new DSL
CREATE VIEW statement. |
CreateViewAsStep<Record> |
createView(String view,
java.util.function.BiFunction<? super Field<?>,? super Integer,? extends String> fieldNameFunction)
Create a new DSL
CREATE VIEW statement. |
CreateViewAsStep<Record> |
createView(String view,
java.util.function.Function<? super Field<?>,? extends String> fieldNameFunction)
Create a new DSL
CREATE VIEW statement. |
CreateViewAsStep<Record> |
createView(String view,
String... fields)
Create a new DSL
CREATE VIEW statement. |
CreateViewAsStep<Record> |
createView(Table<?> view,
java.util.function.BiFunction<? super Field<?>,? super Integer,? extends Field<?>> fieldNameFunction)
Create a new DSL
CREATE VIEW statement. |
CreateViewAsStep<Record> |
createView(Table<?> view,
Field<?>... fields)
Create a new DSL
CREATE VIEW statement. |
CreateViewAsStep<Record> |
createView(Table<?> view,
java.util.function.Function<? super Field<?>,? extends Field<?>> fieldNameFunction)
Create a new DSL
CREATE VIEW statement. |
CreateViewAsStep<Record> |
createViewIfNotExists(Name view,
java.util.function.BiFunction<? super Field<?>,? super Integer,? extends Name> fieldNameFunction)
Create a new DSL
CREATE VIEW statement. |
CreateViewAsStep<Record> |
createViewIfNotExists(Name view,
java.util.function.Function<? super Field<?>,? extends Name> fieldNameFunction)
Create a new DSL
CREATE VIEW statement. |
CreateViewAsStep<Record> |
createViewIfNotExists(Name view,
Name... fields)
Create a new DSL
CREATE VIEW statement. |
CreateViewAsStep<Record> |
createViewIfNotExists(String view,
java.util.function.BiFunction<? super Field<?>,? super Integer,? extends String> fieldNameFunction)
Create a new DSL
CREATE VIEW statement. |
CreateViewAsStep<Record> |
createViewIfNotExists(String view,
java.util.function.Function<? super Field<?>,? extends String> fieldNameFunction)
Create a new DSL
CREATE VIEW statement. |
CreateViewAsStep<Record> |
createViewIfNotExists(String view,
String... fields)
Create a new DSL
CREATE VIEW statement. |
CreateViewAsStep<Record> |
createViewIfNotExists(Table<?> view,
java.util.function.BiFunction<? super Field<?>,? super Integer,? extends Field<?>> fieldNameFunction)
Create a new DSL
CREATE VIEW statement. |
CreateViewAsStep<Record> |
createViewIfNotExists(Table<?> view,
Field<?>... fields)
Create a new DSL
CREATE VIEW statement. |
CreateViewAsStep<Record> |
createViewIfNotExists(Table<?> view,
java.util.function.Function<? super Field<?>,? extends Field<?>> fieldNameFunction)
Create a new DSL
CREATE VIEW statement. |
<T extends Number> |
currval(Sequence<T> sequence)
Convenience method to fetch the CURRVAL for a sequence directly from this
DSLContext's underlying JDBC Connection. |
BigInteger |
currval(String sequence)
Convenience method to fetch the CURRVAL for a sequence directly from this
DSLContext's underlying JDBC Connection. |
Map<Object,Object> |
data()
Get all custom data from this
Scope. |
Object |
data(Object key)
Get some custom data from this
Scope. |
Object |
data(Object key,
Object value)
Set some custom data to this
Scope. |
Queries |
ddl(Catalog catalog)
Generate the complete creation script for the entire catalog.
|
Queries |
ddl(Catalog schema,
DDLFlag... flags)
Generate a partial creation script for the entire catalog.
|
Queries |
ddl(Schema schema)
Generate the complete creation script for the entire schema.
|
Queries |
ddl(Schema schema,
DDLFlag... flags)
Generate a partial creation script for the entire schema.
|
Queries |
ddl(Table<?> table)
Generate the complete creation script for a table.
|
Queries |
ddl(Table<?> table,
DDLFlag... flags)
Generate a partial creation script for a table.
|
<R extends Record> |
delete(Table<R> table)
Create a new DSL delete statement.
|
<R extends Record> |
deleteFrom(Table<R> table)
Create a new DSL delete statement.
|
<R extends Record> |
deleteQuery(Table<R> table)
Create a new
DeleteQuery |
SQLDialect |
dialect()
The
SQLDialect wrapped by this context. |
DropIndexOnStep |
dropIndex(Name index)
Create a new DSL
DROP INDEX statement. |
DropIndexOnStep |
dropIndex(String index)
Create a new DSL
DROP INDEX statement. |
DropIndexOnStep |
dropIndexIfExists(Name index)
Create a new DSL
DROP INDEX IF EXISTS statement. |
DropIndexOnStep |
dropIndexIfExists(String index)
Create a new DSL
DROP INDEX IF EXISTS statement. |
DropSchemaStep |
dropSchema(Name schema)
Create a new DSL
DROP SCHEMA statement. |
DropSchemaStep |
dropSchema(Schema schema)
Create a new DSL
DROP SCHEMA statement. |
DropSchemaStep |
dropSchema(String schema)
Create a new DSL
DROP SCHEMA statement. |
DropSchemaStep |
dropSchemaIfExists(Name schema)
Create a new DSL
DROP SCHEMA statement. |
DropSchemaStep |
dropSchemaIfExists(Schema schema)
Create a new DSL
DROP SCHEMA statement. |
DropSchemaStep |
dropSchemaIfExists(String schema)
Create a new DSL
DROP SCHEMA statement. |
DropSequenceFinalStep |
dropSequence(Name sequence)
Create a new DSL
DROP SEQUENCE statement. |
DropSequenceFinalStep |
dropSequence(Sequence<?> sequence)
Create a new DSL
DROP SEQUENCE statement. |
DropSequenceFinalStep |
dropSequence(String sequence)
Create a new DSL
DROP SEQUENCE statement. |
DropSequenceFinalStep |
dropSequenceIfExists(Name sequence)
Create a new DSL
DROP SEQUENCE IF EXISTS statement. |
DropSequenceFinalStep |
dropSequenceIfExists(Sequence<?> sequence)
Create a new DSL
DROP SEQUENCE IF EXISTS statement. |
DropSequenceFinalStep |
dropSequenceIfExists(String sequence)
Create a new DSL
DROP SEQUENCE IF EXISTS statement. |
DropTableStep |
dropTable(Name table)
Create a new DSL
DROP TABLE statement. |
DropTableStep |
dropTable(String table)
Create a new DSL
DROP TABLE statement. |
DropTableStep |
dropTable(Table<?> table)
Create a new DSL
DROP TABLE statement. |
DropTableStep |
dropTableIfExists(Name table)
Create a new DSL
DROP TABLE IF EXISTS statement. |
DropTableStep |
dropTableIfExists(String table)
Create a new DSL
DROP TABLE IF EXISTS statement. |
DropTableStep |
dropTableIfExists(Table<?> table)
Create a new DSL
DROP TABLE IF EXISTS statement. |
DropViewFinalStep |
dropView(Name view)
Create a new DSL
DROP VIEW statement. |
DropViewFinalStep |
dropView(String view)
Create a new DSL
DROP VIEW statement. |
DropViewFinalStep |
dropView(Table<?> view)
Create a new DSL
DROP VIEW statement. |
DropViewFinalStep |
dropViewIfExists(Name view)
Create a new DSL
DROP VIEW IF EXISTS statement. |
DropViewFinalStep |
dropViewIfExists(String view)
Create a new DSL
DROP VIEW IF EXISTS statement. |
DropViewFinalStep |
dropViewIfExists(Table<?> view)
Create a new DSL
DROP VIEW IF EXISTS statement. |
int |
execute(Query query)
Execute a
Query in the context of this DSLContext. |
int |
execute(SQL sql)
Execute a query holding plain SQL.
|
int |
execute(String sql)
Execute a query holding plain SQL.
|
int |
execute(String sql,
Object... bindings)
Execute a new query holding plain SQL.
|
int |
execute(String sql,
QueryPart... parts)
Execute a new query holding plain SQL.
|
<R extends UpdatableRecord<R>> |
executeDelete(R record)
Delete a record from a table.
|
<R extends TableRecord<R>,T> |
executeDelete(R record,
Condition condition)
Delete a record from a table.
|
<R extends TableRecord<R>> |
executeInsert(R record)
Insert one record.
|
<R extends UpdatableRecord<R>> |
executeUpdate(R record)
Update a table.
|
<R extends TableRecord<R>,T> |
executeUpdate(R record,
Condition condition)
Update a table.
|
List<Object> |
extractBindValues(QueryPart part)
Retrieve the bind values that will be bound by a given
QueryPart. |
Param<?> |
extractParam(QueryPart part,
String name)
Get a named parameter from a
QueryPart, provided its name. |
Map<String,Param<?>> |
extractParams(QueryPart part)
Get a
Map of named parameters. |
SQLDialect |
family()
The
SQLDialect.family() wrapped by this context. |
<R extends Record> |
fetch(ResultQuery<R> query)
Execute a
ResultQuery in the context of this DSLContext and return
results. |
Result<Record> |
fetch(ResultSet rs)
|
Result<Record> |
fetch(ResultSet rs,
Class<?>... types)
|
Result<Record> |
fetch(ResultSet rs,
DataType<?>... types)
|
Result<Record> |
fetch(ResultSet rs,
Field<?>... fields)
|
Result<Record> |
fetch(SQL sql)
Execute a new query holding plain SQL.
|
Result<Record> |
fetch(String sql)
Execute a new query holding plain SQL.
|
Result<Record> |
fetch(String sql,
Object... bindings)
Execute a new query holding plain SQL.
|
Result<Record> |
fetch(String sql,
QueryPart... parts)
Execute a new query holding plain SQL.
|
<R extends Record> |
fetch(Table<R> table)
Execute and return all records for
SELECT * FROM [table]. |
<R extends Record> |
fetch(Table<R> table,
Condition condition)
Execute and return all records for
SELECT * FROM [table] WHERE [condition] . |
<R extends Record> |
fetchAny(Table<R> table)
Execute and return zero or one record for
SELECT * FROM [table] LIMIT 1. |
<R extends Record> |
fetchAny(Table<R> table,
Condition condition)
Execute and return zero or one record for
SELECT * FROM [table] WHERE [condition] LIMIT 1. |
<R extends Record> |
fetchAsync(Executor executor,
ResultQuery<R> query)
Fetch results in a new
CompletionStage that is asynchronously
completed by a task running in the given executor. |
CompletionStage<Result<Record>> |
fetchAsync(Executor executor,
ResultSet rs)
Fetch results in a new
CompletionStage that is asynchronously
completed by a task running in the given executor. |
CompletionStage<Result<Record>> |
fetchAsync(Executor executor,
ResultSet rs,
Class<?>... types)
Fetch results in a new
CompletionStage that is asynchronously
completed by a task running in the given executor. |
CompletionStage<Result<Record>> |
fetchAsync(Executor executor,
ResultSet rs,
DataType<?>... types)
Fetch results in a new
CompletionStage that is asynchronously
completed by a task running in the given executor. |
CompletionStage<Result<Record>> |
fetchAsync(Executor executor,
ResultSet rs,
Field<?>... fields)
Fetch results in a new
CompletionStage that is asynchronously
completed by a task running in the given executor. |
CompletionStage<Result<Record>> |
fetchAsync(Executor executor,
SQL sql)
Fetch results in a new
CompletionStage that is asynchronously
completed by a task running in the given executor. |
CompletionStage<Result<Record>> |
fetchAsync(Executor executor,
String sql)
Fetch results in a new
CompletionStage that is asynchronously
completed by a task running in the given executor. |
CompletionStage<Result<Record>> |
fetchAsync(Executor executor,
String sql,
Object... bindings)
Fetch results in a new
CompletionStage that is asynchronously
completed by a task running in the given executor. |
CompletionStage<Result<Record>> |
fetchAsync(Executor executor,
String sql,
QueryPart... parts)
Fetch results in a new
CompletionStage that is asynchronously
completed by a task running in the given executor. |
<R extends Record> |
fetchAsync(Executor executor,
Table<R> table)
Execute and return all records asynchronously for
SELECT * FROM [table]. |
<R extends Record> |
fetchAsync(Executor executor,
Table<R> table,
Condition condition)
Execute and return all records asynchronously for
SELECT * FROM [table] WHERE [condition] . |
<R extends Record> |
fetchAsync(ResultQuery<R> query)
Fetch results in a new
CompletionStage. |
CompletionStage<Result<Record>> |
fetchAsync(ResultSet rs)
Fetch results in a new
CompletionStage. |
CompletionStage<Result<Record>> |
fetchAsync(ResultSet rs,
Class<?>... types)
Fetch results in a new
CompletionStage. |
CompletionStage<Result<Record>> |
fetchAsync(ResultSet rs,
DataType<?>... types)
Fetch results in a new
CompletionStage. |
CompletionStage<Result<Record>> |
fetchAsync(ResultSet rs,
Field<?>... fields)
Fetch results in a new
CompletionStage. |
CompletionStage<Result<Record>> |
fetchAsync(SQL sql)
Fetch results in a new
CompletionStage. |
CompletionStage<Result<Record>> |
fetchAsync(String sql)
Fetch results in a new
CompletionStage. |
CompletionStage<Result<Record>> |
fetchAsync(String sql,
Object... bindings)
Fetch results in a new
CompletionStage. |
CompletionStage<Result<Record>> |
fetchAsync(String sql,
QueryPart... parts)
Fetch results in a new
CompletionStage. |
<R extends Record> |
fetchAsync(Table<R> table)
Execute and return all records asynchronously for
SELECT * FROM [table]. |
<R extends Record> |
fetchAsync(Table<R> table,
Condition condition)
Execute and return all records asynchronously for
SELECT * FROM [table] WHERE [condition] . |
int |
fetchCount(Select<?> query)
|
int |
fetchCount(Table<?> table)
Count the number of records in a table.
|
int |
fetchCount(Table<?> table,
Condition condition)
Count the number of records in a table that satisfy a condition.
|
boolean |
fetchExists(Select<?> query)
Check if a
Select would return any records, if it were executed. |
boolean |
fetchExists(Table<?> table)
Check if a table has any records.
|
boolean |
fetchExists(Table<?> table,
Condition condition)
Check if a table has any records that satisfy a condition.
|
Result<Record> |
fetchFromCSV(String string)
Fetch all data from a CSV string.
|
Result<Record> |
fetchFromCSV(String string,
boolean header)
Fetch all data from a CSV string.
|
Result<Record> |
fetchFromCSV(String string,
boolean header,
char delimiter)
Fetch all data from a CSV string.
|
Result<Record> |
fetchFromCSV(String string,
char delimiter)
Fetch all data from a CSV string.
|
Result<Record> |
fetchFromHTML(String string)
Convert an HTML table into a jOOQ
Result. |
Result<Record> |
fetchFromJSON(String string)
Fetch all data from a JSON string.
|
Result<Record> |
fetchFromStringData(List<String[]> strings)
Fetch all data from a list of strings.
|
Result<Record> |
fetchFromStringData(List<String[]> strings,
boolean header)
Fetch all data from a list of strings.
|
Result<Record> |
fetchFromStringData(String[]... strings)
Fetch all data from a list of strings.
|
Result<Record> |
fetchFromTXT(String string)
Fetch all data from a formatted string.
|
Result<Record> |
fetchFromTXT(String string,
String nullLiteral)
Fetch all data from a formatted string.
|
<R extends Record> |
fetchLazy(ResultQuery<R> query)
Execute a
ResultQuery in the context of this DSLContext and return
a cursor. |
Cursor<Record> |
fetchLazy(ResultSet rs)
|
Cursor<Record> |
fetchLazy(ResultSet rs,
Class<?>... types)
|
Cursor<Record> |
fetchLazy(ResultSet rs,
DataType<?>... types)
|
Cursor<Record> |
fetchLazy(ResultSet rs,
Field<?>... fields)
|
Cursor<Record> |
fetchLazy(SQL sql)
Execute a new query holding plain SQL and "lazily" return the generated
result.
|
Cursor<Record> |
fetchLazy(String sql)
Execute a new query holding plain SQL and "lazily" return the generated
result.
|
Cursor<Record> |
fetchLazy(String sql,
Object... bindings)
Execute a new query holding plain SQL and "lazily" return the generated
result.
|
Cursor<Record> |
fetchLazy(String sql,
QueryPart... parts)
Execute a new query holding plain SQL and "lazily" return the generated
result.
|
<R extends Record> |
fetchLazy(Table<R> table)
Execute and return all records lazily for
SELECT * FROM [table]. |
<R extends Record> |
fetchLazy(Table<R> table,
Condition condition)
Execute and return all records lazily for
SELECT * FROM [table] WHERE [condition] . |
<R extends Record> |
fetchMany(ResultQuery<R> query)
Execute a
ResultQuery in the context of this DSLContext and return
a cursor. |
Results |
fetchMany(SQL sql)
Execute a new query holding plain SQL, possibly returning several result
sets.
|
Results |
fetchMany(String sql)
Execute a new query holding plain SQL, possibly returning several result
sets.
|
Results |
fetchMany(String sql,
Object... bindings)
Execute a new query holding plain SQL, possibly returning several result
sets.
|
Results |
fetchMany(String sql,
QueryPart... parts)
Execute a new query holding plain SQL, possibly returning several result
sets.
|
<R extends Record> |
fetchOne(ResultQuery<R> query)
Execute a
ResultQuery in the context of this DSLContext and return
a record. |
Record |
fetchOne(ResultSet rs)
|
Record |
fetchOne(ResultSet rs,
Class<?>... types)
|
Record |
fetchOne(ResultSet rs,
DataType<?>... types)
|
Record |
fetchOne(ResultSet rs,
Field<?>... fields)
|
Record |
fetchOne(SQL sql)
Execute a new query holding plain SQL.
|
Record |
fetchOne(String sql)
Execute a new query holding plain SQL.
|
Record |
fetchOne(String sql,
Object... bindings)
Execute a new query holding plain SQL.
|
Record |
fetchOne(String sql,
QueryPart... parts)
Execute a new query holding plain SQL.
|
<R extends Record> |
fetchOne(Table<R> table)
Execute and return zero or one record for
SELECT * FROM [table]. |
<R extends Record> |
fetchOne(Table<R> table,
Condition condition)
Execute and return zero or one record for
SELECT * FROM [table] WHERE [condition] . |
<R extends Record> |
fetchOptional(ResultQuery<R> query)
Execute a
ResultQuery in the context of this DSLContext and return
a record. |
Optional<Record> |
fetchOptional(ResultSet rs)
|
Optional<Record> |
fetchOptional(ResultSet rs,
Class<?>... types)
|
Optional<Record> |
fetchOptional(ResultSet rs,
DataType<?>... types)
|
Optional<Record> |
fetchOptional(ResultSet rs,
Field<?>... fields)
|
Optional<Record> |
fetchOptional(SQL sql)
Execute a new query holding plain SQL.
|
Optional<Record> |
fetchOptional(String sql)
Execute a new query holding plain SQL.
|
Optional<Record> |
fetchOptional(String sql,
Object... bindings)
Execute a new query holding plain SQL.
|
Optional<Record> |
fetchOptional(String sql,
QueryPart... parts)
Execute a new query holding plain SQL.
|
<R extends Record> |
fetchOptional(Table<R> table)
Execute and return zero or one record for
SELECT * FROM [table]. |
<R extends Record> |
fetchOptional(Table<R> table,
Condition condition)
Execute and return zero or one record for
SELECT * FROM [table] WHERE [condition] . |
<T,R extends Record1<T>> |
fetchOptionalValue(ResultQuery<R> query)
Execute a
ResultQuery in the context of this
DSLContext and return a single value. |
Optional<?> |
fetchOptionalValue(ResultSet rs)
Fetch a record from a JDBC
ResultSet and return the only
contained value. |
<T> Optional<T> |
fetchOptionalValue(ResultSet rs,
Class<T> type)
Fetch a record from a JDBC
ResultSet and return the only
contained value. |
<T> Optional<T> |
fetchOptionalValue(ResultSet rs,
DataType<T> type)
Fetch a record from a JDBC
ResultSet and return the only
contained value. |
<T> Optional<T> |
fetchOptionalValue(ResultSet rs,
Field<T> field)
Fetch a record from a JDBC
ResultSet and return the only
contained value. |
Optional<?> |
fetchOptionalValue(SQL sql)
Execute a new query holding plain SQL.
|
Optional<?> |
fetchOptionalValue(String sql)
Execute a new query holding plain SQL.
|
Optional<?> |
fetchOptionalValue(String sql,
Object... bindings)
Execute a new query holding plain SQL.
|
Optional<?> |
fetchOptionalValue(String sql,
QueryPart... parts)
Execute a new query holding plain SQL.
|
<T> Optional<T> |
fetchOptionalValue(TableField<?,T> field)
Execute a
ResultQuery in the context of this
DSLContext and return a single value. |
<R extends Record> |
fetchStream(ResultQuery<R> query)
Execute a
ResultQuery in the context of this DSLContext and return
a stream. |
java.util.stream.Stream<Record> |
fetchStream(ResultSet rs)
|
java.util.stream.Stream<Record> |
fetchStream(ResultSet rs,
Class<?>... types)
|
java.util.stream.Stream<Record> |
fetchStream(ResultSet rs,
DataType<?>... types)
|
java.util.stream.Stream<Record> |
fetchStream(ResultSet rs,
Field<?>... fields)
|
java.util.stream.Stream<Record> |
fetchStream(SQL sql)
Execute a new query holding plain SQL and "lazily" return the generated
result.
|
java.util.stream.Stream<Record> |
fetchStream(String sql)
Execute a new query holding plain SQL and "lazily" return the generated
result.
|
java.util.stream.Stream<Record> |
fetchStream(String sql,
Object... bindings)
Execute a new query holding plain SQL and "lazily" return the generated
result.
|
java.util.stream.Stream<Record> |
fetchStream(String sql,
QueryPart... parts)
Execute a new query holding plain SQL and "lazily" return the generated
result.
|
<R extends Record> |
fetchStream(Table<R> table)
Execute and return all records lazily for
SELECT * FROM [table]. |
<R extends Record> |
fetchStream(Table<R> table,
Condition condition)
Execute and return all records lazily for
SELECT * FROM [table] WHERE [condition] . |
<T,R extends Record1<T>> |
fetchValue(ResultQuery<R> query)
Execute a
ResultQuery in the context of this
DSLContext and return a single value. |
Object |
fetchValue(ResultSet rs)
Fetch a record from a JDBC
ResultSet and return the only
contained value. |
<T> T |
fetchValue(ResultSet rs,
Class<T> type)
Fetch a record from a JDBC
ResultSet and return the only
contained value. |
<T> T |
fetchValue(ResultSet rs,
DataType<T> type)
Fetch a record from a JDBC
ResultSet and return the only
contained value. |
<T> T |
fetchValue(ResultSet rs,
Field<T> field)
Fetch a record from a JDBC
ResultSet and return the only
contained value. |
Object |
fetchValue(SQL sql)
Execute a new query holding plain SQL.
|
Object |
fetchValue(String sql)
Execute a new query holding plain SQL.
|
Object |
fetchValue(String sql,
Object... bindings)
Execute a new query holding plain SQL.
|
Object |
fetchValue(String sql,
QueryPart... parts)
Execute a new query holding plain SQL.
|
<T> T |
fetchValue(TableField<?,T> field)
Execute a
ResultQuery in the context of this
DSLContext and return a single value. |
<T,R extends Record1<T>> |
fetchValues(ResultQuery<R> query)
Execute a
ResultQuery in the context of this
DSLContext and return all values for the only column. |
List<?> |
fetchValues(ResultSet rs)
Fetch a result from a JDBC
ResultSet and return the only
contained column's values. |
<T> List<T> |
fetchValues(ResultSet rs,
Class<T> type)
Fetch a result from a JDBC
ResultSet and return the only
contained column's values. |
<T> List<T> |
fetchValues(ResultSet rs,
DataType<T> type)
Fetch a result from a JDBC
ResultSet and return the only
contained column's values. |
<T> List<T> |
fetchValues(ResultSet rs,
Field<T> field)
Fetch a result from a JDBC
ResultSet and return the only
contained column's values. |
List<?> |
fetchValues(SQL sql)
Execute a new query holding plain SQL.
|
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.
|
<T> List<T> |
fetchValues(TableField<?,T> field)
Fetch all values in a given
Table's TableField |
InformationSchema |
informationSchema(Catalog... catalogs)
Export a set of catalogs to the
InformationSchema format. |
InformationSchema |
informationSchema(Catalog catalog)
Export a catalog to the
InformationSchema format. |
InformationSchema |
informationSchema(Schema... schemas)
Export a set of schemas to the
InformationSchema format. |
InformationSchema |
informationSchema(Schema schema)
Export a schema to the
InformationSchema format. |
InformationSchema |
informationSchema(Table<?>... tables)
Export a set of tables to the
InformationSchema format. |
InformationSchema |
informationSchema(Table<?> table)
Export a table to the
InformationSchema format. |
<R extends Record> |
insertInto(Table<R> into)
Create a new DSL insert statement.
|
<R extends Record> |
insertInto(Table<R> into,
Collection<? extends Field<?>> fields)
Create a new DSL insert statement.
|
<R extends Record> |
insertInto(Table<R> into,
Field<?>... fields)
Create a new DSL insert statement.
|
<R extends Record,T1> |
insertInto(Table<R> into,
Field<T1> field1)
Create a new DSL insert statement.
|
<R extends Record,T1,T2> |
insertInto(Table<R> into,
Field<T1> field1,
Field<T2> field2)
Create a new DSL insert statement.
|
<R extends Record,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> |
insertInto(Table<R> into,
Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4)
Create a new DSL insert statement.
|
<R extends Record,T1,T2,T3,T4,T5> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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(Table<R> into)
Create a new
InsertQuery |
BigInteger |
lastID()
Retrieve the last inserted ID.
|
<R extends Record> |
loadInto(Table<R> table)
Create a new
Loader object to load data from a CSV or XML
source. |
Schema |
map(Schema schema)
Map a schema to another one.
|
<R extends Record> |
map(Table<R> table)
Map a table to another one.
|
<R extends Record> |
mergeInto(Table<R> table)
Create a new DSL SQL standard MERGE statement.
|
<R extends Record> |
mergeInto(Table<R> table,
Collection<? extends Field<?>> fields)
Create a new DSL merge statement (H2-specific syntax).
|
<R extends Record> |
mergeInto(Table<R> table,
Field<?>... fields)
|
<R extends Record,T1> |
mergeInto(Table<R> table,
Field<T1> field1)
|
<R extends Record,T1,T2> |
mergeInto(Table<R> table,
Field<T1> field1,
Field<T2> field2)
|
<R extends Record,T1,T2,T3> |
mergeInto(Table<R> table,
Field<T1> field1,
Field<T2> field2,
Field<T3> field3)
|
<R extends Record,T1,T2,T3,T4> |
mergeInto(Table<R> table,
Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4)
|
<R extends Record,T1,T2,T3,T4,T5> |
mergeInto(Table<R> table,
Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5)
|
<R extends Record,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)
|
<R extends Record,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)
|
<R extends Record,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)
|
<R extends Record,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)
|
<R extends Record,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)
|
<R extends Record,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)
|
<R extends Record,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)
|
<R extends Record,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)
|
<R extends Record,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)
|
<R extends Record,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)
|
<R extends Record,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)
|
<R extends Record,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)
|
<R extends Record,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)
|
<R extends Record,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)
|
<R extends Record,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)
|
<R extends Record,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)
|
<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> |
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)
|
Meta |
meta()
Access the database meta data.
|
Meta |
meta(InformationSchema schema)
Access the databse meta data from its serialised form.
|
void |
mock(MockDataProvider provider,
MockRunnable mockable)
Run a
MockRunnable in the context of this DSLContext
's underlying Scope.configuration()'s, and of a
MockDataProvider. |
<T> T |
mockResult(MockDataProvider provider,
MockCallable<T> mockable)
Run a
MockRunnable in the context of this DSLContext
's underlying Scope.configuration()'s, and of a
MockDataProvider and return the mockable's outcome. |
Record |
newRecord(Field<?>... fields)
Create a new empty
Record. |
<T1> Record1<T1> |
newRecord(Field<T1> field1)
Create a new empty
Record. |
<T1,T2> Record2<T1,T2> |
newRecord(Field<T1> field1,
Field<T2> field2)
Create a new empty
Record. |
<T1,T2,T3> Record3<T1,T2,T3> |
newRecord(Field<T1> field1,
Field<T2> field2,
Field<T3> field3)
Create a new empty
Record. |
<T1,T2,T3,T4> |
newRecord(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4)
Create a new empty
Record. |
<T1,T2,T3,T4,T5> |
newRecord(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5)
Create a new empty
Record. |
<T1,T2,T3,T4,T5,T6> |
newRecord(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6)
Create a new empty
Record. |
<T1,T2,T3,T4,T5,T6,T7> |
newRecord(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7)
Create a new empty
Record. |
<T1,T2,T3,T4,T5,T6,T7,T8> |
newRecord(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8)
Create a new empty
Record. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9> |
newRecord(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9)
Create a new empty
Record. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10> |
newRecord(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10)
Create a new empty
Record. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11> |
newRecord(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11)
Create a new empty
Record. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12> |
newRecord(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11,
Field<T12> field12)
Create a new empty
Record. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13> |
newRecord(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11,
Field<T12> field12,
Field<T13> field13)
Create a new empty
Record. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14> |
newRecord(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11,
Field<T12> field12,
Field<T13> field13,
Field<T14> field14)
Create a new empty
Record. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15> |
newRecord(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11,
Field<T12> field12,
Field<T13> field13,
Field<T14> field14,
Field<T15> field15)
Create a new empty
Record. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16> |
newRecord(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11,
Field<T12> field12,
Field<T13> field13,
Field<T14> field14,
Field<T15> field15,
Field<T16> field16)
Create a new empty
Record. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17> |
newRecord(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11,
Field<T12> field12,
Field<T13> field13,
Field<T14> field14,
Field<T15> field15,
Field<T16> field16,
Field<T17> field17)
Create a new empty
Record. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18> |
newRecord(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11,
Field<T12> field12,
Field<T13> field13,
Field<T14> field14,
Field<T15> field15,
Field<T16> field16,
Field<T17> field17,
Field<T18> field18)
Create a new empty
Record. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19> |
newRecord(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11,
Field<T12> field12,
Field<T13> field13,
Field<T14> field14,
Field<T15> field15,
Field<T16> field16,
Field<T17> field17,
Field<T18> field18,
Field<T19> field19)
Create a new empty
Record. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20> |
newRecord(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11,
Field<T12> field12,
Field<T13> field13,
Field<T14> field14,
Field<T15> field15,
Field<T16> field16,
Field<T17> field17,
Field<T18> field18,
Field<T19> field19,
Field<T20> field20)
Create a new empty
Record. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21> |
newRecord(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11,
Field<T12> field12,
Field<T13> field13,
Field<T14> field14,
Field<T15> field15,
Field<T16> field16,
Field<T17> field17,
Field<T18> field18,
Field<T19> field19,
Field<T20> field20,
Field<T21> field21)
Create a new empty
Record. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22> |
newRecord(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11,
Field<T12> field12,
Field<T13> field13,
Field<T14> field14,
Field<T15> field15,
Field<T16> field16,
Field<T17> field17,
Field<T18> field18,
Field<T19> field19,
Field<T20> field20,
Field<T21> field21,
Field<T22> field22)
Create a new empty
Record. |
<R extends Record> |
newRecord(Table<R> table)
Create a new
Record that can be inserted into the corresponding
table. |
<R extends Record> |
newRecord(Table<R> table,
Object source)
Create a new pre-filled
Record that can be inserted into the
corresponding table. |
<R extends UDTRecord<R>> |
newRecord(UDT<R> type)
Create a new
UDTRecord. |
Result<Record> |
newResult(Field<?>... fields)
Create a new empty
Record. |
<T1> Result<Record1<T1>> |
newResult(Field<T1> field1)
Create a new empty
Result. |
<T1,T2> Result<Record2<T1,T2>> |
newResult(Field<T1> field1,
Field<T2> field2)
Create a new empty
Result. |
<T1,T2,T3> Result<Record3<T1,T2,T3>> |
newResult(Field<T1> field1,
Field<T2> field2,
Field<T3> field3)
Create a new empty
Result. |
<T1,T2,T3,T4> |
newResult(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4)
Create a new empty
Result. |
<T1,T2,T3,T4,T5> |
newResult(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5)
Create a new empty
Result. |
<T1,T2,T3,T4,T5,T6> |
newResult(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6)
Create a new empty
Result. |
<T1,T2,T3,T4,T5,T6,T7> |
newResult(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7)
Create a new empty
Result. |
<T1,T2,T3,T4,T5,T6,T7,T8> |
newResult(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8)
Create a new empty
Result. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9> |
newResult(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9)
Create a new empty
Result. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10> |
newResult(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10)
Create a new empty
Result. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11> |
newResult(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11)
Create a new empty
Result. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12> |
newResult(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11,
Field<T12> field12)
Create a new empty
Result. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13> |
newResult(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11,
Field<T12> field12,
Field<T13> field13)
Create a new empty
Result. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14> |
newResult(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11,
Field<T12> field12,
Field<T13> field13,
Field<T14> field14)
Create a new empty
Result. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15> |
newResult(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11,
Field<T12> field12,
Field<T13> field13,
Field<T14> field14,
Field<T15> field15)
Create a new empty
Result. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16> |
newResult(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11,
Field<T12> field12,
Field<T13> field13,
Field<T14> field14,
Field<T15> field15,
Field<T16> field16)
Create a new empty
Result. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17> |
newResult(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11,
Field<T12> field12,
Field<T13> field13,
Field<T14> field14,
Field<T15> field15,
Field<T16> field16,
Field<T17> field17)
Create a new empty
Result. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18> |
newResult(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11,
Field<T12> field12,
Field<T13> field13,
Field<T14> field14,
Field<T15> field15,
Field<T16> field16,
Field<T17> field17,
Field<T18> field18)
Create a new empty
Result. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19> |
newResult(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11,
Field<T12> field12,
Field<T13> field13,
Field<T14> field14,
Field<T15> field15,
Field<T16> field16,
Field<T17> field17,
Field<T18> field18,
Field<T19> field19)
Create a new empty
Result. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20> |
newResult(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11,
Field<T12> field12,
Field<T13> field13,
Field<T14> field14,
Field<T15> field15,
Field<T16> field16,
Field<T17> field17,
Field<T18> field18,
Field<T19> field19,
Field<T20> field20)
Create a new empty
Result. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21> |
newResult(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11,
Field<T12> field12,
Field<T13> field13,
Field<T14> field14,
Field<T15> field15,
Field<T16> field16,
Field<T17> field17,
Field<T18> field18,
Field<T19> field19,
Field<T20> field20,
Field<T21> field21)
Create a new empty
Result. |
<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22> |
newResult(Field<T1> field1,
Field<T2> field2,
Field<T3> field3,
Field<T4> field4,
Field<T5> field5,
Field<T6> field6,
Field<T7> field7,
Field<T8> field8,
Field<T9> field9,
Field<T10> field10,
Field<T11> field11,
Field<T12> field12,
Field<T13> field13,
Field<T14> field14,
Field<T15> field15,
Field<T16> field16,
Field<T17> field17,
Field<T18> field18,
Field<T19> field19,
Field<T20> field20,
Field<T21> field21,
Field<T22> field22)
Create a new empty
Result. |
<R extends Record> |
newResult(Table<R> table)
Create a new empty
Result. |
<T extends Number> |
nextval(Sequence<T> sequence)
Convenience method to fetch the NEXTVAL for a sequence directly from this
DSLContext's underlying JDBC Connection. |
BigInteger |
nextval(String sequence)
Convenience method to fetch the NEXTVAL for a sequence directly from this
DSLContext's underlying JDBC Connection. |
Parser |
parser()
Deprecated.
|
Query |
query(SQL sql)
Create a new query holding plain SQL.
|
Query |
query(String sql)
Create a new query holding plain SQL.
|
Query |
query(String sql,
Object... bindings)
Create a new query holding plain SQL.
|
Query |
query(String sql,
QueryPart... parts)
Create a new query holding plain SQL.
|
String |
render(QueryPart part)
Render a QueryPart in the context of this
DSLContext. |
RenderContext |
renderContext()
Get a new
RenderContext for the context of this DSLContext. |
String |
renderInlined(QueryPart part)
Render a QueryPart in the context of this
DSLContext, inlining all bind
variables. |
String |
renderNamedOrInlinedParams(QueryPart part)
Render a QueryPart in the context of this
DSLContext, rendering bind
variables as named parameters, or inlined parameters if they have no name. |
String |
renderNamedParams(QueryPart part)
Render a QueryPart in the context of this
DSLContext, rendering bind
variables as named parameters. |
ResultQuery<Record> |
resultQuery(SQL sql)
Create a new query holding plain SQL.
|
ResultQuery<Record> |
resultQuery(String sql)
Create a new query holding plain SQL.
|
ResultQuery<Record> |
resultQuery(String sql,
Object... bindings)
Create a new query holding plain SQL.
|
ResultQuery<Record> |
resultQuery(String sql,
QueryPart... parts)
Create a new query holding plain SQL.
|
SelectSelectStep<Record> |
select(Collection<? extends SelectField<?>> fields)
Create a new DSL select statement.
|
SelectSelectStep<Record> |
select(SelectField<?>... fields)
Create a new DSL select statement.
|
<T1> SelectSelectStep<Record1<T1>> |
select(SelectField<T1> field1)
Create a new DSL select statement.
|
<T1,T2> SelectSelectStep<Record2<T1,T2>> |
select(SelectField<T1> field1,
SelectField<T2> field2)
Create a new DSL select statement.
|
<T1,T2,T3> SelectSelectStep<Record3<T1,T2,T3>> |
select(SelectField<T1> field1,
SelectField<T2> field2,
SelectField<T3> field3)
Create a new DSL select statement.
|
<T1,T2,T3,T4> |
select(SelectField<T1> field1,
SelectField<T2> field2,
SelectField<T3> field3,
SelectField<T4> field4)
Create a new DSL select statement.
|
<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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
select(SelectField<T1> field1,
SelectField<T2> field2,
SelectField<T3> field3,
SelectField<T4> field4,
SelectField<T5> field5,
SelectField<T6> field6,
SelectField<T7> field7,
SelectField<T8> field8,
SelectField<T9> field9,
SelectField<T10> field10,
SelectField<T11> field11,
SelectField<T12> field12,
SelectField<T13> field13,
SelectField<T14> field14,
SelectField<T15> field15,
SelectField<T16> field16,
SelectField<T17> field17,
SelectField<T18> field18,
SelectField<T19> field19,
SelectField<T20> field20,
SelectField<T21> field21,
SelectField<T22> field22)
Create a new DSL select statement.
|
SelectSelectStep<Record1<Integer>> |
selectCount()
Create a new DSL select statement for
COUNT(*). |
SelectSelectStep<Record> |
selectDistinct(Collection<? extends SelectField<?>> fields)
Create a new DSL select statement.
|
SelectSelectStep<Record> |
selectDistinct(SelectField<?>... fields)
Create a new DSL select statement.
|
<T1> SelectSelectStep<Record1<T1>> |
selectDistinct(SelectField<T1> field1)
Create a new DSL select statement.
|
<T1,T2> SelectSelectStep<Record2<T1,T2>> |
selectDistinct(SelectField<T1> field1,
SelectField<T2> field2)
Create a new DSL select statement.
|
<T1,T2,T3> SelectSelectStep<Record3<T1,T2,T3>> |
selectDistinct(SelectField<T1> field1,
SelectField<T2> field2,
SelectField<T3> field3)
Create a new DSL select statement.
|
<T1,T2,T3,T4> |
selectDistinct(SelectField<T1> field1,
SelectField<T2> field2,
SelectField<T3> field3,
SelectField<T4> field4)
Create a new DSL select statement.
|
<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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
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> |
selectDistinct(SelectField<T1> field1,
SelectField<T2> field2,
SelectField<T3> field3,
SelectField<T4> field4,
SelectField<T5> field5,
SelectField<T6> field6,
SelectField<T7> field7,
SelectField<T8> field8,
SelectField<T9> field9,
SelectField<T10> field10,
SelectField<T11> field11,
SelectField<T12> field12,
SelectField<T13> field13,
SelectField<T14> field14,
SelectField<T15> field15,
SelectField<T16> field16,
SelectField<T17> field17,
SelectField<T18> field18,
SelectField<T19> field19,
SelectField<T20> field20,
SelectField<T21> field21,
SelectField<T22> field22)
Create a new DSL select statement.
|
<R extends Record> |
selectFrom(Table<R> table)
Create a new DSL select statement.
|
SelectSelectStep<Record1<Integer>> |
selectOne()
Create a new DSL select statement for a constant
1 literal. |
SelectQuery<Record> |
selectQuery()
Create a new
SelectQuery |
<R extends Record> |
selectQuery(TableLike<R> table)
Create a new
SelectQuery |
SelectSelectStep<Record1<Integer>> |
selectZero()
Create a new DSL select statement for a constant
0 literal. |
Settings |
settings()
The settings wrapped by this context.
|
String |
toString() |
void |
transaction(ContextTransactionalRunnable transactional)
Run a
ContextTransactionalRunnable in the context of this
DSLContext's underlying Scope.configuration()'s
Configuration.transactionProvider(). |
void |
transaction(TransactionalRunnable transactional)
Run a
TransactionalRunnable in the context of this
DSLContext's underlying Scope.configuration()'s
Configuration.transactionProvider(). |
CompletionStage<Void> |
transactionAsync(Executor executor,
TransactionalRunnable transactional)
Run a
TransactionalRunnable asynchronously. |
CompletionStage<Void> |
transactionAsync(TransactionalRunnable transactional)
Run a
TransactionalRunnable asynchronously. |
<T> T |
transactionResult(ContextTransactionalCallable<T> transactional)
Run a
ContextTransactionalRunnable in the context of this
DSLContext's underlying Scope.configuration()'s
Configuration.transactionProvider(), and return the
transactional's outcome. |
<T> T |
transactionResult(TransactionalCallable<T> transactional)
Run a
TransactionalCallable in the context of this
DSLContext's underlying Scope.configuration()'s
Configuration.transactionProvider(), and return the
transactional's outcome. |
<T> CompletionStage<T> |
transactionResultAsync(Executor executor,
TransactionalCallable<T> transactional)
Run a
TransactionalCallable asynchronously. |
<T> CompletionStage<T> |
transactionResultAsync(TransactionalCallable<T> transactional)
Run a
TransactionalCallable asynchronously. |
TruncateIdentityStep<Record> |
truncate(Name table)
Create a new DSL truncate statement.
|
TruncateIdentityStep<Record> |
truncate(String table)
Create a new DSL truncate statement.
|
<R extends Record> |
truncate(Table<R> table)
Create a new DSL truncate statement.
|
<R extends Record> |
update(Table<R> table)
Create a new DSL update statement.
|
<R extends Record> |
updateQuery(Table<R> table)
Create a new
UpdateQuery |
WithStep |
with(CommonTableExpression<?>... tables)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep |
with(String alias)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep |
with(String alias,
java.util.function.BiFunction<? super Field<?>,? super Integer,? extends String> fieldNameFunction)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep |
with(String alias,
java.util.function.Function<? super Field<?>,? extends String> fieldNameFunction)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep |
with(String alias,
String... fieldAliases)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep1 |
with(String alias,
String fieldAlias1)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep2 |
with(String alias,
String fieldAlias1,
String fieldAlias2)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep3 |
with(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep4 |
with(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep5 |
with(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep6 |
with(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep7 |
with(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep8 |
with(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep9 |
with(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep10 |
with(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep11 |
with(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep12 |
with(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11,
String fieldAlias12)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep13 |
with(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11,
String fieldAlias12,
String fieldAlias13)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep14 |
with(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11,
String fieldAlias12,
String fieldAlias13,
String fieldAlias14)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep15 |
with(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11,
String fieldAlias12,
String fieldAlias13,
String fieldAlias14,
String fieldAlias15)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep16 |
with(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11,
String fieldAlias12,
String fieldAlias13,
String fieldAlias14,
String fieldAlias15,
String fieldAlias16)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep17 |
with(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11,
String fieldAlias12,
String fieldAlias13,
String fieldAlias14,
String fieldAlias15,
String fieldAlias16,
String fieldAlias17)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep18 |
with(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11,
String fieldAlias12,
String fieldAlias13,
String fieldAlias14,
String fieldAlias15,
String fieldAlias16,
String fieldAlias17,
String fieldAlias18)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep19 |
with(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11,
String fieldAlias12,
String fieldAlias13,
String fieldAlias14,
String fieldAlias15,
String fieldAlias16,
String fieldAlias17,
String fieldAlias18,
String fieldAlias19)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep20 |
with(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11,
String fieldAlias12,
String fieldAlias13,
String fieldAlias14,
String fieldAlias15,
String fieldAlias16,
String fieldAlias17,
String fieldAlias18,
String fieldAlias19,
String fieldAlias20)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep21 |
with(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11,
String fieldAlias12,
String fieldAlias13,
String fieldAlias14,
String fieldAlias15,
String fieldAlias16,
String fieldAlias17,
String fieldAlias18,
String fieldAlias19,
String fieldAlias20,
String fieldAlias21)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep22 |
with(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11,
String fieldAlias12,
String fieldAlias13,
String fieldAlias14,
String fieldAlias15,
String fieldAlias16,
String fieldAlias17,
String fieldAlias18,
String fieldAlias19,
String fieldAlias20,
String fieldAlias21,
String fieldAlias22)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithStep |
withRecursive(CommonTableExpression<?>... tables)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep |
withRecursive(String alias)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep |
withRecursive(String alias,
java.util.function.BiFunction<? super Field<?>,? super Integer,? extends String> fieldNameFunction)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep |
withRecursive(String alias,
java.util.function.Function<? super Field<?>,? extends String> fieldNameFunction)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep |
withRecursive(String alias,
String... fieldAliases)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep1 |
withRecursive(String alias,
String fieldAlias1)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep2 |
withRecursive(String alias,
String fieldAlias1,
String fieldAlias2)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep3 |
withRecursive(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep4 |
withRecursive(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep5 |
withRecursive(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep6 |
withRecursive(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep7 |
withRecursive(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep8 |
withRecursive(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep9 |
withRecursive(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep10 |
withRecursive(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep11 |
withRecursive(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep12 |
withRecursive(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11,
String fieldAlias12)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep13 |
withRecursive(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11,
String fieldAlias12,
String fieldAlias13)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep14 |
withRecursive(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11,
String fieldAlias12,
String fieldAlias13,
String fieldAlias14)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep15 |
withRecursive(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11,
String fieldAlias12,
String fieldAlias13,
String fieldAlias14,
String fieldAlias15)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep16 |
withRecursive(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11,
String fieldAlias12,
String fieldAlias13,
String fieldAlias14,
String fieldAlias15,
String fieldAlias16)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep17 |
withRecursive(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11,
String fieldAlias12,
String fieldAlias13,
String fieldAlias14,
String fieldAlias15,
String fieldAlias16,
String fieldAlias17)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep18 |
withRecursive(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11,
String fieldAlias12,
String fieldAlias13,
String fieldAlias14,
String fieldAlias15,
String fieldAlias16,
String fieldAlias17,
String fieldAlias18)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep19 |
withRecursive(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11,
String fieldAlias12,
String fieldAlias13,
String fieldAlias14,
String fieldAlias15,
String fieldAlias16,
String fieldAlias17,
String fieldAlias18,
String fieldAlias19)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep20 |
withRecursive(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11,
String fieldAlias12,
String fieldAlias13,
String fieldAlias14,
String fieldAlias15,
String fieldAlias16,
String fieldAlias17,
String fieldAlias18,
String fieldAlias19,
String fieldAlias20)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep21 |
withRecursive(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11,
String fieldAlias12,
String fieldAlias13,
String fieldAlias14,
String fieldAlias15,
String fieldAlias16,
String fieldAlias17,
String fieldAlias18,
String fieldAlias19,
String fieldAlias20,
String fieldAlias21)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
WithAsStep22 |
withRecursive(String alias,
String fieldAlias1,
String fieldAlias2,
String fieldAlias3,
String fieldAlias4,
String fieldAlias5,
String fieldAlias6,
String fieldAlias7,
String fieldAlias8,
String fieldAlias9,
String fieldAlias10,
String fieldAlias11,
String fieldAlias12,
String fieldAlias13,
String fieldAlias14,
String fieldAlias15,
String fieldAlias16,
String fieldAlias17,
String fieldAlias18,
String fieldAlias19,
String fieldAlias20,
String fieldAlias21,
String fieldAlias22)
Create a
WITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions. |
public DefaultDSLContext(SQLDialect dialect)
public DefaultDSLContext(SQLDialect dialect, Settings settings)
public DefaultDSLContext(Connection connection, SQLDialect dialect)
public DefaultDSLContext(Connection connection, SQLDialect dialect, Settings settings)
public DefaultDSLContext(DataSource datasource, SQLDialect dialect)
public DefaultDSLContext(DataSource datasource, SQLDialect dialect, Settings settings)
public DefaultDSLContext(ConnectionProvider connectionProvider, SQLDialect dialect)
public DefaultDSLContext(ConnectionProvider connectionProvider, SQLDialect dialect, Settings settings)
public DefaultDSLContext(Configuration configuration)
public void close()
DSLContextDSLContext.
Some DSLContext constructors, such as DSL.using(String),
DSL.using(String, Properties), or
DSL.using(String, String, String) allocate a Connection
resource, which is inaccessible to the outside of the DSLContext
implementation. Proper resource management must thus be done via this
DSLContext.close() method.
close in interface AutoCloseableclose in interface DSLContextpublic Schema map(Schema schema)
DSLContext
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.
map in interface DSLContextschema - A schemapublic <R extends Record> Table<R> map(Table<R> table)
DSLContext
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.
map in interface DSLContexttable - A table@Deprecated public Parser parser()
DSLContextparser in interface DSLContextpublic Meta meta()
DSLContextThis method returns a wrapper type that gives access to your JDBC connection's database meta data.
meta in interface DSLContextpublic Meta meta(InformationSchema schema)
DSLContextmeta in interface DSLContextpublic InformationSchema informationSchema(Catalog catalog)
DSLContextInformationSchema format.
This allows for serialising schema meta information as XML using JAXB.
See also Constants.XSD_META for details.
informationSchema in interface DSLContextpublic InformationSchema informationSchema(Catalog... catalogs)
DSLContextInformationSchema format.
This allows for serialising schema meta information as XML using JAXB.
See also Constants.XSD_META for details.
informationSchema in interface DSLContextpublic InformationSchema informationSchema(Schema schema)
DSLContextInformationSchema format.
This allows for serialising schema meta information as XML using JAXB.
See also Constants.XSD_META for details.
informationSchema in interface DSLContextpublic InformationSchema informationSchema(Schema... schemas)
DSLContextInformationSchema format.
This allows for serialising schema meta information as XML using JAXB.
See also Constants.XSD_META for details.
informationSchema in interface DSLContextpublic InformationSchema informationSchema(Table<?> table)
DSLContextInformationSchema format.
Exporting a single table will not include any foreign key definitions in the exported data.
This allows for serialising schema meta information as XML using JAXB.
See also Constants.XSD_META for details.
informationSchema in interface DSLContextpublic InformationSchema informationSchema(Table<?>... tables)
DSLContextInformationSchema format.
Only those foreign keys whose referenced table is also included in the export will be exported.
This allows for serialising schema meta information as XML using JAXB.
See also Constants.XSD_META for details.
informationSchema in interface DSLContextpublic <T> T transactionResult(ContextTransactionalCallable<T> transactional)
DSLContextContextTransactionalRunnable in the context of this
DSLContext's underlying Scope.configuration()'s
Configuration.transactionProvider(), and return the
transactional's outcome.
The argument transactional code may capture scope to derive its
Configuration from the "context" in order to create new
statements. This context can be provided, for instance, by
ThreadLocalTransactionProvider automatically.
transactionResult in interface DSLContexttransactional - The transactional codepublic <T> T transactionResult(TransactionalCallable<T> transactional)
DSLContextTransactionalCallable in the context of this
DSLContext's underlying Scope.configuration()'s
Configuration.transactionProvider(), and return the
transactional's outcome.
The argument transactional code should not capture any scope but derive
its Configuration from the
TransactionalCallable.run(Configuration) argument in order to
create new statements.
transactionResult in interface DSLContexttransactional - The transactional codepublic void transaction(ContextTransactionalRunnable transactional)
DSLContextContextTransactionalRunnable in the context of this
DSLContext's underlying Scope.configuration()'s
Configuration.transactionProvider().
The argument transactional code may capture scope to derive its
Configuration from the "context" in order to create new
statements. This context can be provided, for instance, by
ThreadLocalTransactionProvider automatically.
transaction in interface DSLContexttransactional - The transactional codepublic void transaction(TransactionalRunnable transactional)
DSLContextTransactionalRunnable in the context of this
DSLContext's underlying Scope.configuration()'s
Configuration.transactionProvider().
The argument transactional code should not capture any scope but derive
its Configuration from the
TransactionalCallable.run(Configuration) argument in order to
create new statements.
transaction in interface DSLContexttransactional - The transactional codepublic CompletionStage<Void> transactionAsync(TransactionalRunnable transactional)
DSLContextTransactionalRunnable asynchronously.
The TransactionRunnable is run in the context of this
DSLContext's underlying Scope.configuration()'s
Configuration.transactionProvider(), and returns the
transactional's outcome in a new CompletionStage
that is asynchronously completed by a task run by an Executor
provided by the underlying Scope.configuration()'s
Configuration.executorProvider().
transactionAsync in interface DSLContexttransactional - The transactional codepublic CompletionStage<Void> transactionAsync(Executor executor, TransactionalRunnable transactional)
DSLContextTransactionalRunnable asynchronously.
The TransactionRunnable is run in the context of this
DSLContext's underlying Scope.configuration()'s
Configuration.transactionProvider(), and returns the
transactional's outcome in a new CompletionStage
that is asynchronously completed by a task run by a given
Executor.
transactionAsync in interface DSLContexttransactional - The transactional codepublic <T> CompletionStage<T> transactionResultAsync(TransactionalCallable<T> transactional)
DSLContextTransactionalCallable asynchronously.
The TransactionCallable is run in the context of this
DSLContext's underlying Scope.configuration()'s
Configuration.transactionProvider(), and returns the
transactional's outcome in a new CompletionStage
that is asynchronously completed by a task run by an Executor
provided by the underlying Scope.configuration()'s
Configuration.executorProvider().
transactionResultAsync in interface DSLContexttransactional - The transactional codepublic <T> CompletionStage<T> transactionResultAsync(Executor executor, TransactionalCallable<T> transactional)
DSLContextTransactionalCallable asynchronously.
The TransactionCallable is run in the context of this
DSLContext's underlying Scope.configuration()'s
Configuration.transactionProvider(), and returns the
transactional's outcome in a new CompletionStage
that is asynchronously completed by a task run by a given
Executor.
transactionResultAsync in interface DSLContexttransactional - The transactional codepublic <T> T connectionResult(ConnectionCallable<T> callable)
DSLContextConnectionCallable in the context of this
DSLContext's underlying Scope.configuration()'s
Configuration.connectionProvider().connectionResult in interface DSLContextpublic void connection(ConnectionRunnable runnable)
DSLContextConnectionRunnable in the context of this
DSLContext's underlying Scope.configuration()'s
Configuration.connectionProvider().connection in interface DSLContextrunnable - The code running statements against the
connection.public <T> T mockResult(MockDataProvider provider, MockCallable<T> mockable)
DSLContextMockRunnable in the context of this DSLContext
's underlying Scope.configuration()'s, and of a
MockDataProvider and return the mockable's outcome.mockResult in interface DSLContextpublic void mock(MockDataProvider provider, MockRunnable mockable)
DSLContextMockRunnable in the context of this DSLContext
's underlying Scope.configuration()'s, and of a
MockDataProvider.mock in interface DSLContextpublic RenderContext renderContext()
DSLContextRenderContext for the context of this DSLContext.
This will return an initialised render context as such:
RenderContext.castMode() == DEFAULT
Context.declareFields() == falseContext.declareTables() == falseRenderContext.format() == falseRenderContext.paramType() == ParamType.INDEXEDRenderContext.qualify() == trueContext.subquery() == falserenderContext in interface DSLContextpublic String render(QueryPart part)
DSLContextDSLContext.
This is the same as calling renderContext().render(part)
render in interface DSLContextpart - The QueryPart to be renderedpublic String renderNamedParams(QueryPart part)
DSLContextDSLContext, rendering bind
variables as named parameters.
This is the same as calling
renderContext().paramType(NAMED).render(part)
renderNamedParams in interface DSLContextpart - The QueryPart to be renderedpublic String renderNamedOrInlinedParams(QueryPart part)
DSLContextDSLContext, 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)
renderNamedOrInlinedParams in interface DSLContextpart - The QueryPart to be renderedpublic String renderInlined(QueryPart part)
DSLContextDSLContext, inlining all bind
variables.
This is the same as calling
renderContext().inline(true).render(part)
renderInlined in interface DSLContextpart - The QueryPart to be renderedpublic List<Object> extractBindValues(QueryPart part)
DSLContextQueryPart.
The returned List is immutable. To modify bind values, use
DSLContext.extractParams(QueryPart) instead.
Unlike DSLContext.extractParams(QueryPart), which returns also inlined
parameters, this returns only actual bind values that will render an
actual bind value as a question mark "?"
extractBindValues in interface DSLContextpublic Map<String,Param<?>> extractParams(QueryPart part)
DSLContextMap of named parameters.
The Map itself is immutable, but the Param elements
allow for modifying bind values on an existing Query (or any
other QueryPart).
Bind values created with DSL.val(Object) will have their bind
index as name.
extractParams in interface DSLContextParam,
DSL.param(String, Object)public Param<?> extractParam(QueryPart part, String name)
DSLContextQueryPart, provided its name.
Bind values created with DSL.val(Object) will have their bind
index as name.
extractParam in interface DSLContextParam,
DSL.param(String, Object)public BindContext bindContext(PreparedStatement stmt)
DSLContextBindContext for the context of this DSLContext.
This will return an initialised bind context as such:
Context.declareFields() == falseContext.declareTables() == falseBindContext for JOOQ INTERNAL USE only. Avoid referencing it directly
bindContext in interface DSLContext@Deprecated public int bind(QueryPart part, PreparedStatement stmt)
bind in interface DSLContextpublic void attach(Attachable... attachables)
DSLContextDSLContext's underlying Scope.configuration()
to some attachables.attach in interface DSLContextpublic void attach(Collection<? extends Attachable> attachables)
DSLContextDSLContext's underlying Scope.configuration()
to some attachables.attach in interface DSLContextpublic <R extends Record> LoaderOptionsStep<R> loadInto(Table<R> table)
DSLContextLoader object to load data from a CSV or XML
source.loadInto in interface DSLContextpublic Query query(SQL sql)
DSLContextExample:
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!
query in interface DSLContextsql - The SQLSQLpublic Query query(String sql)
DSLContextExample:
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!
query in interface DSLContextsql - The SQLSQLpublic Query query(String sql, Object... bindings)
DSLContextExample:
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!
query in interface DSLContextsql - The SQLbindings - The bindingsSQL,
DSL.sql(String, Object...)public Query query(String sql, QueryPart... parts)
DSLContext
Unlike DSLContext.query(String, Object...), the SQL passed to this method
should not contain any bind variables. Instead, you can pass
QueryPart objects to the method which will be rendered at indexed
locations of your SQL string as such:
// The following query
query("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));
// Will render this SQL on an Oracle database with RenderNameStyle.QUOTED:
select ?, 'test' from "DUAL"
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses! One way to escape
literals is to use DSL.name(String...) and similar methods
query in interface DSLContextsql - The SQL clause, containing {numbered placeholders} where query
parts can be injectedparts - The QueryPart objects that are rendered at the
{numbered placeholder} locationsSQL,
DSL.sql(String, QueryPart...)public Result<Record> fetch(SQL sql)
DSLContextExample (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetch in interface DSLContextsql - The SQLnull.SQLpublic Result<Record> fetch(String sql)
DSLContextExample (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetch in interface DSLContextsql - The SQLnull.SQLpublic Result<Record> fetch(String sql, Object... bindings)
DSLContextThere 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 \"
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!
fetch in interface DSLContextsql - The SQLbindings - The bindingsnull.SQL,
DSL.sql(String, Object...)public Result<Record> fetch(String sql, QueryPart... parts)
DSLContext
Unlike DSLContext.fetch(String, Object...), the SQL passed to this method
should not contain any bind variables. Instead, you can pass
QueryPart objects to the method which will be rendered at indexed
locations of your SQL string as such:
// The following query
fetch("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));
// Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
select ?, 'test' from "DUAL"
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses! One way to escape
literals is to use DSL.name(String...) and similar methods
fetch in interface DSLContextsql - The SQL clause, containing {numbered placeholders} where query
parts can be injectedparts - The QueryPart objects that are rendered at the
{numbered placeholder} locationsnull.SQL,
DSL.sql(String, QueryPart...)public Cursor<Record> fetchLazy(SQL sql)
DSLContext
The returned Cursor holds a reference to the executed
PreparedStatement and the associated ResultSet. Data can
be fetched (or iterated over) lazily, fetching records from the
ResultSet one by one.
Example (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetchLazy in interface DSLContextsql - The SQLnull.SQLpublic Cursor<Record> fetchLazy(String sql)
DSLContext
The returned Cursor holds a reference to the executed
PreparedStatement and the associated ResultSet. Data can
be fetched (or iterated over) lazily, fetching records from the
ResultSet one by one.
Example (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetchLazy in interface DSLContextsql - The SQLnull.SQLpublic Cursor<Record> fetchLazy(String sql, Object... bindings)
DSLContextThere must be as many bind variables contained in the SQL, as passed in the bindings parameter
The returned Cursor holds a reference to the executed
PreparedStatement and the associated ResultSet. Data can
be fetched (or iterated over) lazily, fetching records from the
ResultSet one by one.
Example (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetchLazy in interface DSLContextsql - The SQLbindings - The bindingsnull.SQL,
DSL.sql(String, Object...)public Cursor<Record> fetchLazy(String sql, QueryPart... parts)
DSLContext
The returned Cursor holds a reference to the executed
PreparedStatement and the associated ResultSet. Data can
be fetched (or iterated over) lazily, fetching records from the
ResultSet one by one.
Unlike DSLContext.fetchLazy(String, Object...), the SQL passed to this
method should not contain any bind variables. Instead, you can pass
QueryPart objects to the method which will be rendered at indexed
locations of your SQL string as such:
// The following query
fetchLazy("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));
// Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
select ?, 'test' from "DUAL"
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses! One way to escape
literals is to use DSL.name(String...) and similar methods
fetchLazy in interface DSLContextsql - The SQL clause, containing {numbered placeholders} where query
parts can be injectedparts - The QueryPart objects that are rendered at the
{numbered placeholder} locationsnull.SQL,
DSL.sql(String, QueryPart...)public CompletionStage<Result<Record>> fetchAsync(SQL sql)
DSLContextCompletionStage.
The result is asynchronously completed by a task running in an
Executor provided by the Scope.configuration()'s
Configuration.executorProvider().
Example (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetchAsync in interface DSLContextsql - The SQLnull.SQLpublic CompletionStage<Result<Record>> fetchAsync(String sql)
DSLContextCompletionStage.
The result is asynchronously completed by a task running in an
Executor provided by the Scope.configuration()'s
Configuration.executorProvider().
Example (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetchAsync in interface DSLContextsql - The SQLnull.SQLpublic CompletionStage<Result<Record>> fetchAsync(String sql, Object... bindings)
DSLContextCompletionStage.
The result is asynchronously completed by a task running in an
Executor provided by the Scope.configuration()'s
Configuration.executorProvider().
There must be as many bind variables contained in the SQL, as passed in the bindings parameter
Example (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetchAsync in interface DSLContextsql - The SQLbindings - The bindingsnull.SQL,
DSL.sql(String, Object...)public CompletionStage<Result<Record>> fetchAsync(String sql, QueryPart... parts)
DSLContextCompletionStage.
The result is asynchronously completed by a task running in an
Executor provided by the Scope.configuration()'s
Configuration.executorProvider().
Unlike DSLContext.fetchLazy(String, Object...), the SQL passed to this
method should not contain any bind variables. Instead, you can pass
QueryPart objects to the method which will be rendered at indexed
locations of your SQL string as such:
// The following query
fetchLazy("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));
// Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
select ?, 'test' from "DUAL"
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses! One way to escape
literals is to use DSL.name(String...) and similar methods
fetchAsync in interface DSLContextsql - The SQL clause, containing {numbered placeholders} where query
parts can be injectedparts - The QueryPart objects that are rendered at the
{numbered placeholder} locationsnull.SQL,
DSL.sql(String, QueryPart...)public CompletionStage<Result<Record>> fetchAsync(Executor executor, SQL sql)
DSLContextCompletionStage that is asynchronously
completed by a task running in the given executor.
Example (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetchAsync in interface DSLContextsql - The SQLnull.SQLpublic CompletionStage<Result<Record>> fetchAsync(Executor executor, String sql)
DSLContextCompletionStage that is asynchronously
completed by a task running in the given executor.
Example (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetchAsync in interface DSLContextsql - The SQLnull.SQLpublic CompletionStage<Result<Record>> fetchAsync(Executor executor, String sql, Object... bindings)
DSLContextCompletionStage 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 \"
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!
fetchAsync in interface DSLContextsql - The SQLbindings - The bindingsnull.SQL,
DSL.sql(String, Object...)public CompletionStage<Result<Record>> fetchAsync(Executor executor, String sql, QueryPart... parts)
DSLContextCompletionStage that is asynchronously
completed by a task running in the given executor.
Unlike DSLContext.fetchLazy(String, Object...), the SQL passed to this
method should not contain any bind variables. Instead, you can pass
QueryPart objects to the method which will be rendered at indexed
locations of your SQL string as such:
// The following query
fetchLazy("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));
// Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
select ?, 'test' from "DUAL"
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses! One way to escape
literals is to use DSL.name(String...) and similar methods
fetchAsync in interface DSLContextsql - The SQL clause, containing {numbered placeholders} where query
parts can be injectedparts - The QueryPart objects that are rendered at the
{numbered placeholder} locationsnull.SQL,
DSL.sql(String, QueryPart...)public java.util.stream.Stream<Record> fetchStream(SQL sql)
DSLContext
The returned Stream holds a reference to the executed
PreparedStatement and the associated ResultSet. Data can
be fetched (or iterated over) lazily, fetching records from the
ResultSet one by one.
Example (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetchStream in interface DSLContextsql - The SQLnull, even if the database returns no
ResultSetSQLpublic java.util.stream.Stream<Record> fetchStream(String sql)
DSLContext
The returned Stream holds a reference to the executed
PreparedStatement and the associated ResultSet. Data can
be fetched (or iterated over) lazily, fetching records from the
ResultSet one by one.
Example (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetchStream in interface DSLContextsql - The SQLnull, even if the database returns no
ResultSetSQLpublic java.util.stream.Stream<Record> fetchStream(String sql, Object... bindings)
DSLContextThere must be as many bind variables contained in the SQL, as passed in the bindings parameter
The returned Stream holds a reference to the executed
PreparedStatement and the associated ResultSet. Data can
be fetched (or iterated over) lazily, fetching records from the
ResultSet one by one.
Example (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetchStream in interface DSLContextsql - The SQLbindings - The bindingsnull, even if the database returns no
ResultSetSQL,
DSL.sql(String, Object...)public java.util.stream.Stream<Record> fetchStream(String sql, QueryPart... parts)
DSLContext
The returned Stream holds a reference to the executed
PreparedStatement and the associated ResultSet. Data can
be fetched (or iterated over) lazily, fetching records from the
ResultSet one by one.
Unlike DSLContext.fetchStream(String, Object...), the SQL passed to this
method should not contain any bind variables. Instead, you can pass
QueryPart objects to the method which will be rendered at indexed
locations of your SQL string as such:
// The following query
fetchLazy("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));
// Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
select ?, 'test' from "DUAL"
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses! One way to escape
literals is to use DSL.name(String...) and similar methods
fetchStream in interface DSLContextsql - The SQL clause, containing {numbered placeholders} where query
parts can be injectedparts - The QueryPart objects that are rendered at the
{numbered placeholder} locationsnull, even if the database returns no
ResultSetSQL,
DSL.sql(String, QueryPart...)public Results fetchMany(SQL sql)
DSLContextExample (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!
fetchMany in interface DSLContextsql - The SQLnull.SQLpublic Results fetchMany(String sql)
DSLContextExample (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!
fetchMany in interface DSLContextsql - The SQLnull.SQLpublic Results fetchMany(String sql, Object... bindings)
DSLContextThere 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!
fetchMany in interface DSLContextsql - The SQLbindings - The bindingsnull.SQL,
DSL.sql(String, Object...)public Results fetchMany(String sql, QueryPart... parts)
DSLContext
Unlike DSLContext.fetchMany(String, Object...), the SQL passed to this
method should not contain any bind variables. Instead, you can pass
QueryPart objects to the method which will be rendered at indexed
locations of your SQL string as such:
// The following query
fetchMany("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));
// Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
select ?, 'test' from "DUAL"
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses! One way to escape
literals is to use DSL.name(String...) and similar methods
fetchMany in interface DSLContextsql - The SQL clause, containing {numbered placeholders} where query
parts can be injectedparts - The QueryPart objects that are rendered at the
{numbered placeholder} locationsnull.SQL,
DSL.sql(String, QueryPart...)public Record fetchOne(SQL sql)
DSLContextExample (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetchOne in interface DSLContextsql - The SQLnull, if no record was found.SQLpublic Record fetchOne(String sql)
DSLContextExample (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetchOne in interface DSLContextsql - The SQLnull, if no record was found.SQLpublic Record fetchOne(String sql, Object... bindings)
DSLContextThere 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 \"
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!
fetchOne in interface DSLContextsql - The SQLbindings - The bindingsnull, if no record was found.SQL,
DSL.sql(String, Object...)public Record fetchOne(String sql, QueryPart... parts)
DSLContext
Unlike DSLContext.fetchOne(String, Object...), the SQL passed to this
method should not contain any bind variables. Instead, you can pass
QueryPart objects to the method which will be rendered at indexed
locations of your SQL string as such:
// The following query
fetchOne("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));
// Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
select ?, 'test' from "DUAL"
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses! One way to escape
literals is to use DSL.name(String...) and similar methods
fetchOne in interface DSLContextsql - The SQL clause, containing {numbered placeholders} where query
parts can be injectedparts - The QueryPart objects that are rendered at the
{numbered placeholder} locationsnull, if no record was found.SQL,
DSL.sql(String, QueryPart...)public Optional<Record> fetchOptional(SQL sql)
DSLContextExample (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetchOptional in interface DSLContextsql - The SQLSQLpublic Optional<Record> fetchOptional(String sql)
DSLContextExample (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetchOptional in interface DSLContextsql - The SQLSQLpublic Optional<Record> fetchOptional(String sql, Object... bindings)
DSLContextThere 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 \"
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!
fetchOptional in interface DSLContextsql - The SQLbindings - The bindingsSQL,
DSL.sql(String, Object...)public Optional<Record> fetchOptional(String sql, QueryPart... parts)
DSLContext
Unlike DSLContext.fetchOne(String, Object...), the SQL passed to this
method should not contain any bind variables. Instead, you can pass
QueryPart objects to the method which will be rendered at indexed
locations of your SQL string as such:
// The following query
fetchOne("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));
// Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
select ?, 'test' from "DUAL"
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses! One way to escape
literals is to use DSL.name(String...) and similar methods
fetchOptional in interface DSLContextsql - The SQL clause, containing {numbered placeholders} where query
parts can be injectedparts - The QueryPart objects that are rendered at the
{numbered placeholder} locationsSQL,
DSL.sql(String, QueryPart...)public Object fetchValue(SQL sql)
DSLContextExample (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetchValue in interface DSLContextsql - The SQLnull, if no record was found.SQLpublic Object fetchValue(String sql)
DSLContextExample (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetchValue in interface DSLContextsql - The SQLnull, if no record was found.SQLpublic Object fetchValue(String sql, Object... bindings)
DSLContextThere 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 \"
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!
fetchValue in interface DSLContextsql - The SQLbindings - The bindingsnull, if no record was found.SQL,
DSL.sql(String, Object...)public Object fetchValue(String sql, QueryPart... parts)
DSLContext
Unlike DSLContext.fetchValue(String, Object...), the SQL passed to this
method should not contain any bind variables. Instead, you can pass
QueryPart objects to the method which will be rendered at indexed
locations of your SQL string as such:
// The following query
fetchOne("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));
// Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
select ?, 'test' from "DUAL"
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses! One way to escape
literals is to use DSL.name(String...) and similar methods
fetchValue in interface DSLContextsql - The SQL clause, containing {numbered placeholders} where query
parts can be injectedparts - The QueryPart objects that are rendered at the
{numbered placeholder} locationsnull, if no record was found.SQL,
DSL.sql(String, QueryPart...)public Optional<?> fetchOptionalValue(SQL sql)
DSLContextExample (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetchOptionalValue in interface DSLContextsql - The SQLSQLpublic Optional<?> fetchOptionalValue(String sql)
DSLContextExample (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetchOptionalValue in interface DSLContextsql - The SQLSQLpublic Optional<?> fetchOptionalValue(String sql, Object... bindings)
DSLContextThere 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 \"
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!
fetchOptionalValue in interface DSLContextsql - The SQLbindings - The bindingsSQL,
DSL.sql(String, Object...)public Optional<?> fetchOptionalValue(String sql, QueryPart... parts)
DSLContext
Unlike DSLContext.fetchValue(String, Object...), the SQL passed to this
method should not contain any bind variables. Instead, you can pass
QueryPart objects to the method which will be rendered at indexed
locations of your SQL string as such:
// The following query
fetchOne("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));
// Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
select ?, 'test' from "DUAL"
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses! One way to escape
literals is to use DSL.name(String...) and similar methods
fetchOptionalValue in interface DSLContextsql - The SQL clause, containing {numbered placeholders} where query
parts can be injectedparts - The QueryPart objects that are rendered at the
{numbered placeholder} locationsSQL,
DSL.sql(String, QueryPart...)public List<?> fetchValues(SQL sql)
DSLContextExample (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetchValues in interface DSLContextsql - The SQLnull.SQLpublic List<?> fetchValues(String sql)
DSLContextExample (Postgres):
Example
(SQLite):
String sql = "FETCH ALL IN \"
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!
fetchValues in interface DSLContextsql - The SQLnull.SQLpublic List<?> fetchValues(String sql, Object... bindings)
DSLContextThere 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 \"
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!
fetchValues in interface DSLContextsql - The SQLbindings - The bindingsnull.SQL,
DSL.sql(String, Object...)public List<?> fetchValues(String sql, QueryPart... parts)
DSLContext
Unlike DSLContext.fetchValue(String, Object...), the SQL passed to this
method should not contain any bind variables. Instead, you can pass
QueryPart objects to the method which will be rendered at indexed
locations of your SQL string as such:
// The following query
fetchOne("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));
// Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
select ?, 'test' from "DUAL"
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses! One way to escape
literals is to use DSL.name(String...) and similar methods
fetchValues in interface DSLContextsql - The SQL clause, containing {numbered placeholders} where query
parts can be injectedparts - The QueryPart objects that are rendered at the
{numbered placeholder} locationsnull.SQL,
DSL.sql(String, QueryPart...)public int execute(SQL sql)
DSLContextNOTE: 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!
execute in interface DSLContextsql - The SQLSQLpublic int execute(String sql)
DSLContextNOTE: 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!
execute in interface DSLContextsql - The SQLSQLpublic int execute(String sql, Object... bindings)
DSLContextThere 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!
execute in interface DSLContextsql - The SQLbindings - The bindingsSQL,
DSL.sql(String, Object...)public int execute(String sql, QueryPart... parts)
DSLContext
Unlike DSLContext.execute(String, Object...), the SQL passed to this method
should not contain any bind variables. Instead, you can pass
QueryPart objects to the method which will be rendered at indexed
locations of your SQL string as such:
// The following query
execute("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));
// Will execute this SQL on an Oracle database with RenderNameStyle.QUOTED:
select ?, 'test' from "DUAL"
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses! One way to escape
literals is to use DSL.name(String...) and similar methods
execute in interface DSLContextsql - The SQL clause, containing {numbered placeholders} where query
parts can be injectedparts - The QueryPart objects that are rendered at the
{numbered placeholder} locationsSQL,
DSL.sql(String, QueryPart...)public ResultQuery<Record> resultQuery(SQL sql)
DSLContextThere must not be any binding 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 \"
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!
resultQuery in interface DSLContextsql - The SQLSQLpublic ResultQuery<Record> resultQuery(String sql)
DSLContextThere must not be any binding 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 \"
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!
resultQuery in interface DSLContextsql - The SQLSQLpublic ResultQuery<Record> resultQuery(String sql, Object... bindings)
DSLContextThere 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 \"
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!
resultQuery in interface DSLContextsql - The SQLbindings - The bindingsSQL,
DSL.sql(String, Object...)public ResultQuery<Record> resultQuery(String sql, QueryPart... parts)
DSLContext
Unlike DSLContext.resultQuery(String, Object...), the SQL passed to this
method should not contain any bind variables. Instead, you can pass
QueryPart objects to the method which will be rendered at indexed
locations of your SQL string as such:
// The following query
resultQuery("select {0}, {1} from {2}", val(1), inline("test"), name("DUAL"));
// Will render this SQL on an Oracle database with RenderNameStyle.QUOTED:
select ?, 'test' from "DUAL"
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. You may also create the possibility of
malicious SQL injection. Be sure to properly use bind variables and/or
escape literals when concatenated into SQL clauses! One way to escape
literals is to use DSL.name(String...) and similar methods
resultQuery in interface DSLContextsql - The SQL clause, containing {numbered placeholders} where query
parts can be injectedparts - The QueryPart objects that are rendered at the
{numbered placeholder} locationsSQL,
DSL.sql(String, QueryPart...)public Result<Record> fetch(ResultSet rs)
DSLContextResultSet and transform it to a jOOQ
Result.
After fetching all data, the JDBC ResultSet will be closed.
Use DSLContext.fetchLazy(ResultSet), to fetch one Record at a
time, instead of load the entire ResultSet into a jOOQ
Result at once.
fetch in interface DSLContextrs - The JDBC ResultSet to fetch data fromnull.public Result<Record> fetch(ResultSet rs, Field<?>... fields)
DSLContextResultSet and transform it to a jOOQ
Result.
After fetching all data, the JDBC ResultSet will be closed.
Use DSLContext.fetchLazy(ResultSet), to fetch one Record at a
time, instead of load the entire ResultSet into a jOOQ
Result at once.
The additional fields argument is used by jOOQ to coerce
field names and data types to the desired output
fetch in interface DSLContextrs - The JDBC ResultSet to fetch data fromfields - The fields to use in the desired outputnull.public Result<Record> fetch(ResultSet rs, DataType<?>... types)
DSLContextResultSet and transform it to a jOOQ
Result.
After fetching all data, the JDBC ResultSet will be closed.
Use DSLContext.fetchLazy(ResultSet), to fetch one Record at a
time, instead of load the entire ResultSet into a jOOQ
Result at once.
The additional types argument is used by jOOQ to coerce data
types to the desired output
fetch in interface DSLContextrs - The JDBC ResultSet to fetch data fromtypes - The data types to use in the desired outputnull.public Result<Record> fetch(ResultSet rs, Class<?>... types)
DSLContextResultSet and transform it to a jOOQ
Result.
After fetching all data, the JDBC ResultSet will be closed.
Use DSLContext.fetchLazy(ResultSet), to fetch one Record at a
time, instead of load the entire ResultSet into a jOOQ
Result at once.
The additional types argument is used by jOOQ to coerce data
types to the desired output
fetch in interface DSLContextrs - The JDBC ResultSet to fetch data fromtypes - The data types to use in the desired outputnull.public Record fetchOne(ResultSet rs)
DSLContextResultSet and transform it to a jOOQ
Record.
This will internally fetch all records and throw an exception if there was more than one resulting record.
fetchOne in interface DSLContextrs - The JDBC ResultSet to fetch data fromnull, if no record was found.public Record fetchOne(ResultSet rs, Field<?>... fields)
DSLContextResultSet and transform it to a jOOQ
Record.
This will internally fetch all records and throw an exception if there was more than one resulting record.
The additional fields argument is used by jOOQ to coerce
field names and data types to the desired output
fetchOne in interface DSLContextrs - The JDBC ResultSet to fetch data fromfields - The fields to use in the desired outputnull, if no record was found.public Record fetchOne(ResultSet rs, DataType<?>... types)
DSLContextResultSet and transform it to a jOOQ
Record.
This will internally fetch all records and throw an exception if there was more than one resulting record.
The additional types argument is used by jOOQ to coerce data
types to the desired output
fetchOne in interface DSLContextrs - The JDBC ResultSet to fetch data fromtypes - The data types to use in the desired outputnull, if no record was found.public Record fetchOne(ResultSet rs, Class<?>... types)
DSLContextResultSet and transform it to a jOOQ
Record.
This will internally fetch all records and throw an exception if there was more than one resulting record.
The additional types argument is used by jOOQ to coerce data
types to the desired output
fetchOne in interface DSLContextrs - The JDBC ResultSet to fetch data fromtypes - The data types to use in the desired outputnull, if no record was found.public Optional<Record> fetchOptional(ResultSet rs)
DSLContextResultSet and transform it to a jOOQ
Record.
This will internally fetch all records and throw an exception if there was more than one resulting record.
fetchOptional in interface DSLContextrs - The JDBC ResultSet to fetch data frompublic Optional<Record> fetchOptional(ResultSet rs, Field<?>... fields)
DSLContextResultSet and transform it to a jOOQ
Record.
This will internally fetch all records and throw an exception if there was more than one resulting record.
The additional fields argument is used by jOOQ to coerce
field names and data types to the desired output
fetchOptional in interface DSLContextrs - The JDBC ResultSet to fetch data fromfields - The fields to use in the desired outputpublic Optional<Record> fetchOptional(ResultSet rs, DataType<?>... types)
DSLContextResultSet and transform it to a jOOQ
Record.
This will internally fetch all records and throw an exception if there was more than one resulting record.
The additional types argument is used by jOOQ to coerce data
types to the desired output
fetchOptional in interface DSLContextrs - The JDBC ResultSet to fetch data fromtypes - The data types to use in the desired outputpublic Optional<Record> fetchOptional(ResultSet rs, Class<?>... types)
DSLContextResultSet and transform it to a jOOQ
Record.
This will internally fetch all records and throw an exception if there was more than one resulting record.
The additional types argument is used by jOOQ to coerce data
types to the desired output
fetchOptional in interface DSLContextrs - The JDBC ResultSet to fetch data fromtypes - The data types to use in the desired outputpublic Object fetchValue(ResultSet rs)
DSLContextResultSet and return the only
contained value.
This will internally fetch all records and throw an exception if there was more than one resulting record.
fetchValue in interface DSLContextrs - The JDBC ResultSet to fetch data fromnull, if no record was found.public <T> T fetchValue(ResultSet rs, Field<T> field)
DSLContextResultSet 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
fetchValue in interface DSLContextrs - The JDBC ResultSet to fetch data fromfield - The field to use in the desired outputnull, if no record was found.public <T> T fetchValue(ResultSet rs, DataType<T> type)
DSLContextResultSet 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
fetchValue in interface DSLContextrs - The JDBC ResultSet to fetch data fromtype - The data type to use in the desired outputnull, if no record was found.public <T> T fetchValue(ResultSet rs, Class<T> type)
DSLContextResultSet 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
fetchValue in interface DSLContextrs - The JDBC ResultSet to fetch data fromtype - The data types to use in the desired outputnull, if no record was found.public Optional<?> fetchOptionalValue(ResultSet rs)
DSLContextResultSet and return the only
contained value.
This will internally fetch all records and throw an exception if there was more than one resulting record.
fetchOptionalValue in interface DSLContextrs - The JDBC ResultSet to fetch data frompublic <T> Optional<T> fetchOptionalValue(ResultSet rs, Field<T> field)
DSLContextResultSet 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
fetchOptionalValue in interface DSLContextrs - The JDBC ResultSet to fetch data fromfield - The field to use in the desired outputpublic <T> Optional<T> fetchOptionalValue(ResultSet rs, DataType<T> type)
DSLContextResultSet 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
fetchOptionalValue in interface DSLContextrs - The JDBC ResultSet to fetch data fromtype - The data type to use in the desired outputpublic <T> Optional<T> fetchOptionalValue(ResultSet rs, Class<T> type)
DSLContextResultSet 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
fetchOptionalValue in interface DSLContextrs - The JDBC ResultSet to fetch data fromtype - The data types to use in the desired outputpublic List<?> fetchValues(ResultSet rs)
DSLContextResultSet and return the only
contained column's values.fetchValues in interface DSLContextrs - The JDBC ResultSet to fetch data fromnull.public <T> List<T> fetchValues(ResultSet rs, Field<T> field)
DSLContextResultSet 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
fetchValues in interface DSLContextrs - The JDBC ResultSet to fetch data fromfield - The field to use in the desired outputnull.public <T> List<T> fetchValues(ResultSet rs, DataType<T> type)
DSLContextResultSet and return the only
contained column's values.
The additional type argument is used by jOOQ to coerce data
types to the desired output
fetchValues in interface DSLContextrs - The JDBC ResultSet to fetch data fromtype - The data type to use in the desired outputnull.public <T> List<T> fetchValues(ResultSet rs, Class<T> type)
DSLContextResultSet and return the only
contained column's values.
The additional type argument is used by jOOQ to coerce data
types to the desired output
fetchValues in interface DSLContextrs - The JDBC ResultSet to fetch data fromtype - The data types to use in the desired outputnull.public Cursor<Record> fetchLazy(ResultSet rs)
DSLContextResultSet into a jOOQ Cursor.
Use DSLContext.fetch(ResultSet), to load the entire ResultSet
into a jOOQ Result at once.
fetchLazy in interface DSLContextrs - The JDBC ResultSet to fetch data fromnull.public Cursor<Record> fetchLazy(ResultSet rs, Field<?>... fields)
DSLContextResultSet into a jOOQ Cursor.
Use DSLContext.fetch(ResultSet), to load the entire ResultSet
into a jOOQ Result at once.
The additional fields argument is used by jOOQ to coerce
field names and data types to the desired output
fetchLazy in interface DSLContextrs - The JDBC ResultSet to fetch data fromfields - The fields to use in the desired outputnull.public Cursor<Record> fetchLazy(ResultSet rs, DataType<?>... types)
DSLContextResultSet into a jOOQ Cursor.
Use DSLContext.fetch(ResultSet), to load the entire ResultSet
into a jOOQ Result at once.
The additional types argument is used by jOOQ to coerce data
types to the desired output
fetchLazy in interface DSLContextrs - The JDBC ResultSet to fetch data fromtypes - The data types to use in the desired outputnull.public Cursor<Record> fetchLazy(ResultSet rs, Class<?>... types)
DSLContextResultSet into a jOOQ Cursor.
Use DSLContext.fetch(ResultSet), to load the entire ResultSet
into a jOOQ Result at once.
The additional types argument is used by jOOQ to coerce data
types to the desired output
fetchLazy in interface DSLContextrs - The JDBC ResultSet to fetch data fromtypes - The data types to use in the desired outputnull.public CompletionStage<Result<Record>> fetchAsync(ResultSet rs)
DSLContextCompletionStage.
The result is asynchronously completed by a task running in an
Executor provided by the Scope.configuration()'s
Configuration.executorProvider().
fetchAsync in interface DSLContextrs - The JDBC ResultSet to fetch data fromnull.public CompletionStage<Result<Record>> fetchAsync(ResultSet rs, Field<?>... fields)
DSLContextCompletionStage.
The result is asynchronously completed by a task running in an
Executor provided by the Scope.configuration()'s
Configuration.executorProvider().
The additional fields argument is used by jOOQ to coerce
field names and data types to the desired output
fetchAsync in interface DSLContextrs - The JDBC ResultSet to fetch data fromfields - The fields to use in the desired outputnull.public CompletionStage<Result<Record>> fetchAsync(ResultSet rs, DataType<?>... types)
DSLContextCompletionStage.
The result is asynchronously completed by a task running in an
Executor provided by the Scope.configuration()'s
Configuration.executorProvider().
The additional types argument is used by jOOQ to coerce data
types to the desired output
fetchAsync in interface DSLContextrs - The JDBC ResultSet to fetch data fromtypes - The data types to use in the desired outputnull.public CompletionStage<Result<Record>> fetchAsync(ResultSet rs, Class<?>... types)
DSLContextCompletionStage.
The result is asynchronously completed by a task running in an
Executor provided by the Scope.configuration()'s
Configuration.executorProvider().
The additional types argument is used by jOOQ to coerce data
types to the desired output
fetchAsync in interface DSLContextrs - The JDBC ResultSet to fetch data fromtypes - The data types to use in the desired outputnull.public CompletionStage<Result<Record>> fetchAsync(Executor executor, ResultSet rs)
DSLContextCompletionStage that is asynchronously
completed by a task running in the given executor.fetchAsync in interface DSLContextrs - The JDBC ResultSet to fetch data fromnull.public CompletionStage<Result<Record>> fetchAsync(Executor executor, ResultSet rs, Field<?>... fields)
DSLContextCompletionStage 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
fetchAsync in interface DSLContextrs - The JDBC ResultSet to fetch data fromfields - The fields to use in the desired outputnull.public CompletionStage<Result<Record>> fetchAsync(Executor executor, ResultSet rs, DataType<?>... types)
DSLContextCompletionStage 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
fetchAsync in interface DSLContextrs - The JDBC ResultSet to fetch data fromtypes - The data types to use in the desired outputnull.public CompletionStage<Result<Record>> fetchAsync(Executor executor, ResultSet rs, Class<?>... types)
DSLContextCompletionStage 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
fetchAsync in interface DSLContextrs - The JDBC ResultSet to fetch data fromtypes - The data types to use in the desired outputnull.public java.util.stream.Stream<Record> fetchStream(ResultSet rs)
DSLContextResultSet into a jOOQ Stream.
Use DSLContext.fetch(ResultSet), to load the entire ResultSet
into a jOOQ Result at once.
fetchStream in interface DSLContextrs - The JDBC ResultSet to fetch data frompublic java.util.stream.Stream<Record> fetchStream(ResultSet rs, Field<?>... fields)
DSLContextResultSet into a jOOQ Stream.
Use DSLContext.fetch(ResultSet), to load the entire ResultSet
into a jOOQ Result at once.
The additional fields argument is used by jOOQ to coerce
field names and data types to the desired output
fetchStream in interface DSLContextrs - The JDBC ResultSet to fetch data fromfields - The fields to use in the desired outputpublic java.util.stream.Stream<Record> fetchStream(ResultSet rs, DataType<?>... types)
DSLContextResultSet into a jOOQ Stream.
Use DSLContext.fetch(ResultSet), to load the entire ResultSet
into a jOOQ Result at once.
The additional types argument is used by jOOQ to coerce data
types to the desired output
fetchStream in interface DSLContextrs - The JDBC ResultSet to fetch data fromtypes - The data types to use in the desired outputpublic java.util.stream.Stream<Record> fetchStream(ResultSet rs, Class<?>... types)
DSLContextResultSet into a jOOQ Stream.
Use DSLContext.fetch(ResultSet), to load the entire ResultSet
into a jOOQ Result at once.
The additional types argument is used by jOOQ to coerce data
types to the desired output
fetchStream in interface DSLContextrs - The JDBC ResultSet to fetch data fromtypes - The data types to use in the desired outputpublic Result<Record> fetchFromTXT(String string)
DSLContext
The supplied string is supposed to be formatted in a human-readable way.
This is the same as calling fetchFromTXT(string, "{null}")
fetchFromTXT in interface DSLContextstring - The formatted stringnull.DSLContext.fetchFromTXT(String, String)public Result<Record> fetchFromTXT(String string, String nullLiteral)
DSLContextThis method supports parsing results from two types of human-readable formats:
Result.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 |
+-----+-----+--------------------------+
VARCHAR(N) where
N = number of dashes per dash group
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
VARCHAR(N) where
N = number of dashes per dash groupBoth parsing methods make no assumption about the resulting data types. Instead, all data is string-based.
fetchFromTXT in interface DSLContextstring - The formatted stringnullLiteral - The string literal to be used as null
value.null.public Result<Record> fetchFromHTML(String string)
DSLContextResult.
This is the inverse operation of Result.formatHTML(). It works
according to the following parsing rules:
<caption>,
<thead>, <tbody> are simply ignored.<table> element is optional, but it
may appear only once<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.<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.
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>
fetchFromHTML in interface DSLContextstring - The HTML-formatted string.null.public Result<Record> fetchFromCSV(String string)
DSLContext
This is the same as calling fetchFromCSV(string, ',') and
the inverse of calling Result.formatCSV(). The first row of the
CSV data is required to hold field name information. Subsequent rows may
contain data, which is interpreted as String. Use the various
conversion methods to retrieve other data types from the
Result:
Result.getValues(Field, Class)Result.getValues(int, Class)Result.getValues(String, Class)Result.getValues(Field, Converter)Result.getValues(int, Converter)Result.getValues(String, Converter)
Missing values result in null. Empty values result in empty
Strings
fetchFromCSV in interface DSLContextstring - The CSV stringnull.DSLContext.fetchFromCSV(String, char)public Result<Record> fetchFromCSV(String string, char delimiter)
DSLContext
This is inverse of calling Result.formatCSV(char). The first row
of the CSV data is required to hold field name information. Subsequent
rows may contain data, which is interpreted as String. Use the
various conversion methods to retrieve other data types from the
Result:
Result.getValues(Field, Class)Result.getValues(int, Class)Result.getValues(String, Class)Result.getValues(Field, Converter)Result.getValues(int, Converter)Result.getValues(String, Converter)
Missing values result in null. Empty values result in empty
Strings
fetchFromCSV in interface DSLContextstring - The CSV stringdelimiter - The delimiter to expect between recordsnull.DSLContext.fetchFromCSV(String),
DSLContext.fetchFromStringData(List)public Result<Record> fetchFromCSV(String string, boolean header)
DSLContext
This is the same as calling fetchFromCSV(string, ',') and
the inverse of calling Result.formatCSV(boolean). Rows may
contain data, which is interpreted as String. Use the various
conversion methods to retrieve other data types from the
Result:
Result.getValues(Field, Class)Result.getValues(int, Class)Result.getValues(String, Class)Result.getValues(Field, Converter)Result.getValues(int, Converter)Result.getValues(String, Converter)
Missing values result in null. Empty values result in empty
Strings
fetchFromCSV in interface DSLContextstring - The CSV stringheader - Whether to parse the first line as a CSV header linenull.DSLContext.fetchFromCSV(String, char)public Result<Record> fetchFromCSV(String string, boolean header, char delimiter)
DSLContext
This is inverse of calling Result.formatCSV(boolean, char). Rows
may contain data, which are interpreted as String. Use the
various conversion methods to retrieve other data types from the
Result:
Result.getValues(Field, Class)Result.getValues(int, Class)Result.getValues(String, Class)Result.getValues(Field, Converter)Result.getValues(int, Converter)Result.getValues(String, Converter)
Missing values result in null. Empty values result in empty
Strings
fetchFromCSV in interface DSLContextstring - The CSV stringheader - Whether to parse the first line as a CSV header linedelimiter - The delimiter to expect between recordsnull.DSLContext.fetchFromCSV(String),
DSLContext.fetchFromStringData(List)public Result<Record> fetchFromJSON(String string)
DSLContext
This is the inverse of calling Result.formatJSON(). Use the
various conversion methods to retrieve other data types from the
Result:
Result.getValues(Field, Class)Result.getValues(int, Class)Result.getValues(String, Class)Result.getValues(Field, Converter)Result.getValues(int, Converter)Result.getValues(String, Converter)
Missing values result in null. Empty values result in empty
Strings
fetchFromJSON in interface DSLContextstring - The JSON stringnull.public Result<Record> fetchFromStringData(String[]... strings)
DSLContextThis 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.fetchFromStringData in interface DSLContextstrings - The data to be transformed into a Resultnull.DSLContext.fetchFromStringData(List)public Result<Record> fetchFromStringData(List<String[]> strings)
DSLContextThis 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.fetchFromStringData in interface DSLContextstrings - The data to be transformed into a Resultnull.public Result<Record> fetchFromStringData(List<String[]> strings, boolean header)
DSLContextThis 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.fetchFromStringData in interface DSLContextstrings - The data to be transformed into a Resultheader - Whether to interpret the first line as a set of column
names.null.public WithAsStep with(String alias)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String) for strictly non-recursive CTE
and DSLContext.withRecursive(String) for strictly
recursive CTE.
with in interface DSLContextpublic WithAsStep with(String alias, String... fieldAliases)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContextpublic WithAsStep with(String alias, java.util.function.Function<? super Field<?>,? extends String> fieldNameFunction)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE and
DSLContext.withRecursive(String, String...) for strictly recursive CTE.
This works in a similar way as DSLContext.with(String, String...), except
that all column names are produced by a function that receives the CTE's
Select columns as input.
with in interface DSLContextpublic WithAsStep with(String alias, java.util.function.BiFunction<? super Field<?>,? super Integer,? extends String> fieldNameFunction)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE and
DSLContext.withRecursive(String, String...) for strictly recursive CTE.
This works in a similar way as DSLContext.with(String, String...), except
that all column names are produced by a function that receives the CTE's
Select columns and their column indexes as input.
with in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public WithAsStep1 with(String alias, String fieldAlias1)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public WithAsStep2 with(String alias, String fieldAlias1, String fieldAlias2)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public WithAsStep3 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public WithAsStep4 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public WithAsStep5 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public WithAsStep6 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public WithAsStep7 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public WithAsStep8 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public WithAsStep9 with(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
with in interface DSLContextpublic WithStep with(CommonTableExpression<?>... tables)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
Reusable CommonTableExpression types can be constructed through
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(CommonTableExpression...) for strictly non-recursive CTE
and DSLContext.withRecursive(CommonTableExpression...) for strictly
recursive CTE.
with in interface DSLContextpublic WithAsStep withRecursive(String alias)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String) for strictly non-recursive CTE
and DSLContext.withRecursive(String) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContextpublic WithAsStep withRecursive(String alias, String... fieldAliases)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContextpublic WithAsStep withRecursive(String alias, java.util.function.Function<? super Field<?>,? extends String> fieldNameFunction)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
This works in a similar way as DSLContext.with(String, String...), except
that all column names are produced by a function that receives the CTE's
Select columns as input.
withRecursive in interface DSLContextpublic WithAsStep withRecursive(String alias, java.util.function.BiFunction<? super Field<?>,? super Integer,? extends String> fieldNameFunction)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
This works in a similar way as DSLContext.with(String, String...), except
that all column names are produced by a function that receives the CTE's
Select columns and their column indexes as input.
withRecursive in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public WithAsStep1 withRecursive(String alias, String fieldAlias1)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public WithAsStep2 withRecursive(String alias, String fieldAlias1, String fieldAlias2)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public WithAsStep3 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public WithAsStep4 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public WithAsStep5 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public WithAsStep6 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public WithAsStep7 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public WithAsStep8 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public WithAsStep9 withRecursive(String alias, String fieldAlias1, String fieldAlias2, String fieldAlias3, String fieldAlias4, String fieldAlias5, String fieldAlias6, String fieldAlias7, String fieldAlias8, String fieldAlias9)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") 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)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(String, String...) for strictly non-recursive CTE
and DSLContext.withRecursive(String, String...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContextpublic WithStep withRecursive(CommonTableExpression<?>... tables)
DSLContextWITH clause to supply subsequent
SELECT, UPDATE, INSERT,
DELETE, and MERGE statements with
CommonTableExpressions.
Reusable CommonTableExpression types can be constructed through
The RECURSIVE keyword may be optional or unsupported in some
databases, in case of which it will not be rendered. For optimal database
interoperability and readability, however, it is suggested that you use
DSLContext.with(CommonTableExpression...) for strictly non-recursive CTE
and DSLContext.withRecursive(CommonTableExpression...) for strictly
recursive CTE.
Note that the SQLDialect.H2 database only supports single-table,
RECURSIVE common table expression lists.
withRecursive in interface DSLContextpublic <R extends Record> SelectWhereStep<R> selectFrom(Table<R> table)
DSLContext
Example:
SELECT * FROM [table] WHERE [conditions] ORDER BY [ordering] LIMIT [limit clause]
selectFrom in interface DSLContextpublic SelectSelectStep<Record> select(Collection<? extends SelectField<?>> fields)
DSLContext
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(Collection) instead.
Example:
DSLContext create = DSL.using(configuration);
create.select(fields)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
Note that passing an empty collection conveniently produces
SELECT * semantics, i.e. it:
SELECT tab1.col1, tab1.col2, ..., tabN.colN if
all columns are knownSELECT * if not all columns are known, e.g. when
using plain SQLselect in interface DSLContextDSL.select(Collection)public SelectSelectStep<Record> select(SelectField<?>... fields)
DSLContext
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL#select(Field...) 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:
SELECT tab1.col1, tab1.col2, ..., tabN.colN if
all columns are knownSELECT * if not all columns are known, e.g. when
using plain SQLselect in interface DSLContextDSL#select(Field...)@Generated(value="This method was generated using jOOQ-tools") public <T1> SelectSelectStep<Record1<T1>> select(SelectField<T1> field1)
DSLContext
This is the same as #select(Field...), except that it
declares additional record-level typesafety, which is needed by
Field.in(Select), Field.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(SelectField) instead.
Example:
using(configuration)
.select(field1)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
select in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2> SelectSelectStep<Record2<T1,T2>> select(SelectField<T1> field1, SelectField<T2> field2)
DSLContext
This is the same as #select(Field...), except that it
declares additional record-level typesafety, which is needed by
Row2.in(Select), Row2.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(SelectField, SelectField) instead.
Example:
using(configuration)
.select(field1, field2)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
select in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3> SelectSelectStep<Record3<T1,T2,T3>> select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3)
DSLContext
This is the same as #select(Field...), except that it
declares additional record-level typesafety, which is needed by
Row3.in(Select), Row3.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.select(field1, field2, field3)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
select in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4> SelectSelectStep<Record4<T1,T2,T3,T4>> select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4)
DSLContext
This is the same as #select(Field...), except that it
declares additional record-level typesafety, which is needed by
Row4.in(Select), Row4.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.select(field1, field2, field3, field4)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
select in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5> SelectSelectStep<Record5<T1,T2,T3,T4,T5>> select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5)
DSLContext
This is the same as #select(Field...), except that it
declares additional record-level typesafety, which is needed by
Row5.in(Select), Row5.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.select(field1, field2, field3, field4, field5)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
select in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6> SelectSelectStep<Record6<T1,T2,T3,T4,T5,T6>> select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6)
DSLContext
This is the same as #select(Field...), except that it
declares additional record-level typesafety, which is needed by
Row6.in(Select), Row6.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.select(field1, field2, field3, .., field5, field6)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
select in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7> SelectSelectStep<Record7<T1,T2,T3,T4,T5,T6,T7>> select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7)
DSLContext
This is the same as #select(Field...), except that it
declares additional record-level typesafety, which is needed by
Row7.in(Select), Row7.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.select(field1, field2, field3, .., field6, field7)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
select in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8> SelectSelectStep<Record8<T1,T2,T3,T4,T5,T6,T7,T8>> select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8)
DSLContext
This is the same as #select(Field...), except that it
declares additional record-level typesafety, which is needed by
Row8.in(Select), Row8.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.select(field1, field2, field3, .., field7, field8)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
select in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9> SelectSelectStep<Record9<T1,T2,T3,T4,T5,T6,T7,T8,T9>> select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9)
DSLContext
This is the same as #select(Field...), except that it
declares additional record-level typesafety, which is needed by
Row9.in(Select), Row9.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.select(field1, field2, field3, .., field8, field9)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
select in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10> SelectSelectStep<Record10<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10>> select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10)
DSLContext
This is the same as #select(Field...), except that it
declares additional record-level typesafety, which is needed by
Row10.in(Select), Row10.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.select(field1, field2, field3, .., field9, field10)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
select in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11> SelectSelectStep<Record11<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11>> select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11)
DSLContext
This is the same as #select(Field...), except that it
declares additional record-level typesafety, which is needed by
Row11.in(Select), Row11.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.select(field1, field2, field3, .., field10, field11)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
select in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12> SelectSelectStep<Record12<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12>> select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12)
DSLContext
This is the same as #select(Field...), except that it
declares additional record-level typesafety, which is needed by
Row12.in(Select), Row12.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.select(field1, field2, field3, .., field11, field12)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
select in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13> SelectSelectStep<Record13<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13>> select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13)
DSLContext
This is the same as #select(Field...), except that it
declares additional record-level typesafety, which is needed by
Row13.in(Select), Row13.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.select(field1, field2, field3, .., field12, field13)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
select in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14> SelectSelectStep<Record14<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14>> select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14)
DSLContext
This is the same as #select(Field...), except that it
declares additional record-level typesafety, which is needed by
Row14.in(Select), Row14.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.select(field1, field2, field3, .., field13, field14)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
select in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15> SelectSelectStep<Record15<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15>> select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15)
DSLContext
This is the same as #select(Field...), except that it
declares additional record-level typesafety, which is needed by
Row15.in(Select), Row15.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.select(field1, field2, field3, .., field14, field15)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
select in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16> SelectSelectStep<Record16<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16>> select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16)
DSLContext
This is the same as #select(Field...), except that it
declares additional record-level typesafety, which is needed by
Row16.in(Select), Row16.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.select(field1, field2, field3, .., field15, field16)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
select in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17> SelectSelectStep<Record17<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17>> select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17)
DSLContext
This is the same as #select(Field...), except that it
declares additional record-level typesafety, which is needed by
Row17.in(Select), Row17.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.select(field1, field2, field3, .., field16, field17)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
select in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18> SelectSelectStep<Record18<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18>> select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17, SelectField<T18> field18)
DSLContext
This is the same as #select(Field...), except that it
declares additional record-level typesafety, which is needed by
Row18.in(Select), Row18.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.select(field1, field2, field3, .., field17, field18)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
select in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19> SelectSelectStep<Record19<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19>> select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17, SelectField<T18> field18, SelectField<T19> field19)
DSLContext
This is the same as #select(Field...), except that it
declares additional record-level typesafety, which is needed by
Row19.in(Select), Row19.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.select(field1, field2, field3, .., field18, field19)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
select in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20> SelectSelectStep<Record20<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20>> select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17, SelectField<T18> field18, SelectField<T19> field19, SelectField<T20> field20)
DSLContext
This is the same as #select(Field...), except that it
declares additional record-level typesafety, which is needed by
Row20.in(Select), Row20.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.select(field1, field2, field3, .., field19, field20)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
select in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21> SelectSelectStep<Record21<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21>> select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17, SelectField<T18> field18, SelectField<T19> field19, SelectField<T20> field20, SelectField<T21> field21)
DSLContext
This is the same as #select(Field...), except that it
declares additional record-level typesafety, which is needed by
Row21.in(Select), Row21.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.select(field1, field2, field3, .., field20, field21)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
select in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22> SelectSelectStep<Record22<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22>> select(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17, SelectField<T18> field18, SelectField<T19> field19, SelectField<T20> field20, SelectField<T21> field21, SelectField<T22> field22)
DSLContext
This is the same as #select(Field...), except that it
declares additional record-level typesafety, which is needed by
Row22.in(Select), Row22.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.select(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.select(field1, field2, field3, .., field21, field22)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
select in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)public SelectSelectStep<Record> selectDistinct(Collection<? extends SelectField<?>> fields)
DSLContext
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(Collection) instead.
Example:
DSLContext create = DSL.using(configuration);
create.selectDistinct(fields)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
Note that passing an empty collection conveniently produces
SELECT DISTINCT * semantics, i.e. it:
SELECT DISTINCT tab1.col1, tab1.col2, ..., tabN.colN if
all columns are knownSELECT DISTINCT * if not all columns are known, e.g. when
using plain SQLselectDistinct in interface DSLContextDSL.selectDistinct(Collection)public SelectSelectStep<Record> selectDistinct(SelectField<?>... fields)
DSLContext
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL#selectDistinct(Field...) 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:
SELECT DISTINCT tab1.col1, tab1.col2, ..., tabN.colN if
all columns are knownSELECT DISTINCT * if not all columns are known, e.g. when
using plain SQLselectDistinct in interface DSLContextDSL#selectDistinct(Field...)@Generated(value="This method was generated using jOOQ-tools") public <T1> SelectSelectStep<Record1<T1>> selectDistinct(SelectField<T1> field1)
DSLContext
This is the same as #selectDistinct(Field...), except that it
declares additional record-level typesafety, which is needed by
Field.in(Select), Field.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(SelectField) instead.
Example:
using(configuration)
.selectDistinct(field1)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectDistinct in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2> SelectSelectStep<Record2<T1,T2>> selectDistinct(SelectField<T1> field1, SelectField<T2> field2)
DSLContext
This is the same as #selectDistinct(Field...), except that it
declares additional record-level typesafety, which is needed by
Row2.in(Select), Row2.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(SelectField, SelectField) instead.
Example:
using(configuration)
.selectDistinct(field1, field2)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectDistinct in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3> SelectSelectStep<Record3<T1,T2,T3>> selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3)
DSLContext
This is the same as #selectDistinct(Field...), except that it
declares additional record-level typesafety, which is needed by
Row3.in(Select), Row3.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.selectDistinct(field1, field2, field3)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectDistinct in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4> SelectSelectStep<Record4<T1,T2,T3,T4>> selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4)
DSLContext
This is the same as #selectDistinct(Field...), except that it
declares additional record-level typesafety, which is needed by
Row4.in(Select), Row4.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.selectDistinct(field1, field2, field3, field4)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectDistinct in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5> SelectSelectStep<Record5<T1,T2,T3,T4,T5>> selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5)
DSLContext
This is the same as #selectDistinct(Field...), except that it
declares additional record-level typesafety, which is needed by
Row5.in(Select), Row5.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.selectDistinct(field1, field2, field3, field4, field5)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectDistinct in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6> SelectSelectStep<Record6<T1,T2,T3,T4,T5,T6>> selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6)
DSLContext
This is the same as #selectDistinct(Field...), except that it
declares additional record-level typesafety, which is needed by
Row6.in(Select), Row6.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.selectDistinct(field1, field2, field3, .., field5, field6)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectDistinct in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7> SelectSelectStep<Record7<T1,T2,T3,T4,T5,T6,T7>> selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7)
DSLContext
This is the same as #selectDistinct(Field...), except that it
declares additional record-level typesafety, which is needed by
Row7.in(Select), Row7.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.selectDistinct(field1, field2, field3, .., field6, field7)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectDistinct in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8> SelectSelectStep<Record8<T1,T2,T3,T4,T5,T6,T7,T8>> selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8)
DSLContext
This is the same as #selectDistinct(Field...), except that it
declares additional record-level typesafety, which is needed by
Row8.in(Select), Row8.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.selectDistinct(field1, field2, field3, .., field7, field8)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectDistinct in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9> SelectSelectStep<Record9<T1,T2,T3,T4,T5,T6,T7,T8,T9>> selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9)
DSLContext
This is the same as #selectDistinct(Field...), except that it
declares additional record-level typesafety, which is needed by
Row9.in(Select), Row9.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.selectDistinct(field1, field2, field3, .., field8, field9)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectDistinct in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10> SelectSelectStep<Record10<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10>> selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10)
DSLContext
This is the same as #selectDistinct(Field...), except that it
declares additional record-level typesafety, which is needed by
Row10.in(Select), Row10.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.selectDistinct(field1, field2, field3, .., field9, field10)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectDistinct in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11> SelectSelectStep<Record11<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11>> selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11)
DSLContext
This is the same as #selectDistinct(Field...), except that it
declares additional record-level typesafety, which is needed by
Row11.in(Select), Row11.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.selectDistinct(field1, field2, field3, .., field10, field11)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectDistinct in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12> SelectSelectStep<Record12<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12>> selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12)
DSLContext
This is the same as #selectDistinct(Field...), except that it
declares additional record-level typesafety, which is needed by
Row12.in(Select), Row12.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.selectDistinct(field1, field2, field3, .., field11, field12)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectDistinct in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13> SelectSelectStep<Record13<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13>> selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13)
DSLContext
This is the same as #selectDistinct(Field...), except that it
declares additional record-level typesafety, which is needed by
Row13.in(Select), Row13.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.selectDistinct(field1, field2, field3, .., field12, field13)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectDistinct in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14> SelectSelectStep<Record14<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14>> selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14)
DSLContext
This is the same as #selectDistinct(Field...), except that it
declares additional record-level typesafety, which is needed by
Row14.in(Select), Row14.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.selectDistinct(field1, field2, field3, .., field13, field14)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectDistinct in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15> SelectSelectStep<Record15<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15>> selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15)
DSLContext
This is the same as #selectDistinct(Field...), except that it
declares additional record-level typesafety, which is needed by
Row15.in(Select), Row15.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.selectDistinct(field1, field2, field3, .., field14, field15)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectDistinct in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16> SelectSelectStep<Record16<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16>> selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16)
DSLContext
This is the same as #selectDistinct(Field...), except that it
declares additional record-level typesafety, which is needed by
Row16.in(Select), Row16.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.selectDistinct(field1, field2, field3, .., field15, field16)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectDistinct in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17> SelectSelectStep<Record17<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17>> selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17)
DSLContext
This is the same as #selectDistinct(Field...), except that it
declares additional record-level typesafety, which is needed by
Row17.in(Select), Row17.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.selectDistinct(field1, field2, field3, .., field16, field17)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectDistinct in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18> SelectSelectStep<Record18<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18>> selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17, SelectField<T18> field18)
DSLContext
This is the same as #selectDistinct(Field...), except that it
declares additional record-level typesafety, which is needed by
Row18.in(Select), Row18.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.selectDistinct(field1, field2, field3, .., field17, field18)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectDistinct in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19> SelectSelectStep<Record19<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19>> selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17, SelectField<T18> field18, SelectField<T19> field19)
DSLContext
This is the same as #selectDistinct(Field...), except that it
declares additional record-level typesafety, which is needed by
Row19.in(Select), Row19.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.selectDistinct(field1, field2, field3, .., field18, field19)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectDistinct in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20> SelectSelectStep<Record20<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20>> selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17, SelectField<T18> field18, SelectField<T19> field19, SelectField<T20> field20)
DSLContext
This is the same as #selectDistinct(Field...), except that it
declares additional record-level typesafety, which is needed by
Row20.in(Select), Row20.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.selectDistinct(field1, field2, field3, .., field19, field20)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectDistinct in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21> SelectSelectStep<Record21<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21>> selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17, SelectField<T18> field18, SelectField<T19> field19, SelectField<T20> field20, SelectField<T21> field21)
DSLContext
This is the same as #selectDistinct(Field...), except that it
declares additional record-level typesafety, which is needed by
Row21.in(Select), Row21.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.selectDistinct(field1, field2, field3, .., field20, field21)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectDistinct in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22> SelectSelectStep<Record22<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22>> selectDistinct(SelectField<T1> field1, SelectField<T2> field2, SelectField<T3> field3, SelectField<T4> field4, SelectField<T5> field5, SelectField<T6> field6, SelectField<T7> field7, SelectField<T8> field8, SelectField<T9> field9, SelectField<T10> field10, SelectField<T11> field11, SelectField<T12> field12, SelectField<T13> field13, SelectField<T14> field14, SelectField<T15> field15, SelectField<T16> field16, SelectField<T17> field17, SelectField<T18> field18, SelectField<T19> field19, SelectField<T20> field20, SelectField<T21> field21, SelectField<T22> field22)
DSLContext
This is the same as #selectDistinct(Field...), except that it
declares additional record-level typesafety, which is needed by
Row22.in(Select), Row22.equal(Select) and other predicate
building methods taking subselect arguments.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectDistinct(SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField, SelectField) instead.
Example:
using(configuration)
.selectDistinct(field1, field2, field3, .., field21, field22)
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectDistinct in interface DSLContextDSL.selectDistinct(SelectField...),
DSLContext.selectDistinct(SelectField...)public SelectSelectStep<Record1<Integer>> selectZero()
DSLContext0 literal.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectZero() instead.
Example:
DSLContext create = DSL.using(configuration);
create.selectZero()
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectZero in interface DSLContextDSL.zero(),
DSL.selectZero()public SelectSelectStep<Record1<Integer>> selectOne()
DSLContext1 literal.
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectOne() instead.
Example:
DSLContext create = DSL.using(configuration);
create.selectOne()
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectOne in interface DSLContextDSL.one(),
DSL.selectOne()public SelectSelectStep<Record1<Integer>> selectCount()
DSLContextCOUNT(*).
This creates an attached, renderable and executable SELECT
statement from this DSLContext. If you don't need to render or
execute this SELECT statement (e.g. because you want to
create a subselect), consider using the static
DSL.selectCount() instead.
Example:
DSLContext create = DSL.using(configuration);
create.selectCount()
.from(table1)
.join(table2).on(field1.equal(field2))
.where(field1.greaterThan(100))
.orderBy(field2);
selectCount in interface DSLContextDSL.selectCount()public SelectQuery<Record> selectQuery()
DSLContextSelectQueryselectQuery in interface DSLContextpublic <R extends Record> SelectQuery<R> selectQuery(TableLike<R> table)
DSLContextSelectQueryselectQuery in interface DSLContexttable - The table to select data fromSelectQuerypublic <R extends Record> InsertQuery<R> insertQuery(Table<R> into)
DSLContextInsertQueryinsertQuery in interface DSLContextinto - The table to insert data intoInsertQuerypublic <R extends Record> InsertSetStep<R> insertInto(Table<R> into)
DSLContext
This type of insert may feel more convenient to some users, as it uses
the UPDATE statement's SET a = b syntax.
Example:
DSLContext create = DSL.using(configuration);
create.insertInto(table)
.set(field1, value1)
.set(field2, value2)
.newRecord()
.set(field1, value3)
.set(field2, value4)
.onDuplicateKeyUpdate()
.set(field1, value1)
.set(field2, value2)
.execute();
insertInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1> InsertValuesStep1<R,T1> insertInto(Table<R> into, Field<T1> field1)
DSLContext
Example:
using(configuration)
.insertInto(table, field1)
.values(field1)
.values(field1)
.onDuplicateKeyUpdate()
.set(field1, value1)
.set(field2, value2)
.execute();
insertInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2> InsertValuesStep2<R,T1,T2> insertInto(Table<R> into, Field<T1> field1, Field<T2> field2)
DSLContext
Example:
using(configuration)
.insertInto(table, field1, field2)
.values(field1, field2)
.values(field1, field2)
.onDuplicateKeyUpdate()
.set(field1, value1)
.set(field2, value2)
.execute();
insertInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3> InsertValuesStep3<R,T1,T2,T3> insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3)
DSLContext
Example:
using(configuration)
.insertInto(table, field1, field2, field3)
.values(field1, field2, field3)
.values(field1, field2, field3)
.onDuplicateKeyUpdate()
.set(field1, value1)
.set(field2, value2)
.execute();
insertInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4> InsertValuesStep4<R,T1,T2,T3,T4> insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4)
DSLContext
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();
insertInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5> InsertValuesStep5<R,T1,T2,T3,T4,T5> insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5)
DSLContext
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();
insertInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6> InsertValuesStep6<R,T1,T2,T3,T4,T5,T6> insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6)
DSLContext
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();
insertInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7> InsertValuesStep7<R,T1,T2,T3,T4,T5,T6,T7> insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7)
DSLContext
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();
insertInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8> InsertValuesStep8<R,T1,T2,T3,T4,T5,T6,T7,T8> insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8)
DSLContext
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();
insertInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9> InsertValuesStep9<R,T1,T2,T3,T4,T5,T6,T7,T8,T9> insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9)
DSLContext
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();
insertInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10> InsertValuesStep10<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10> insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10)
DSLContext
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();
insertInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11> InsertValuesStep11<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11> insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11)
DSLContext
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();
insertInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12> InsertValuesStep12<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12> insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12)
DSLContext
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();
insertInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13> InsertValuesStep13<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13> insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13)
DSLContext
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();
insertInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14> InsertValuesStep14<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14> insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14)
DSLContext
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();
insertInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15> InsertValuesStep15<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15> insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15)
DSLContext
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();
insertInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16> InsertValuesStep16<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16> insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16)
DSLContext
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();
insertInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17> InsertValuesStep17<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17> insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17)
DSLContext
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();
insertInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18> InsertValuesStep18<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18> insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18)
DSLContext
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();
insertInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19> InsertValuesStep19<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19> insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19)
DSLContext
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();
insertInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20> InsertValuesStep20<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20> insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20)
DSLContext
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();
insertInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21> InsertValuesStep21<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21> insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20, Field<T21> field21)
DSLContext
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();
insertInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22> InsertValuesStep22<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22> insertInto(Table<R> into, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20, Field<T21> field21, Field<T22> field22)
DSLContext
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();
insertInto in interface DSLContextpublic <R extends Record> InsertValuesStepN<R> insertInto(Table<R> into, Field<?>... fields)
DSLContext
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();
insertInto in interface DSLContextpublic <R extends Record> InsertValuesStepN<R> insertInto(Table<R> into, Collection<? extends Field<?>> fields)
DSLContext
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();
insertInto in interface DSLContextpublic <R extends Record> UpdateQuery<R> updateQuery(Table<R> table)
DSLContextUpdateQueryupdateQuery in interface DSLContexttable - The table to update data intoUpdateQuerypublic <R extends Record> UpdateSetFirstStep<R> update(Table<R> table)
DSLContext
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 CUBRID and 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();
update in interface DSLContextpublic <R extends Record> MergeUsingStep<R> mergeInto(Table<R> table)
DSLContextThis 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 |
|---|---|---|
| CUBRID | SQL:2008 standard and some enhancements | http://www.cubrid.org/manual/90/en/MERGE |
| 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...)
mergeInto in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1> MergeKeyStep1<R,T1> mergeInto(Table<R> table, Field<T1> field1)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2> MergeKeyStep2<R,T1,T2> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3> MergeKeyStep3<R,T1,T2,T3> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4> MergeKeyStep4<R,T1,T2,T3,T4> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5> MergeKeyStep5<R,T1,T2,T3,T4,T5> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6> MergeKeyStep6<R,T1,T2,T3,T4,T5,T6> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7> MergeKeyStep7<R,T1,T2,T3,T4,T5,T6,T7> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8> MergeKeyStep8<R,T1,T2,T3,T4,T5,T6,T7,T8> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9> MergeKeyStep9<R,T1,T2,T3,T4,T5,T6,T7,T8,T9> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10> MergeKeyStep10<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11> MergeKeyStep11<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12> MergeKeyStep12<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13> MergeKeyStep13<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14> MergeKeyStep14<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15> MergeKeyStep15<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16> MergeKeyStep16<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17> MergeKeyStep17<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18> MergeKeyStep18<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19> MergeKeyStep19<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20> MergeKeyStep20<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21> MergeKeyStep21<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20, Field<T21> field21)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)@Generated(value="This method was generated using jOOQ-tools") public <R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22> MergeKeyStep22<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22> mergeInto(Table<R> table, Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20, Field<T21> field21, Field<T22> field22)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)public <R extends Record> MergeKeyStepN<R> mergeInto(Table<R> table, Field<?>... fields)
DSLContextSQLDialect.H2
MERGE) or SQLDialect.HANA UPSERT).
This statement is available from DSL syntax only. It is known to be supported in some way by any of these dialects:
| H2 | H2 natively supports this special syntax | http://www.h2database.com/html/grammar.html#merge |
| 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 |
mergeInto in interface DSLContextpublic <R extends Record> MergeKeyStepN<R> mergeInto(Table<R> table, Collection<? extends Field<?>> fields)
DSLContextmergeInto in interface DSLContextDSLContext.mergeInto(Table, Field...)public <R extends Record> DeleteQuery<R> deleteQuery(Table<R> table)
DSLContextDeleteQuerydeleteQuery in interface DSLContexttable - The table to delete data fromDeleteQuerypublic <R extends Record> DeleteWhereStep<R> delete(Table<R> table)
DSLContext
This is an alias for DSLContext.deleteFrom(Table)
delete in interface DSLContextpublic <R extends Record> DeleteWhereStep<R> deleteFrom(Table<R> table)
DSLContext
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.
deleteFrom in interface DSLContextpublic Batch batch(Query... queries)
DSLContext
This essentially runs the following logic:
Statement s = connection.createStatement();
for (Query query : queries) {
s.addBatch(query.getSQL(true));
}
s.execute();
batch in interface DSLContextStatement.executeBatch()public Batch batch(Queries queries)
DSLContext
This essentially runs the following logic:
Statement s = connection.createStatement();
for (Query query : queries) {
s.addBatch(query.getSQL(true));
}
s.execute();
batch in interface DSLContextStatement.executeBatch()public Batch batch(String... queries)
DSLContext
This is a convenience method for calling
.batch(query(queries[0]), query(queries[1]), ...)
batch in interface DSLContextDSLContext.query(String),
DSLContext.batch(Query...),
Statement.executeBatch()public Batch batch(Collection<? extends Query> queries)
DSLContext
This essentially runs the following logic:
Statement s = connection.createStatement();
for (Query query : queries) {
s.addBatch(query.getSQL(true));
}
s.execute();
batch in interface DSLContextStatement.executeBatch()public BatchBindStep batch(Query query)
DSLContext
When running
create.batch(query)
.bind(valueA1, valueA2)
.bind(valueB1, valueB2)
.execute();
This essentially runs the following logic:
Statement s = connection.prepareStatement(query.getSQL(false));
for (Object[] bindValues : allBindValues) {
for (Object bindValue : bindValues) {
s.setXXX(bindValue);
}
s.addBatch();
}
s.execute();
Note: bind values will be inlined to a static batch query as in
DSLContext.batch(Query...), if you choose to execute queries with
Settings.getStatementType() == StatementType.STATIC_STATEMENT
batch in interface DSLContextStatement.executeBatch()public BatchBindStep batch(String sql)
DSLContext
This is a convenience method for calling
.batch(query(sql))
batch in interface DSLContextDSLContext.query(String),
DSLContext.batch(Query),
Statement.executeBatch()public Batch batch(Query query, Object[]... bindings)
DSLContext
This is a convenience method for calling DSLContext.batch(Query) and then
binding values one by one using BatchBindStep.bind(Object...)
Note: bind values will be inlined to a static batch query as in
DSLContext.batch(Query...), if you choose to execute queries with
Settings.getStatementType() == StatementType.STATIC_STATEMENT
batch in interface DSLContextDSLContext.batch(Query),
Statement.executeBatch()public Batch batch(String sql, Object[]... bindings)
DSLContext
This is a convenience method for calling
.batch(query(sql), bindings)
batch in interface DSLContextDSLContext.query(String),
DSLContext.batch(Query, Object[][]),
Statement.executeBatch()public Batch batchStore(UpdatableRecord<?>... records)
DSLContextINSERT and
UPDATE queries in batch mode (with bind values) according to
UpdatableRecord.store() semantics.
This batch operation can be executed in two modes:
Settings.getStatementType() == StatementType.PREPARED_STATEMENT
(the default)
In this mode, record order is preserved as much as possible, as long as
two subsequent records generate the same SQL (with bind variables). The
number of executed batch operations corresponds to
[number of distinct rendered SQL statements]. In the worst
case, this corresponds to the number of total records.
The record type order is preserved in the way they are passed to this
method. This is an example of how statements will be ordered: 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:
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.
This method (just like UpdatableRecord.store()) does not
implement the semantics of an actual UPSERT or
MERGE statement, which delegates the decision of whether to
INSERT or UPDATE a record to the database. The
decision is made by the client (jOOQ) depending on whether each
individual record has been fetched from the database prior to storing it.
batchStore in interface DSLContextUpdatableRecord.store(),
Statement.executeBatch()public Batch batchStore(Collection<? extends UpdatableRecord<?>> records)
DSLContextINSERT and
UPDATE queries in batch mode (with bind values) according to
UpdatableRecord.store() semantics.batchStore in interface DSLContextDSLContext.batchStore(UpdatableRecord...),
UpdatableRecord.store(),
Statement.executeBatch()public Batch batchInsert(TableRecord<?>... records)
DSLContextINSERT queries
in batch mode (with bind values) according to
TableRecord.insert() semantics.batchInsert in interface DSLContextDSLContext.batchStore(UpdatableRecord...),
TableRecord.insert(),
Statement.executeBatch()public Batch batchInsert(Collection<? extends TableRecord<?>> records)
DSLContextINSERT queries
in batch mode (with bind values) according to
TableRecord.insert() semantics.batchInsert in interface DSLContextDSLContext.batchStore(UpdatableRecord...),
Statement.executeBatch()public Batch batchUpdate(UpdatableRecord<?>... records)
DSLContextUPDATE queries
in batch mode (with bind values) according to
UpdatableRecord.update() semantics.batchUpdate in interface DSLContextDSLContext.batchStore(UpdatableRecord...),
UpdatableRecord.update(),
Statement.executeBatch()public Batch batchUpdate(Collection<? extends UpdatableRecord<?>> records)
DSLContextUPDATE queries
in batch mode (with bind values) according to
UpdatableRecord.update() semantics.batchUpdate in interface DSLContextDSLContext.batchStore(UpdatableRecord...),
UpdatableRecord.update(),
Statement.executeBatch()public Batch batchDelete(UpdatableRecord<?>... records)
DSLContextDELETE queries
in batch mode (with bind values) according to
UpdatableRecord.delete() sematics.
This batch operation can be executed in two modes:
Settings.getStatementType() == StatementType.PREPARED_STATEMENT
(the default)
In this mode, record order is preserved as much as possible, as long as
two subsequent records generate the same SQL (with bind variables). The
number of executed batch operations corresponds to
[number of distinct rendered SQL statements]. In the worst
case, this corresponds to the number of total records.
The record type order is preserved in the way they are passed to this
method. This is an example of how statements will be ordered: 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:
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.
batchDelete in interface DSLContextUpdatableRecord.delete(),
Statement.executeBatch()public Batch batchDelete(Collection<? extends UpdatableRecord<?>> records)
DSLContextDELETE queries
in batch mode (with bind values) according to
UpdatableRecord.delete() sematics.batchDelete in interface DSLContextDSLContext.batchDelete(UpdatableRecord...),
UpdatableRecord.delete(),
Statement.executeBatch()public Queries ddl(Catalog catalog)
DSLContextddl in interface DSLContextDSLContext.ddl(Catalog, DDLFlag...)public Queries ddl(Catalog schema, DDLFlag... flags)
DSLContext
The following DDLFlag can be set:
DDLFlag.SCHEMA: If set, the catalog's SCHEMA
specification will be generated.DDLFlag.TABLE: If set, the schema's TABLE
specification will be generated.DDLFlag.PRIMARY_KEY: If set, a potential
PRIMARY KEY constraint is specified inline with the table.
DDLFlag.UNIQUE: If set, any potential UNIQUE
constraint is specified inline with the table.DDLFlag.FOREIGN_KEY: If set, any potential
FOREIGN KEY constraint is specified after all the tables, as
a separate ALTER TABLE .. ADD CONSTRAINT statement.ddl in interface DSLContextpublic Queries ddl(Schema schema)
DSLContextddl in interface DSLContextDSLContext.ddl(Schema, DDLFlag...)public Queries ddl(Schema schema, DDLFlag... flags)
DSLContext
The following DDLFlag can be set:
DDLFlag.TABLE: If set, the schema's TABLE
specification will be generated.DDLFlag.PRIMARY_KEY: If set, a potential
PRIMARY KEY constraint is specified inline with the table.
DDLFlag.UNIQUE: If set, any potential UNIQUE
constraint is specified inline with the table.DDLFlag.FOREIGN_KEY: If set, any potential
FOREIGN KEY constraint is specified after all the tables, as
a separate ALTER TABLE .. ADD CONSTRAINT statement.ddl in interface DSLContextpublic Queries ddl(Table<?> table)
DSLContextddl in interface DSLContextDSLContext.ddl(Table, DDLFlag...)public Queries ddl(Table<?> table, DDLFlag... flags)
DSLContext
The following DDLFlag can be set:
DDLFlag.TABLE: If not set, this will generate nothing at all.
DDLFlag.PRIMARY_KEY: If set, a potential
PRIMARY KEY constraint is specified inline with the table.
DDLFlag.UNIQUE: If set, any potential UNIQUE
constraint is specified inline with the table.DDLFlag.FOREIGN_KEY: If set, any potential
FOREIGN KEY constraint is specified inline with the table.
ddl in interface DSLContextpublic CreateViewAsStep<Record> createView(String view, String... fields)
DSLContextCREATE VIEW statement.createView in interface DSLContextDSL.createView(String, String...)public CreateViewAsStep<Record> createView(Name view, Name... fields)
DSLContextCREATE VIEW statement.createView in interface DSLContextDSL.createView(Name, Name...)public CreateViewAsStep<Record> createView(Table<?> view, Field<?>... fields)
DSLContextCREATE VIEW statement.createView in interface DSLContextDSL.createView(Table, Field...)public CreateViewAsStep<Record> createView(String view, java.util.function.Function<? super Field<?>,? extends String> fieldNameFunction)
DSLContextCREATE VIEW statement.
This works like DSLContext.createView(String, String...) except that the
view's field names are derived from the view's Select statement
using a function.
createView in interface DSLContextDSL.createView(String, String...)public CreateViewAsStep<Record> createView(String view, java.util.function.BiFunction<? super Field<?>,? super Integer,? extends String> fieldNameFunction)
DSLContextCREATE VIEW statement.
This works like DSLContext.createView(String, String...) except that the
view's field names are derived from the view's Select statement
using a function.
createView in interface DSLContextDSL.createView(String, String...)public CreateViewAsStep<Record> createView(Name view, java.util.function.Function<? super Field<?>,? extends Name> fieldNameFunction)
DSLContextCREATE VIEW statement.
This works like DSLContext.createView(Name, Name...) except that the
view's field names are derived from the view's Select statement
using a function.
createView in interface DSLContextDSL.createView(String, String...)public CreateViewAsStep<Record> createView(Name view, java.util.function.BiFunction<? super Field<?>,? super Integer,? extends Name> fieldNameFunction)
DSLContextCREATE VIEW statement.
This works like DSLContext.createView(Name, Name...) except that the
view's field names are derived from the view's Select statement
using a function.
createView in interface DSLContextDSL.createView(String, String...)public CreateViewAsStep<Record> createView(Table<?> view, java.util.function.Function<? super Field<?>,? extends Field<?>> fieldNameFunction)
DSLContextCREATE VIEW statement.
This works like DSLContext.createView(Table, Field...) except that the
view's field names are derived from the view's Select statement
using a function.
createView in interface DSLContextDSL.createView(String, String...)public CreateViewAsStep<Record> createView(Table<?> view, java.util.function.BiFunction<? super Field<?>,? super Integer,? extends Field<?>> fieldNameFunction)
DSLContextCREATE VIEW statement.
This works like DSLContext.createView(Table, Field...) except that the
view's field names are derived from the view's Select statement
using a function.
createView in interface DSLContextDSL.createView(String, String...)public CreateViewAsStep<Record> createViewIfNotExists(String view, String... fields)
DSLContextCREATE VIEW statement.createViewIfNotExists in interface DSLContextDSL.createViewIfNotExists(String, String...)public CreateViewAsStep<Record> createViewIfNotExists(Name view, Name... fields)
DSLContextCREATE VIEW statement.createViewIfNotExists in interface DSLContextDSL.createViewIfNotExists(Name, Name...)public CreateViewAsStep<Record> createViewIfNotExists(Table<?> view, Field<?>... fields)
DSLContextCREATE VIEW statement.createViewIfNotExists in interface DSLContextDSL.createViewIfNotExists(Table, Field...)public CreateViewAsStep<Record> createViewIfNotExists(String view, java.util.function.Function<? super Field<?>,? extends String> fieldNameFunction)
DSLContextCREATE VIEW statement.
This works like DSLContext.createViewIfNotExists(String, String...) except that the
view's field names are derived from the view's Select statement
using a function.
createViewIfNotExists in interface DSLContextDSL.createViewIfNotExists(String, String...)public CreateViewAsStep<Record> createViewIfNotExists(String view, java.util.function.BiFunction<? super Field<?>,? super Integer,? extends String> fieldNameFunction)
DSLContextCREATE VIEW statement.
This works like DSLContext.createViewIfNotExists(String, String...) except that the
view's field names are derived from the view's Select statement
using a function.
createViewIfNotExists in interface DSLContextDSL.createViewIfNotExists(String, String...)public CreateViewAsStep<Record> createViewIfNotExists(Name view, java.util.function.Function<? super Field<?>,? extends Name> fieldNameFunction)
DSLContextCREATE VIEW statement.
This works like DSLContext.createViewIfNotExists(Name, Name...) except that the
view's field names are derived from the view's Select statement
using a function.
createViewIfNotExists in interface DSLContextDSL.createViewIfNotExists(String, String...)public CreateViewAsStep<Record> createViewIfNotExists(Name view, java.util.function.BiFunction<? super Field<?>,? super Integer,? extends Name> fieldNameFunction)
DSLContextCREATE VIEW statement.
This works like DSLContext.createViewIfNotExists(Name, Name...) except that the
view's field names are derived from the view's Select statement
using a function.
createViewIfNotExists in interface DSLContextDSL.createViewIfNotExists(String, String...)public CreateViewAsStep<Record> createViewIfNotExists(Table<?> view, java.util.function.Function<? super Field<?>,? extends Field<?>> fieldNameFunction)
DSLContextCREATE VIEW statement.
This works like DSLContext.createViewIfNotExists(Table, Field...) except that the
view's field names are derived from the view's Select statement
using a function.
createViewIfNotExists in interface DSLContextDSL.createViewIfNotExists(String, String...)public CreateViewAsStep<Record> createViewIfNotExists(Table<?> view, java.util.function.BiFunction<? super Field<?>,? super Integer,? extends Field<?>> fieldNameFunction)
DSLContextCREATE VIEW statement.
This works like DSLContext.createViewIfNotExists(Table, Field...) except that the
view's field names are derived from the view's Select statement
using a function.
createViewIfNotExists in interface DSLContextDSL.createViewIfNotExists(String, String...)public CreateSchemaFinalStep createSchema(String schema)
DSLContextCREATE SCHEMA statement.createSchema in interface DSLContextDSL.createSchema(String)public CreateSchemaFinalStep createSchema(Name schema)
DSLContextCREATE SCHEMA statement.createSchema in interface DSLContextDSL.createSchema(Name)public CreateSchemaFinalStep createSchema(Schema schema)
DSLContextCREATE SCHEMA statement.createSchema in interface DSLContextDSL.createSchema(Schema)public CreateSchemaFinalStep createSchemaIfNotExists(String schema)
DSLContextCREATE SCHEMA statement.createSchemaIfNotExists in interface DSLContextDSL.createSchemaIfNotExists(String)public CreateSchemaFinalStep createSchemaIfNotExists(Name schema)
DSLContextCREATE SCHEMA statement.createSchemaIfNotExists in interface DSLContextDSL.createSchemaIfNotExists(Name)public CreateSchemaFinalStep createSchemaIfNotExists(Schema schema)
DSLContextCREATE SCHEMA statement.createSchemaIfNotExists in interface DSLContextDSL.createSchemaIfNotExists(Schema)public CreateTableAsStep<Record> createTable(String table)
DSLContextCREATE TABLE statement.createTable in interface DSLContextDSL.createTable(String)public CreateTableAsStep<Record> createTable(Name table)
DSLContextCREATE TABLE statement.createTable in interface DSLContextDSL.createTable(Name)public CreateTableAsStep<Record> createTable(Table<?> table)
DSLContextCREATE TABLE statement.createTable in interface DSLContextDSL.createTable(Table)public CreateTableAsStep<Record> createTableIfNotExists(String table)
DSLContextCREATE TABLE statement.createTableIfNotExists in interface DSLContextDSL.createTableIfNotExists(String)public CreateTableAsStep<Record> createTableIfNotExists(Name table)
DSLContextCREATE TABLE statement.createTableIfNotExists in interface DSLContextDSL.createTableIfNotExists(Name)public CreateTableAsStep<Record> createTableIfNotExists(Table<?> table)
DSLContextCREATE TABLE statement.createTableIfNotExists in interface DSLContextDSL.createTableIfNotExists(Table)public CreateTableAsStep<Record> createTemporaryTable(String table)
DSLContextCREATE TEMPORARY TABLE statement.createTemporaryTable in interface DSLContextDSL.createTemporaryTable(String)public CreateTableAsStep<Record> createTemporaryTable(Name table)
DSLContextCREATE TEMPORARY TABLE statement.createTemporaryTable in interface DSLContextDSL.createTemporaryTable(Name)public CreateTableAsStep<Record> createTemporaryTable(Table<?> table)
DSLContextCREATE TEMPORARY TABLE statement.createTemporaryTable in interface DSLContextDSL.createTemporaryTable(Table)public CreateTableAsStep<Record> createGlobalTemporaryTable(String table)
DSLContextCREATE GLOBAL TEMPORARY TABLE statement.createGlobalTemporaryTable in interface DSLContextDSL.createGlobalTemporaryTable(String)public CreateTableAsStep<Record> createGlobalTemporaryTable(Name table)
DSLContextCREATE GLOBAL TEMPORARY TABLE statement.createGlobalTemporaryTable in interface DSLContextDSL.createGlobalTemporaryTable(Name)public CreateTableAsStep<Record> createGlobalTemporaryTable(Table<?> table)
DSLContextCREATE GLOBAL TEMPORARY TABLE statement.createGlobalTemporaryTable in interface DSLContextDSL.createGlobalTemporaryTable(Table)public CreateIndexStep createIndex(String index)
DSLContextCREATE INDEX statement.createIndex in interface DSLContextDSL.createIndex(String)public CreateIndexStep createIndex(Name index)
DSLContextCREATE INDEX statement.createIndex in interface DSLContextDSL.createIndex(Name)public CreateIndexStep createIndexIfNotExists(String index)
DSLContextCREATE INDEX IF NOT EXISTS statement.createIndexIfNotExists in interface DSLContextDSL.createIndexIfNotExists(String)public CreateIndexStep createIndexIfNotExists(Name index)
DSLContextCREATE INDEX IF NOT EXISTS statement.createIndexIfNotExists in interface DSLContextDSL.createIndexIfNotExists(Name)public CreateIndexStep createUniqueIndex(String index)
DSLContextCREATE UNIQUE INDEX statement.createUniqueIndex in interface DSLContextDSL.createIndex(String)public CreateIndexStep createUniqueIndex(Name index)
DSLContextCREATE UNIQUE INDEX statement.createUniqueIndex in interface DSLContextDSL.createIndex(Name)public CreateIndexStep createUniqueIndexIfNotExists(String index)
DSLContextCREATE UNIQUE INDEX statement.createUniqueIndexIfNotExists in interface DSLContextDSL.createIndex(String)public CreateIndexStep createUniqueIndexIfNotExists(Name index)
DSLContextCREATE UNIQUE INDEX statement.createUniqueIndexIfNotExists in interface DSLContextDSL.createIndex(Name)public CreateSequenceFinalStep createSequence(String sequence)
DSLContextCREATE SEQUENCE statement.createSequence in interface DSLContextDSL.createSequence(String)public CreateSequenceFinalStep createSequence(Name sequence)
DSLContextCREATE SEQUENCE statement.createSequence in interface DSLContextDSL.createSequence(Name)public CreateSequenceFinalStep createSequence(Sequence<?> sequence)
DSLContextCREATE SEQUENCE statement.createSequence in interface DSLContextDSL.createSequence(String)public CreateSequenceFinalStep createSequenceIfNotExists(String sequence)
DSLContextCREATE SEQUENCE statement.createSequenceIfNotExists in interface DSLContextDSL.createSequenceIfNotExists(String)public CreateSequenceFinalStep createSequenceIfNotExists(Name sequence)
DSLContextCREATE SEQUENCE statement.createSequenceIfNotExists in interface DSLContextDSL.createSequenceIfNotExists(Name)public CreateSequenceFinalStep createSequenceIfNotExists(Sequence<?> sequence)
DSLContextCREATE SEQUENCE statement.createSequenceIfNotExists in interface DSLContextDSL.createSequenceIfNotExists(String)public AlterSequenceStep<BigInteger> alterSequence(String sequence)
DSLContextALTER SEQUENCE statement.alterSequence in interface DSLContextDSL.alterSequence(String)public AlterSequenceStep<BigInteger> alterSequence(Name sequence)
DSLContextALTER SEQUENCE statement.alterSequence in interface DSLContextDSL.alterSequence(Name)public <T extends Number> AlterSequenceStep<T> alterSequence(Sequence<T> sequence)
DSLContextALTER SEQUENCE statement.alterSequence in interface DSLContextDSL.alterSequence(Sequence)public AlterSequenceStep<BigInteger> alterSequenceIfExists(String sequence)
DSLContextALTER SEQUENCE statement.alterSequenceIfExists in interface DSLContextDSL.alterSequenceIfExists(String)public AlterSequenceStep<BigInteger> alterSequenceIfExists(Name sequence)
DSLContextALTER SEQUENCE statement.alterSequenceIfExists in interface DSLContextDSL.alterSequenceIfExists(Name)public <T extends Number> AlterSequenceStep<T> alterSequenceIfExists(Sequence<T> sequence)
DSLContextALTER SEQUENCE statement.alterSequenceIfExists in interface DSLContextDSL.alterSequenceIfExists(Sequence)public AlterTableStep alterTable(String table)
DSLContextALTER TABLE statement.alterTable in interface DSLContextDSL.alterTable(String)public AlterTableStep alterTable(Name table)
DSLContextALTER TABLE statement.alterTable in interface DSLContextDSL.alterTable(Name)public AlterTableStep alterTable(Table<?> table)
DSLContextALTER TABLE statement.alterTable in interface DSLContextDSL.alterTable(Table)public AlterTableStep alterTableIfExists(String table)
DSLContextALTER TABLE statement.alterTableIfExists in interface DSLContextDSL.alterTableIfExists(String)public AlterTableStep alterTableIfExists(Name table)
DSLContextALTER TABLE statement.alterTableIfExists in interface DSLContextDSL.alterTableIfExists(Name)public AlterTableStep alterTableIfExists(Table<?> table)
DSLContextALTER TABLE statement.alterTableIfExists in interface DSLContextDSL.alterTableIfExists(Table)public AlterSchemaStep alterSchema(String schema)
DSLContextALTER SCHEMA statement.alterSchema in interface DSLContextDSL.alterSchema(String)public AlterSchemaStep alterSchema(Name schema)
DSLContextALTER SCHEMA statement.alterSchema in interface DSLContextDSL.alterSchema(Name)public AlterSchemaStep alterSchema(Schema schema)
DSLContextALTER SCHEMA statement.alterSchema in interface DSLContextDSL.alterSchema(Schema)public AlterSchemaStep alterSchemaIfExists(String schema)
DSLContextALTER SCHEMA statement.alterSchemaIfExists in interface DSLContextDSL.alterSchemaIfExists(String)public AlterSchemaStep alterSchemaIfExists(Name schema)
DSLContextALTER SCHEMA statement.alterSchemaIfExists in interface DSLContextDSL.alterSchemaIfExists(Name)public AlterSchemaStep alterSchemaIfExists(Schema schema)
DSLContextALTER SCHEMA statement.alterSchemaIfExists in interface DSLContextDSL.alterSchemaIfExists(Schema)public AlterViewStep alterView(String table)
DSLContextALTER VIEW statement.alterView in interface DSLContextDSL.alterView(String)public AlterViewStep alterView(Name table)
DSLContextALTER VIEW statement.alterView in interface DSLContextDSL.alterView(Name)public AlterViewStep alterView(Table<?> table)
DSLContextALTER VIEW statement.alterView in interface DSLContextDSL.alterView(Table)public AlterViewStep alterViewIfExists(String table)
DSLContextALTER VIEW statement.alterViewIfExists in interface DSLContextDSL.alterViewIfExists(String)public AlterViewStep alterViewIfExists(Name table)
DSLContextALTER VIEW statement.alterViewIfExists in interface DSLContextDSL.alterViewIfExists(Name)public AlterViewStep alterViewIfExists(Table<?> table)
DSLContextALTER VIEW statement.alterViewIfExists in interface DSLContextDSL.alterViewIfExists(Table)public AlterIndexStep alterIndex(String index)
DSLContextALTER INDEX statement.alterIndex in interface DSLContextDSL.alterIndex(String)public AlterIndexStep alterIndex(Name index)
DSLContextALTER INDEX statement.alterIndex in interface DSLContextDSL.alterIndex(Name)public AlterIndexStep alterIndexIfExists(String index)
DSLContextALTER INDEX statement.alterIndexIfExists in interface DSLContextDSL.alterIndexIfExists(String)public AlterIndexStep alterIndexIfExists(Name index)
DSLContextALTER INDEX statement.alterIndexIfExists in interface DSLContextDSL.alterIndexIfExists(Name)public DropSchemaStep dropSchema(String schema)
DSLContextDROP SCHEMA statement.dropSchema in interface DSLContextDSL.dropSchema(String)public DropSchemaStep dropSchema(Name schema)
DSLContextDROP SCHEMA statement.dropSchema in interface DSLContextDSL.dropSchema(Name)public DropSchemaStep dropSchema(Schema schema)
DSLContextDROP SCHEMA statement.dropSchema in interface DSLContextDSL.dropSchema(Schema)public DropSchemaStep dropSchemaIfExists(String schema)
DSLContextDROP SCHEMA statement.dropSchemaIfExists in interface DSLContextDSL.dropSchemaIfExists(String)public DropSchemaStep dropSchemaIfExists(Name schema)
DSLContextDROP SCHEMA statement.dropSchemaIfExists in interface DSLContextDSL.dropSchemaIfExists(Name)public DropSchemaStep dropSchemaIfExists(Schema schema)
DSLContextDROP SCHEMA statement.dropSchemaIfExists in interface DSLContextDSL.dropSchemaIfExists(Schema)public DropViewFinalStep dropView(String view)
DSLContextDROP VIEW statement.dropView in interface DSLContextDSL.dropView(String)public DropViewFinalStep dropView(Name view)
DSLContextDROP VIEW statement.dropView in interface DSLContextDSL.dropView(Name)public DropViewFinalStep dropView(Table<?> view)
DSLContextDROP VIEW statement.dropView in interface DSLContextDSL.dropView(Table)public DropViewFinalStep dropViewIfExists(String view)
DSLContextDROP VIEW IF EXISTS statement.
If your database doesn't natively support IF EXISTS, this is
emulated by catching (and ignoring) the relevant SQLException.
dropViewIfExists in interface DSLContextDSL.dropViewIfExists(String)public DropViewFinalStep dropViewIfExists(Name view)
DSLContextDROP VIEW IF EXISTS statement.
If your database doesn't natively support IF EXISTS, this is
emulated by catching (and ignoring) the relevant SQLException.
dropViewIfExists in interface DSLContextDSL.dropViewIfExists(Name)public DropViewFinalStep dropViewIfExists(Table<?> view)
DSLContextDROP VIEW IF EXISTS statement.
If your database doesn't natively support IF EXISTS, this is
emulated by catching (and ignoring) the relevant SQLException.
dropViewIfExists in interface DSLContextDSL.dropViewIfExists(Table)public DropTableStep dropTable(String table)
DSLContextDROP TABLE statement.dropTable in interface DSLContextDSL.dropTable(String)public DropTableStep dropTable(Name table)
DSLContextDROP TABLE statement.dropTable in interface DSLContextDSL.dropTable(Name)public DropTableStep dropTable(Table<?> table)
DSLContextDROP TABLE statement.dropTable in interface DSLContextDSL.dropTable(Table)public DropTableStep dropTableIfExists(String table)
DSLContextDROP TABLE IF EXISTS statement.
If your database doesn't natively support IF EXISTS, this is
emulated by catching (and ignoring) the relevant SQLException.
dropTableIfExists in interface DSLContextDSL.dropTableIfExists(String)public DropTableStep dropTableIfExists(Name table)
DSLContextDROP TABLE IF EXISTS statement.
If your database doesn't natively support IF EXISTS, this is
emulated by catching (and ignoring) the relevant SQLException.
dropTableIfExists in interface DSLContextDSL.dropTableIfExists(Name)public DropTableStep dropTableIfExists(Table<?> table)
DSLContextDROP TABLE IF EXISTS statement.
If your database doesn't natively support IF EXISTS, this is
emulated by catching (and ignoring) the relevant SQLException.
dropTableIfExists in interface DSLContextDSL.dropTableIfExists(Table)public DropIndexOnStep dropIndex(String index)
DSLContextDROP INDEX statement.dropIndex in interface DSLContextDSL.dropIndex(String)public DropIndexOnStep dropIndex(Name index)
DSLContextDROP INDEX statement.dropIndex in interface DSLContextDSL.dropIndex(Name)public DropIndexOnStep dropIndexIfExists(String index)
DSLContextDROP INDEX IF EXISTS statement.
If your database doesn't natively support IF EXISTS, this is
emulated by catching (and ignoring) the relevant SQLException.
dropIndexIfExists in interface DSLContextDSL.dropIndexIfExists(String)public DropIndexOnStep dropIndexIfExists(Name index)
DSLContextDROP INDEX IF EXISTS statement.
If your database doesn't natively support IF EXISTS, this is
emulated by catching (and ignoring) the relevant SQLException.
dropIndexIfExists in interface DSLContextDSL.dropIndexIfExists(Name)public DropSequenceFinalStep dropSequence(String sequence)
DSLContextDROP SEQUENCE statement.dropSequence in interface DSLContextDSL.dropSequence(String)public DropSequenceFinalStep dropSequence(Name sequence)
DSLContextDROP SEQUENCE statement.dropSequence in interface DSLContextDSL.dropSequence(Name)public DropSequenceFinalStep dropSequence(Sequence<?> sequence)
DSLContextDROP SEQUENCE statement.dropSequence in interface DSLContextDSL.dropSequence(Sequence)public DropSequenceFinalStep dropSequenceIfExists(String sequence)
DSLContextDROP SEQUENCE IF EXISTS statement.
If your database doesn't natively support IF EXISTS, this is
emulated by catching (and ignoring) the relevant SQLException.
dropSequenceIfExists in interface DSLContextDSL.dropSequenceIfExists(String)public DropSequenceFinalStep dropSequenceIfExists(Name sequence)
DSLContextDROP SEQUENCE IF EXISTS statement.
If your database doesn't natively support IF EXISTS, this is
emulated by catching (and ignoring) the relevant SQLException.
dropSequenceIfExists in interface DSLContextDSL.dropSequenceIfExists(Name)public DropSequenceFinalStep dropSequenceIfExists(Sequence<?> sequence)
DSLContextDROP SEQUENCE IF EXISTS statement.
If your database doesn't natively support IF EXISTS, this is
emulated by catching (and ignoring) the relevant SQLException.
dropSequenceIfExists in interface DSLContextDSL.dropSequenceIfExists(Sequence)public final TruncateIdentityStep<Record> truncate(String table)
DSLContextExample:
DSLContext create = DSL.using(configuration);
create.truncate(table)
.execute();
TRUNCATE
Most dialects implement the TRUNCATE statement. If it is not
supported, it is emulated using an equivalent DELETE
statement. This is particularly true for these dialects:
TRUNCATE
Some statements also support extensions of the TRUNCATE
statement, such as Postgres:
create.truncate(table)
.restartIdentity()
.cascade()
.execute();
These vendor-specific extensions are currently not emulated for those dialects that do not support them natively.
truncate in interface DSLContextDSLContext.truncate(Table)public final TruncateIdentityStep<Record> truncate(Name table)
DSLContextExample:
DSLContext create = DSL.using(configuration);
create.truncate(table)
.execute();
TRUNCATE
Most dialects implement the TRUNCATE statement. If it is not
supported, it is emulated using an equivalent DELETE
statement. This is particularly true for these dialects:
TRUNCATE
Some statements also support extensions of the TRUNCATE
statement, such as Postgres:
create.truncate(table)
.restartIdentity()
.cascade()
.execute();
These vendor-specific extensions are currently not emulated for those dialects that do not support them natively.
truncate in interface DSLContextDSLContext.truncate(Name)public <R extends Record> TruncateIdentityStep<R> truncate(Table<R> table)
DSLContextExample:
DSLContext create = DSL.using(configuration);
create.truncate(table)
.execute();
TRUNCATE
Most dialects implement the TRUNCATE statement. If it is not
supported, it is emulated using an equivalent DELETE
statement. This is particularly true for these dialects:
TRUNCATE
Some statements also support extensions of the TRUNCATE
statement, such as Postgres:
create.truncate(table)
.restartIdentity()
.cascade()
.execute();
These vendor-specific extensions are currently not emulated for those dialects that do not support them natively.
truncate in interface DSLContextpublic BigInteger lastID()
DSLContextThis is implemented for the following dialects:
SQLDialect.ACCESS: Using @@identitySQLDialect.ASE: Using @@identitySQLDialect.CUBRID: Using last_insert_id()SQLDialect.DERBY: Using identity_val_local()SQLDialect.H2: Using identity()SQLDialect.HSQLDB: Using identity()SQLDialect.INFORMIX: Using
dbinfo('sqlca.sqlerrd1')SQLDialect.INGRES: Using last_identity()SQLDialect.MARIADB: Using last_insert_id()SQLDialect.MYSQL: Using last_insert_id()SQLDialect.POSTGRES: Using lastval()SQLDialect.SQLITE: Using last_insert_rowid()SQLDialect.SQLSERVER: Using @@identitySQLDialect.SYBASE: Using @@identitySQLDialect.VERTICA: Using last_insert_id()lastID in interface DSLContextnull in some
dialects, if no such number is available.public BigInteger nextval(String sequence)
DSLContextDSLContext's underlying JDBC Connection.nextval in interface DSLContextpublic <T extends Number> T nextval(Sequence<T> sequence)
DSLContextDSLContext's underlying JDBC Connection.nextval in interface DSLContextpublic BigInteger currval(String sequence)
DSLContextDSLContext's underlying JDBC Connection.currval in interface DSLContextpublic <T extends Number> T currval(Sequence<T> sequence)
DSLContextDSLContext's underlying JDBC Connection.currval in interface DSLContextpublic Record newRecord(Field<?>... fields)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContextfields - The fields defining the Record type@Generated(value="This method was generated using jOOQ-tools") public <T1> Record1<T1> newRecord(Field<T1> field1)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2> Record2<T1,T2> newRecord(Field<T1> field1, Field<T2> field2)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3> Record3<T1,T2,T3> newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4> Record4<T1,T2,T3,T4> newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5> Record5<T1,T2,T3,T4,T5> newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6> Record6<T1,T2,T3,T4,T5,T6> newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7> Record7<T1,T2,T3,T4,T5,T6,T7> newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8> Record8<T1,T2,T3,T4,T5,T6,T7,T8> newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9> Record9<T1,T2,T3,T4,T5,T6,T7,T8,T9> newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10> Record10<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10> newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11> Record11<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11> newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12> Record12<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12> newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13> Record13<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13> newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14> Record14<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14> newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15> Record15<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15> newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16> Record16<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16> newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17> Record17<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17> newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18> Record18<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18> newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19> Record19<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19> newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20> Record20<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20> newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21> Record21<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21> newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20, Field<T21> field21)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22> Record22<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22> newRecord(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20, Field<T21> field21, Field<T22> field22)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContextpublic <R extends UDTRecord<R>> R newRecord(UDT<R> type)
DSLContextUDTRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContextR - The generic record typetype - The UDT describing records of type <R>public <R extends Record> R newRecord(Table<R> table)
DSLContextRecord that can be inserted into the corresponding
table.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContextR - The generic record typetable - The table holding records of type <R>public <R extends Record> R newRecord(Table<R> table, Object source)
DSLContextRecord that can be inserted into the
corresponding table.
This performs roughly the inverse operation of Record.into(Class)
The resulting record will have its internal "changed" flags set to true
for all values. This means that UpdatableRecord.store() will
perform an INSERT statement. If you wish to store the record
using an UPDATE statement, use
DSLContext.executeUpdate(UpdatableRecord) instead.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newRecord in interface DSLContextR - The generic record typetable - The table holding records of type <R>source - The source to be used to fill the new recordRecord.from(Object),
Record.into(Class)public <R extends Record> Result<R> newResult(Table<R> table)
DSLContextResult.
The result is attached to this Configuration by default. This
result can be used as a container for records.
newResult in interface DSLContextR - The generic record typetable - The table holding records of type <R>public Result<Record> newResult(Field<?>... fields)
DSLContextRecord.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContextfields - The fields defining the Record type@Generated(value="This method was generated using jOOQ-tools") public <T1> Result<Record1<T1>> newResult(Field<T1> field1)
DSLContextResult.
The resulting result is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2> Result<Record2<T1,T2>> newResult(Field<T1> field1, Field<T2> field2)
DSLContextResult.
The resulting result is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3> Result<Record3<T1,T2,T3>> newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3)
DSLContextResult.
The resulting result is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4> Result<Record4<T1,T2,T3,T4>> newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4)
DSLContextResult.
The resulting result is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5> Result<Record5<T1,T2,T3,T4,T5>> newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5)
DSLContextResult.
The resulting result is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6> Result<Record6<T1,T2,T3,T4,T5,T6>> newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6)
DSLContextResult.
The resulting result is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7> Result<Record7<T1,T2,T3,T4,T5,T6,T7>> newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7)
DSLContextResult.
The resulting result is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8> Result<Record8<T1,T2,T3,T4,T5,T6,T7,T8>> newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8)
DSLContextResult.
The resulting result is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9> Result<Record9<T1,T2,T3,T4,T5,T6,T7,T8,T9>> newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9)
DSLContextResult.
The resulting result is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10> Result<Record10<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10>> newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10)
DSLContextResult.
The resulting result is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11> Result<Record11<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11>> newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11)
DSLContextResult.
The resulting result is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12> Result<Record12<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12>> newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12)
DSLContextResult.
The resulting result is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13> Result<Record13<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13>> newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13)
DSLContextResult.
The resulting result is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14> Result<Record14<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14>> newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14)
DSLContextResult.
The resulting result is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15> Result<Record15<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15>> newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15)
DSLContextResult.
The resulting result is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16> Result<Record16<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16>> newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16)
DSLContextResult.
The resulting result is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17> Result<Record17<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17>> newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17)
DSLContextResult.
The resulting result is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18> Result<Record18<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18>> newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18)
DSLContextResult.
The resulting result is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19> Result<Record19<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19>> newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19)
DSLContextResult.
The resulting result is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20> Result<Record20<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20>> newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20)
DSLContextResult.
The resulting result is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21> Result<Record21<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21>> newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20, Field<T21> field21)
DSLContextResult.
The resulting result is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContext@Generated(value="This method was generated using jOOQ-tools") public <T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22> Result<Record22<T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13,T14,T15,T16,T17,T18,T19,T20,T21,T22>> newResult(Field<T1> field1, Field<T2> field2, Field<T3> field3, Field<T4> field4, Field<T5> field5, Field<T6> field6, Field<T7> field7, Field<T8> field8, Field<T9> field9, Field<T10> field10, Field<T11> field11, Field<T12> field12, Field<T13> field13, Field<T14> field14, Field<T15> field15, Field<T16> field16, Field<T17> field17, Field<T18> field18, Field<T19> field19, Field<T20> field20, Field<T21> field21, Field<T22> field22)
DSLContextResult.
The resulting result is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
newResult in interface DSLContextpublic <R extends Record> Result<R> fetch(ResultQuery<R> query)
DSLContextResultQuery in the context of this DSLContext and return
results.fetch in interface DSLContextquery - The query to executenull.ResultQuery.fetch()public <R extends Record> Cursor<R> fetchLazy(ResultQuery<R> query)
DSLContextResultQuery in the context of this DSLContext and return
a cursor.fetchLazy in interface DSLContextquery - The query to executenull.ResultQuery.fetchLazy()public <R extends Record> CompletionStage<Result<R>> fetchAsync(ResultQuery<R> query)
DSLContextCompletionStage.
The result is asynchronously completed by a task running in an
Executor provided by the Scope.configuration()'s
Configuration.executorProvider().
fetchAsync in interface DSLContextquery - The query to executenull.ResultQuery.fetchAsync()public <R extends Record> CompletionStage<Result<R>> fetchAsync(Executor executor, ResultQuery<R> query)
DSLContextCompletionStage that is asynchronously
completed by a task running in the given executor.fetchAsync in interface DSLContextquery - The query to executenull.ResultQuery.fetchAsync()public <R extends Record> java.util.stream.Stream<R> fetchStream(ResultQuery<R> query)
DSLContextResultQuery in the context of this DSLContext and return
a stream.fetchStream in interface DSLContextquery - The query to executeResultQuery.stream()public <R extends Record> Results fetchMany(ResultQuery<R> query)
DSLContextResultQuery in the context of this DSLContext and return
a cursor.fetchMany in interface DSLContextquery - The query to executenull.ResultQuery.fetchMany()public <R extends Record> R fetchOne(ResultQuery<R> query)
DSLContextResultQuery in the context of this DSLContext and return
a record.fetchOne in interface DSLContextquery - The query to executenull, if no record was found.ResultQuery.fetchOne()public <R extends Record> Optional<R> fetchOptional(ResultQuery<R> query)
DSLContextResultQuery in the context of this DSLContext and return
a record.fetchOptional in interface DSLContextquery - The query to executeResultQuery.fetchOptional()public <T,R extends Record1<T>> T fetchValue(ResultQuery<R> query)
DSLContextResultQuery in the context of this
DSLContext and return a single value.fetchValue in interface DSLContextquery - The query to executenull, if no record was found.public <T> T fetchValue(TableField<?,T> field)
DSLContextResultQuery in the context of this
DSLContext and return a single value.fetchValue in interface DSLContextfield - The field for which to fetch a single value.null, if no record was found.public <T,R extends Record1<T>> Optional<T> fetchOptionalValue(ResultQuery<R> query)
DSLContextResultQuery in the context of this
DSLContext and return a single value.fetchOptionalValue in interface DSLContextquery - The query to executepublic <T> Optional<T> fetchOptionalValue(TableField<?,T> field)
DSLContextResultQuery in the context of this
DSLContext and return a single value.fetchOptionalValue in interface DSLContextfield - The field for which to fetch a single value.public <T,R extends Record1<T>> List<T> fetchValues(ResultQuery<R> query)
DSLContextResultQuery in the context of this
DSLContext and return all values for the only column.fetchValues in interface DSLContextquery - The query to executenull.public <T> List<T> fetchValues(TableField<?,T> field)
DSLContextTable's TableFieldfetchValues in interface DSLContextfield - The field for which to fetch all values.null.public int fetchCount(Select<?> query)
DSLContextSelect query in the context of this DSLContext and return
a COUNT(*) value.
This wraps a pre-existing SELECT query in another one to
calculate the COUNT(*) value, without modifying the original
SELECT. An example: 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.
fetchCount in interface DSLContextquery - The wrapped queryCOUNT(*) resultpublic int fetchCount(Table<?> table)
DSLContext
This executes SELECT COUNT(*) FROM table
fetchCount in interface DSLContexttable - The table whose records to countpublic int fetchCount(Table<?> table, Condition condition)
DSLContext
This executes SELECT COUNT(*) FROM table WHERE condition
fetchCount in interface DSLContexttable - The table whose records to countpublic boolean fetchExists(Select<?> query) throws DataAccessException
DSLContextSelect would return any records, if it were executed.
This wraps a pre-existing SELECT query in another one to
check for result existence, without modifying the original
SELECT. An example:
-- Original query:
SELECT id, title FROM book WHERE title LIKE '%a%'
-- Wrapped query:
SELECT EXISTS (
SELECT id, title FROM book WHERE title LIKE '%a%'
)
fetchExists in interface DSLContextquery - The wrapped queryEXISTS(...) resultDataAccessException - if something went wrong executing the querypublic boolean fetchExists(Table<?> table) throws DataAccessException
DSLContext
This executes SELECT EXISTS(SELECT * FROM table)
fetchExists in interface DSLContexttable - The table whose records to countDataAccessException - if something went wrong executing the querypublic boolean fetchExists(Table<?> table, Condition condition) throws DataAccessException
DSLContext
This executes SELECT EXISTS(SELECT * FROM table WHERE condition)
fetchExists in interface DSLContexttable - The table whose records to countDataAccessException - if something went wrong executing the querypublic int execute(Query query)
DSLContextQuery in the context of this DSLContext.execute in interface DSLContextquery - The query to executeQuery.execute()public <R extends Record> Result<R> fetch(Table<R> table)
DSLContextSELECT * FROM [table]
.
The result and its contained records are attached to this
Configuration by default. Use Settings.isAttachRecords()
to override this behaviour.
fetch in interface DSLContextnull.public <R extends Record> Result<R> fetch(Table<R> table, Condition condition)
DSLContextSELECT * FROM [table] WHERE [condition]
.
The result and its contained records are attached to this
Configuration by default. Use Settings.isAttachRecords()
to override this behaviour.
fetch in interface DSLContextnull.public <R extends Record> R fetchOne(Table<R> table)
DSLContextSELECT * FROM [table]
.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
fetchOne in interface DSLContextnull, if no record was found.public <R extends Record> R fetchOne(Table<R> table, Condition condition)
DSLContextSELECT * FROM [table] WHERE [condition]
.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
fetchOne in interface DSLContextnull, if no record was found.public <R extends Record> Optional<R> fetchOptional(Table<R> table)
DSLContextSELECT * FROM [table]
.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
fetchOptional in interface DSLContextpublic <R extends Record> Optional<R> fetchOptional(Table<R> table, Condition condition)
DSLContextSELECT * FROM [table] WHERE [condition]
.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
fetchOptional in interface DSLContextpublic <R extends Record> R fetchAny(Table<R> table)
DSLContextSELECT * FROM [table] LIMIT 1
.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
fetchAny in interface DSLContextnull if no record was returnedpublic <R extends Record> R fetchAny(Table<R> table, Condition condition)
DSLContextSELECT * FROM [table] WHERE [condition] LIMIT 1
.
The resulting record is attached to this Configuration by
default. Use Settings.isAttachRecords() to override this
behaviour.
fetchAny in interface DSLContextnull if no record was returnedpublic <R extends Record> Cursor<R> fetchLazy(Table<R> table)
DSLContextSELECT * FROM [table]
.
The result and its contained records are attached to this
Configuration by default. Use Settings.isAttachRecords()
to override this behaviour.
fetchLazy in interface DSLContextnull.public <R extends Record> Cursor<R> fetchLazy(Table<R> table, Condition condition)
DSLContextSELECT * FROM [table] WHERE [condition]
.
The result and its contained records are attached to this
Configuration by default. Use Settings.isAttachRecords()
to override this behaviour.
fetchLazy in interface DSLContextnull.public <R extends Record> CompletionStage<Result<R>> fetchAsync(Table<R> table)
DSLContextSELECT * FROM [table]
.
The result and its contained records are attached to this
Configuration by default. Use Settings.isAttachRecords()
to override this behaviour.
fetchAsync in interface DSLContextnull.public <R extends Record> CompletionStage<Result<R>> fetchAsync(Table<R> table, Condition condition)
DSLContextSELECT * FROM [table] WHERE [condition]
.
The result and its contained records are attached to this
Configuration by default. Use Settings.isAttachRecords()
to override this behaviour.
fetchAsync in interface DSLContextnull.public <R extends Record> CompletionStage<Result<R>> fetchAsync(Executor executor, Table<R> table)
DSLContextSELECT * FROM [table]
.
The result and its contained records are attached to this
Configuration by default. Use Settings.isAttachRecords()
to override this behaviour.
fetchAsync in interface DSLContextnull.public <R extends Record> CompletionStage<Result<R>> fetchAsync(Executor executor, Table<R> table, Condition condition)
DSLContextSELECT * FROM [table] WHERE [condition]
.
The result and its contained records are attached to this
Configuration by default. Use Settings.isAttachRecords()
to override this behaviour.
fetchAsync in interface DSLContextnull.public <R extends Record> java.util.stream.Stream<R> fetchStream(Table<R> table)
DSLContextSELECT * FROM [table]
.
The result and its contained records are attached to this
Configuration by default. Use Settings.isAttachRecords()
to override this behaviour.
fetchStream in interface DSLContextpublic <R extends Record> java.util.stream.Stream<R> fetchStream(Table<R> table, Condition condition)
DSLContextSELECT * FROM [table] WHERE [condition]
.
The result and its contained records are attached to this
Configuration by default. Use Settings.isAttachRecords()
to override this behaviour.
fetchStream in interface DSLContextpublic <R extends TableRecord<R>> int executeInsert(R record)
DSLContext
This executes something like the following statement:
INSERT INTO [table] ... VALUES [record]
Unlike UpdatableRecord.store(), this does not change any of the
argument record's internal "changed" flags, such that a
subsequent call to UpdatableRecord.store() might lead to another
INSERT statement being executed.
executeInsert in interface DSLContextpublic <R extends UpdatableRecord<R>> int executeUpdate(R record)
DSLContextUPDATE [table] SET [modified values in record] WHERE [record is supplied record]
executeUpdate in interface DSLContextpublic <R extends TableRecord<R>,T> int executeUpdate(R record, Condition condition)
DSLContextUPDATE [table] SET [modified values in record] WHERE [condition]
executeUpdate in interface DSLContextpublic <R extends UpdatableRecord<R>> int executeDelete(R record)
DSLContextDELETE FROM [table] WHERE [record is supplied record]
executeDelete in interface DSLContextpublic <R extends TableRecord<R>,T> int executeDelete(R record, Condition condition)
DSLContextDELETE FROM [table] WHERE [condition]
executeDelete in interface DSLContextpublic final Configuration configuration()
Scopeconfiguration in interface Scopepublic final Settings settings()
Scope
This method is a convenient way of accessing
configuration().settings().
public final SQLDialect dialect()
ScopeSQLDialect wrapped by this context.
This method is a convenient way of accessing
configuration().dialect().
public final SQLDialect family()
ScopeSQLDialect.family() wrapped by this context.
This method is a convenient way of accessing
configuration().dialect().family().
public final Map<Object,Object> data()
ScopeScope.
This is custom data that was previously set to the context using
Scope.data(Object, Object). Use custom data if you want to pass data
to QueryPart objects for a given Scope.
public final Object data(Object key)
ScopeScope.
This is custom data that was previously set to the context using
Scope.data(Object, Object). Use custom data if you want to pass data
to QueryPart objects for a given Scope
public final Object data(Object key, Object value)
ScopeScope.
This is custom data that was previously set to the context using
Scope.data(Object, Object). Use custom data if you want to pass data
to QueryPart objects for a given Scope.
Copyright © 2017. All Rights Reserved.