-
- All Superinterfaces:
Attachable
,AutoCloseable
,FieldLike
,Flow.Publisher<R>
,Iterable<R>
,org.reactivestreams.Publisher<R>
,Query
,QueryPart
,ResultQuery<R>
,Select<R>
,SelectConnectByStep<R>
,SelectFinalStep<R>
,SelectForUpdateStep<R>
,SelectGroupByStep<R>
,SelectHavingStep<R>
,SelectJoinStep<R>
,SelectLimitStep<R>
,SelectOptionStep<R>
,SelectOrderByStep<R>
,SelectQualifyStep<R>
,SelectUnionStep<R>
,SelectWhereStep<R>
,SelectWindowStep<R>
,Serializable
,Statement
,TableLike<R>
public interface SelectOnConditionStep<R extends Record> extends SelectJoinStep<R>
This type is used for theSelect
's DSL API when selecting genericRecord
types.Example:
Its equivalent in jOOQ-- get all authors' first and last names, and the number -- of books they've written in German, if they have written -- more than five books in German in the last three years -- (from 2011), and sort those authors by last names -- limiting results to the second and third row SELECT T_AUTHOR.FIRST_NAME, T_AUTHOR.LAST_NAME, COUNT(*) FROM T_AUTHOR JOIN T_BOOK ON T_AUTHOR.ID = T_BOOK.AUTHOR_ID WHERE T_BOOK.LANGUAGE = 'DE' AND T_BOOK.PUBLISHED > '2008-01-01' GROUP BY T_AUTHOR.FIRST_NAME, T_AUTHOR.LAST_NAME HAVING COUNT(*) > 5 ORDER BY T_AUTHOR.LAST_NAME ASC NULLS FIRST LIMIT 2 OFFSET 1 FOR UPDATE OF FIRST_NAME, LAST_NAME NO WAIT
Refer to the manual for more detailscreate.select(TAuthor.FIRST_NAME, TAuthor.LAST_NAME, create.count()) .from(T_AUTHOR) .join(T_BOOK).on(TBook.AUTHOR_ID.equal(TAuthor.ID)) .where(TBook.LANGUAGE.equal("DE")) .and(TBook.PUBLISHED.greaterThan(parseDate('2008-01-01'))) .groupBy(TAuthor.FIRST_NAME, TAuthor.LAST_NAME) .having(create.count().greaterThan(5)) .orderBy(TAuthor.LAST_NAME.asc().nullsFirst()) .limit(2) .offset(1) .forUpdate() .of(TAuthor.FIRST_NAME, TAuthor.LAST_NAME) .noWait();
Referencing
XYZ*Step
types directly from client codeIt is usually not recommended to reference any
XYZ*Step
types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql.Drawbacks of referencing the
XYZ*Step
types directly:- They're operating on mutable implementations (as of jOOQ 3.x)
- They're less composable and not easy to get right when dynamic SQL gets complex
- They're less readable
- They might have binary incompatible changes between minor releases
- Author:
- Lukas Eder
-
-
Method Summary
All Methods Instance Methods Abstract Methods Deprecated Methods Modifier and Type Method Description SelectOnConditionStep<R>
and(Boolean condition)
Deprecated.- 3.8.0 - [#4763] - Useand(Condition)
(typically withDSL.trueCondition()
,DSL.falseCondition()
, orDSL.noCondition()
as the parameter) orand(Field)
instead.SelectOnConditionStep<R>
and(String sql)
Combine the currently assembled conditions with another one using theOperator.AND
operator and proceed to the next step.SelectOnConditionStep<R>
and(String sql, Object... bindings)
Combine the currently assembled conditions with another one using theOperator.AND
operator and proceed to the next step.SelectOnConditionStep<R>
and(String sql, QueryPart... parts)
Combine the currently assembled conditions with another one using theOperator.AND
operator and proceed to the next step.SelectOnConditionStep<R>
and(Condition condition)
Combine the currently assembled conditions with another one using theOperator.AND
operator and proceed to the next step.SelectOnConditionStep<R>
and(Field<Boolean> condition)
Combine the currently assembled conditions with another one using theOperator.AND
operator and proceed to the next step.SelectOnConditionStep<R>
and(SQL sql)
Combine the currently assembled conditions with another one using theOperator.AND
operator and proceed to the next step.SelectOnConditionStep<R>
andExists(Select<?> select)
Combine the currently assembled conditions with an EXISTS clause using theOperator.AND
operator and proceed to the next step.SelectOnConditionStep<R>
andNot(Boolean condition)
Deprecated.- 3.8.0 - [#4763] - UseandNot(Condition)
(typically withDSL.trueCondition()
,DSL.falseCondition()
, orDSL.noCondition()
as the parameter) orandNot(Field)
instead.SelectOnConditionStep<R>
andNot(Condition condition)
Combine the currently assembled conditions with a negated other one using theOperator.AND
operator and proceed to the next step.SelectOnConditionStep<R>
andNot(Field<Boolean> condition)
Combine the currently assembled conditions with a negated other one using theOperator.AND
operator and proceed to the next step.SelectOnConditionStep<R>
andNotExists(Select<?> select)
Combine the currently assembled conditions with a NOT EXISTS clause using theOperator.AND
operator and proceed to the next step.SelectOnConditionStep<R>
or(Boolean condition)
Deprecated.- 3.8.0 - [#4763] - Useor(Condition)
(typically withDSL.trueCondition()
,DSL.falseCondition()
, orDSL.noCondition()
as the parameter) oror(Field)
instead.SelectOnConditionStep<R>
or(String sql)
Combine the currently assembled conditions with another one using theOperator.OR
operator and proceed to the next step.SelectOnConditionStep<R>
or(String sql, Object... bindings)
Combine the currently assembled conditions with another one using theOperator.OR
operator and proceed to the next step.SelectOnConditionStep<R>
or(String sql, QueryPart... parts)
Combine the currently assembled conditions with another one using theOperator.OR
operator and proceed to the next step.SelectOnConditionStep<R>
or(Condition condition)
Combine the currently assembled conditions with another one using theOperator.OR
operator and proceed to the next step.SelectOnConditionStep<R>
or(Field<Boolean> condition)
Combine the currently assembled conditions with another one using theOperator.OR
operator and proceed to the next step.SelectOnConditionStep<R>
or(SQL sql)
Combine the currently assembled conditions with another one using theOperator.OR
operator and proceed to the next step.SelectOnConditionStep<R>
orExists(Select<?> select)
Combine the currently assembled conditions with an EXISTS clause using theOperator.OR
operator and proceed to the next step.SelectOnConditionStep<R>
orNot(Boolean condition)
Deprecated.- 3.8.0 - [#4763] - UseorNot(Condition)
(typically withDSL.trueCondition()
,DSL.falseCondition()
, orDSL.noCondition()
as the parameter) ororNot(Field)
instead.SelectOnConditionStep<R>
orNot(Condition condition)
Combine the currently assembled conditions with a negated other one using theOperator.OR
operator and proceed to the next step.SelectOnConditionStep<R>
orNot(Field<Boolean> condition)
Combine the currently assembled conditions with a negated other one using theOperator.OR
operator and proceed to the next step.SelectOnConditionStep<R>
orNotExists(Select<?> select)
Combine the currently assembled conditions with a NOT EXISTS clause using theOperator.OR
operator and proceed to the next step.-
Methods inherited from interface org.jooq.Attachable
attach, configuration, detach
-
Methods inherited from interface java.util.concurrent.Flow.Publisher
subscribe
-
Methods inherited from interface org.jooq.Query
cancel, close, execute, executeAsync, executeAsync, getBindValues, getParam, getParams, getSQL, getSQL, getSQL, isExecutable
-
Methods inherited from interface org.jooq.ResultQuery
bind, bind, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, coerce, collect, fetch, fetch, fetch, fetch, fetch, fetch, fetch, fetch, fetch, fetch, fetch, fetch, fetch, fetch, fetchAny, fetchAny, fetchAny, fetchAny, fetchAny, fetchAny, fetchAny, fetchAny, fetchAny, fetchAny, fetchAny, fetchAny, fetchAny, fetchAny, fetchAnyArray, fetchAnyInto, fetchAnyInto, fetchAnyMap, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArrays, fetchAsync, fetchAsync, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchInto, fetchInto, fetchInto, fetchLater, fetchLater, fetchLazy, fetchLazy, fetchMany, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMaps, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOneArray, fetchOneInto, fetchOneInto, fetchOneMap, fetchOptional, fetchOptional, fetchOptional, fetchOptional, fetchOptional, fetchOptional, fetchOptional, fetchOptional, fetchOptional, fetchOptional, fetchOptional, fetchOptional, fetchOptional, fetchOptional, fetchOptionalArray, fetchOptionalInto, fetchOptionalInto, fetchOptionalMap, fetchResultSet, fetchSet, fetchSet, fetchSet, fetchSet, fetchSet, fetchSet, fetchSet, fetchSet, fetchSet, fetchSet, fetchSet, fetchSet, fetchSet, fetchSingle, fetchSingle, fetchSingle, fetchSingle, fetchSingle, fetchSingle, fetchSingle, fetchSingle, fetchSingle, fetchSingle, fetchSingle, fetchSingle, fetchSingle, fetchSingle, fetchSingleArray, fetchSingleInto, fetchSingleInto, fetchSingleMap, fetchSize, fetchStream, fetchStreamInto, fetchStreamInto, forEach, getRecordType, getResult, intern, intern, intern, intern, iterator, keepStatement, maxRows, poolable, queryTimeout, resultSetConcurrency, resultSetHoldability, resultSetType, spliterator, stream
-
Methods inherited from interface org.jooq.Select
fetchCount, getSelect
-
Methods inherited from interface org.jooq.SelectConnectByStep
connectBy, connectBy, connectBy, connectBy, connectBy, connectBy, connectBy, connectByNoCycle, connectByNoCycle, connectByNoCycle, connectByNoCycle, connectByNoCycle, connectByNoCycle, connectByNoCycle, startWith, startWith, startWith, startWith, startWith, startWith, startWith
-
Methods inherited from interface org.jooq.SelectFinalStep
getQuery
-
Methods inherited from interface org.jooq.SelectForUpdateStep
forKeyShare, forNoKeyUpdate, forShare, forUpdate, withCheckOption, withReadOnly
-
Methods inherited from interface org.jooq.SelectGroupByStep
groupBy, groupBy
-
Methods inherited from interface org.jooq.SelectHavingStep
having, having, having, having, having, having, having, having, having
-
Methods inherited from interface org.jooq.SelectJoinStep
crossApply, crossApply, crossApply, crossApply, crossApply, crossApply, crossJoin, crossJoin, crossJoin, crossJoin, crossJoin, crossJoin, fullJoin, fullJoin, fullJoin, fullJoin, fullJoin, fullJoin, fullOuterJoin, fullOuterJoin, fullOuterJoin, fullOuterJoin, fullOuterJoin, fullOuterJoin, innerJoin, innerJoin, innerJoin, innerJoin, innerJoin, innerJoin, join, join, join, join, join, join, join, leftAntiJoin, leftJoin, leftJoin, leftJoin, leftJoin, leftJoin, leftJoin, leftOuterJoin, leftOuterJoin, leftOuterJoin, leftOuterJoin, leftOuterJoin, leftOuterJoin, leftSemiJoin, naturalFullOuterJoin, naturalFullOuterJoin, naturalFullOuterJoin, naturalFullOuterJoin, naturalFullOuterJoin, naturalFullOuterJoin, naturalJoin, naturalJoin, naturalJoin, naturalJoin, naturalJoin, naturalJoin, naturalLeftOuterJoin, naturalLeftOuterJoin, naturalLeftOuterJoin, naturalLeftOuterJoin, naturalLeftOuterJoin, naturalLeftOuterJoin, naturalRightOuterJoin, naturalRightOuterJoin, naturalRightOuterJoin, naturalRightOuterJoin, naturalRightOuterJoin, naturalRightOuterJoin, outerApply, outerApply, outerApply, outerApply, outerApply, outerApply, rightJoin, rightJoin, rightJoin, rightJoin, rightJoin, rightJoin, rightOuterJoin, rightOuterJoin, rightOuterJoin, rightOuterJoin, rightOuterJoin, rightOuterJoin, straightJoin, straightJoin, straightJoin, straightJoin, straightJoin, straightJoin
-
Methods inherited from interface org.jooq.SelectLimitStep
limit, limit, limit, limit, limit, limit, limit, limit, limit, limit, offset, offset, offset
-
Methods inherited from interface org.jooq.SelectOptionStep
option
-
Methods inherited from interface org.jooq.SelectOrderByStep
orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderBy, orderSiblingsBy, orderSiblingsBy, orderSiblingsBy
-
Methods inherited from interface org.jooq.SelectQualifyStep
qualify, qualify, qualify, qualify, qualify, qualify, qualify, qualify
-
Methods inherited from interface org.jooq.SelectUnionStep
except, exceptAll, intersect, intersectAll, union, unionAll
-
Methods inherited from interface org.jooq.SelectWhereStep
where, where, where, where, where, where, where, where, where, whereExists, whereNotExists
-
Methods inherited from interface org.jooq.SelectWindowStep
window, window
-
-
-
-
Method Detail
-
and
@Support SelectOnConditionStep<R> and(Condition condition)
Combine the currently assembled conditions with another one using theOperator.AND
operator and proceed to the next step.
-
and
@Support SelectOnConditionStep<R> and(Field<Boolean> condition)
Combine the currently assembled conditions with another one using theOperator.AND
operator and proceed to the next step.
-
and
@Deprecated @Support SelectOnConditionStep<R> and(Boolean condition)
Deprecated.- 3.8.0 - [#4763] - Useand(Condition)
(typically withDSL.trueCondition()
,DSL.falseCondition()
, orDSL.noCondition()
as the parameter) orand(Field)
instead. Due to ambiguity between calling this method usingField.equals(Object)
argument, vs. calling the other method via aField.equal(Object)
argument, this method will be removed in the future.Combine the currently assembled conditions with another one using theOperator.AND
operator and proceed to the next step.
-
and
@Support @PlainSQL SelectOnConditionStep<R> and(SQL sql)
Combine the currently assembled conditions with another one using theOperator.AND
operator and proceed to the next step.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!
- See Also:
DSL.condition(SQL)
,SQL
-
and
@Support @PlainSQL SelectOnConditionStep<R> and(String sql)
Combine the currently assembled conditions with another one using theOperator.AND
operator and proceed to the next step.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!
- See Also:
DSL.condition(String)
,SQL
-
and
@Support @PlainSQL SelectOnConditionStep<R> and(String sql, Object... bindings)
Combine the currently assembled conditions with another one using theOperator.AND
operator and proceed to the next step.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!
-
and
@Support @PlainSQL SelectOnConditionStep<R> and(String sql, QueryPart... parts)
Combine the currently assembled conditions with another one using theOperator.AND
operator and proceed to the next step.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!
-
andNot
@Support SelectOnConditionStep<R> andNot(Condition condition)
Combine the currently assembled conditions with a negated other one using theOperator.AND
operator and proceed to the next step.
-
andNot
@Support SelectOnConditionStep<R> andNot(Field<Boolean> condition)
Combine the currently assembled conditions with a negated other one using theOperator.AND
operator and proceed to the next step.
-
andNot
@Deprecated @Support SelectOnConditionStep<R> andNot(Boolean condition)
Deprecated.- 3.8.0 - [#4763] - UseandNot(Condition)
(typically withDSL.trueCondition()
,DSL.falseCondition()
, orDSL.noCondition()
as the parameter) orandNot(Field)
instead. Due to ambiguity between calling this method usingField.equals(Object)
argument, vs. calling the other method via aField.equal(Object)
argument, this method will be removed in the future.Combine the currently assembled conditions with a negated other one using theOperator.AND
operator and proceed to the next step.
-
andExists
@Support SelectOnConditionStep<R> andExists(Select<?> select)
Combine the currently assembled conditions with an EXISTS clause using theOperator.AND
operator and proceed to the next step.
-
andNotExists
@Support SelectOnConditionStep<R> andNotExists(Select<?> select)
Combine the currently assembled conditions with a NOT EXISTS clause using theOperator.AND
operator and proceed to the next step.
-
or
@Support SelectOnConditionStep<R> or(Condition condition)
Combine the currently assembled conditions with another one using theOperator.OR
operator and proceed to the next step.
-
or
@Support SelectOnConditionStep<R> or(Field<Boolean> condition)
Combine the currently assembled conditions with another one using theOperator.OR
operator and proceed to the next step.
-
or
@Deprecated @Support SelectOnConditionStep<R> or(Boolean condition)
Deprecated.- 3.8.0 - [#4763] - Useor(Condition)
(typically withDSL.trueCondition()
,DSL.falseCondition()
, orDSL.noCondition()
as the parameter) oror(Field)
instead. Due to ambiguity between calling this method usingField.equals(Object)
argument, vs. calling the other method via aField.equal(Object)
argument, this method will be removed in the future.Combine the currently assembled conditions with another one using theOperator.OR
operator and proceed to the next step.
-
or
@Support @PlainSQL SelectOnConditionStep<R> or(SQL sql)
Combine the currently assembled conditions with another one using theOperator.OR
operator and proceed to the next step.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!
- See Also:
DSL.condition(SQL)
,SQL
-
or
@Support @PlainSQL SelectOnConditionStep<R> or(String sql)
Combine the currently assembled conditions with another one using theOperator.OR
operator and proceed to the next step.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!
- See Also:
DSL.condition(String)
,SQL
-
or
@Support @PlainSQL SelectOnConditionStep<R> or(String sql, Object... bindings)
Combine the currently assembled conditions with another one using theOperator.OR
operator and proceed to the next step.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!
-
or
@Support @PlainSQL SelectOnConditionStep<R> or(String sql, QueryPart... parts)
Combine the currently assembled conditions with another one using theOperator.OR
operator and proceed to the next step.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!
-
orNot
@Support SelectOnConditionStep<R> orNot(Condition condition)
Combine the currently assembled conditions with a negated other one using theOperator.OR
operator and proceed to the next step.
-
orNot
@Support SelectOnConditionStep<R> orNot(Field<Boolean> condition)
Combine the currently assembled conditions with a negated other one using theOperator.OR
operator and proceed to the next step.
-
orNot
@Deprecated @Support SelectOnConditionStep<R> orNot(Boolean condition)
Deprecated.- 3.8.0 - [#4763] - UseorNot(Condition)
(typically withDSL.trueCondition()
,DSL.falseCondition()
, orDSL.noCondition()
as the parameter) ororNot(Field)
instead. Due to ambiguity between calling this method usingField.equals(Object)
argument, vs. calling the other method via aField.equal(Object)
argument, this method will be removed in the future.Combine the currently assembled conditions with a negated other one using theOperator.OR
operator and proceed to the next step.
-
orExists
@Support SelectOnConditionStep<R> orExists(Select<?> select)
Combine the currently assembled conditions with an EXISTS clause using theOperator.OR
operator and proceed to the next step.
-
orNotExists
@Support SelectOnConditionStep<R> orNotExists(Select<?> select)
Combine the currently assembled conditions with a NOT EXISTS clause using theOperator.OR
operator and proceed to the next step.
-
-