public interface SelectConditionStep<R extends Record> extends SelectConnectByStep<R>
Select
's DSL API when selecting generic
Record
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 details
create.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();
Modifier and Type | Method and Description |
---|---|
SelectConditionStep<R> |
and(Boolean condition)
Deprecated.
- 3.8.0 - [#4763] - Use
and(Condition) or
and(Field) instead. Due to ambiguity between
calling this method using Field.equals(Object)
argument, vs. calling the other method via a
Field.equal(Object) argument, this method will be
removed in the future. |
SelectConditionStep<R> |
and(Condition condition)
Combine the currently assembled conditions with another one using the
Operator.AND operator and proceed to the next step. |
SelectConditionStep<R> |
and(Field<Boolean> condition)
Combine the currently assembled conditions with another one using the
Operator.AND operator and proceed to the next step. |
SelectConditionStep<R> |
and(SQL sql)
Combine the currently assembled conditions with another one using the
Operator.AND operator and proceed to the next step. |
SelectConditionStep<R> |
and(String sql)
Combine the currently assembled conditions with another one using the
Operator.AND operator and proceed to the next step. |
SelectConditionStep<R> |
and(String sql,
Object... bindings)
Combine the currently assembled conditions with another one using the
Operator.AND operator and proceed to the next step. |
SelectConditionStep<R> |
and(String sql,
QueryPart... parts)
Combine the currently assembled conditions with another one using the
Operator.AND operator and proceed to the next step. |
SelectConditionStep<R> |
andExists(Select<?> select)
Combine the currently assembled conditions with an EXISTS clause using
the
Operator.AND operator and proceed to the next step. |
SelectConditionStep<R> |
andNot(Boolean condition)
Deprecated.
- 3.8.0 - [#4763] - Use
andNot(Condition) or
andNot(Field) instead. Due to ambiguity between
calling this method using Field.equals(Object)
argument, vs. calling the other method via a
Field.equal(Object) argument, this method will be
removed in the future. |
SelectConditionStep<R> |
andNot(Condition condition)
Combine the currently assembled conditions with a negated other one using
the
Operator.AND operator and proceed to the next step. |
SelectConditionStep<R> |
andNot(Field<Boolean> condition)
Combine the currently assembled conditions with a negated other one using
the
Operator.AND operator and proceed to the next step. |
SelectConditionStep<R> |
andNotExists(Select<?> select)
Combine the currently assembled conditions with a NOT EXISTS clause using
the
Operator.AND operator and proceed to the next step. |
SelectConditionStep<R> |
or(Boolean condition)
Deprecated.
- 3.8.0 - [#4763] - Use
or(Condition) or
or(Field) instead. Due to ambiguity between
calling this method using Field.equals(Object)
argument, vs. calling the other method via a
Field.equal(Object) argument, this method will be
removed in the future. |
SelectConditionStep<R> |
or(Condition condition)
Combine the currently assembled conditions with another one using the
Operator.OR operator and proceed to the next step. |
SelectConditionStep<R> |
or(Field<Boolean> condition)
Combine the currently assembled conditions with another one using the
Operator.OR operator and proceed to the next step. |
SelectConditionStep<R> |
or(SQL sql)
Combine the currently assembled conditions with another one using the
Operator.OR operator and proceed to the next step. |
SelectConditionStep<R> |
or(String sql)
Combine the currently assembled conditions with another one using the
Operator.OR operator and proceed to the next step. |
SelectConditionStep<R> |
or(String sql,
Object... bindings)
Combine the currently assembled conditions with another one using the
Operator.OR operator and proceed to the next step. |
SelectConditionStep<R> |
or(String sql,
QueryPart... parts)
Combine the currently assembled conditions with another one using the
Operator.OR operator and proceed to the next step. |
SelectConditionStep<R> |
orExists(Select<?> select)
Combine the currently assembled conditions with an EXISTS clause using
the
Operator.OR operator and proceed to the next step. |
SelectConditionStep<R> |
orNot(Boolean condition)
Deprecated.
- 3.8.0 - [#4763] - Use
orNot(Condition) or
orNot(Field) instead. Due to ambiguity between
calling this method using Field.equals(Object)
argument, vs. calling the other method via a
Field.equal(Object) argument, this method will be
removed in the future. |
SelectConditionStep<R> |
orNot(Condition condition)
Combine the currently assembled conditions with a negated other one using
the
Operator.OR operator and proceed to the next step. |
SelectConditionStep<R> |
orNot(Field<Boolean> condition)
Combine the currently assembled conditions with a negated other one using
the
Operator.OR operator and proceed to the next step. |
SelectConditionStep<R> |
orNotExists(Select<?> select)
Combine the currently assembled conditions with a NOT EXISTS clause using
the
Operator.OR operator and proceed to the next step. |
connectBy, connectBy, connectBy, connectBy, connectBy, connectBy, connectBy, connectByNoCycle, connectByNoCycle, connectByNoCycle, connectByNoCycle, connectByNoCycle, connectByNoCycle, connectByNoCycle
groupBy, groupBy
having, having, having, having, having, having, having, having
window, window
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, 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, orderSiblingsBy
limit, limit, limit, limit, limit, limit, offset, offset
forShare, forUpdate, withCheckOption, withReadOnly
option
except, exceptAll, intersect, intersectAll, union, unionAll
getQuery
fetchCount, getSelect
bind, bind, 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, 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, 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, fetchSize, fetchStream, getRecordType, getResult, intern, intern, intern, intern, iterator, keepStatement, maxRows, queryTimeout, resultSetConcurrency, resultSetHoldability, resultSetType, stream
cancel, close, execute, executeAsync, executeAsync, getBindValues, getParam, getParams, getSQL, getSQL, getSQL, isExecutable
attach, detach
forEach, spliterator
@Support SelectConditionStep<R> and(Condition condition)
Operator.AND
operator and proceed to the next step.@Support SelectConditionStep<R> and(Field<Boolean> condition)
Operator.AND
operator and proceed to the next step.@Deprecated @Support SelectConditionStep<R> and(Boolean condition)
and(Condition)
or
and(Field)
instead. Due to ambiguity between
calling this method using Field.equals(Object)
argument, vs. calling the other method via a
Field.equal(Object)
argument, this method will be
removed in the future.Operator.AND
operator and proceed to the next step.@Support @PlainSQL SelectConditionStep<R> and(SQL sql)
Operator.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!
DSL.condition(SQL)
,
SQL
@Support @PlainSQL SelectConditionStep<R> and(String sql)
Operator.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!
DSL.condition(String)
,
SQL
@Support @PlainSQL SelectConditionStep<R> and(String sql, Object... bindings)
Operator.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!
@Support @PlainSQL SelectConditionStep<R> and(String sql, QueryPart... parts)
Operator.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!
@Support SelectConditionStep<R> andNot(Condition condition)
Operator.AND
operator and proceed to the next step.@Support SelectConditionStep<R> andNot(Field<Boolean> condition)
Operator.AND
operator and proceed to the next step.@Deprecated @Support SelectConditionStep<R> andNot(Boolean condition)
andNot(Condition)
or
andNot(Field)
instead. Due to ambiguity between
calling this method using Field.equals(Object)
argument, vs. calling the other method via a
Field.equal(Object)
argument, this method will be
removed in the future.Operator.AND
operator and proceed to the next step.@Support SelectConditionStep<R> andExists(Select<?> select)
Operator.AND
operator and proceed to the next step.@Support SelectConditionStep<R> andNotExists(Select<?> select)
Operator.AND
operator and proceed to the next step.@Support SelectConditionStep<R> or(Condition condition)
Operator.OR
operator and proceed to the next step.@Support SelectConditionStep<R> or(Field<Boolean> condition)
Operator.OR
operator and proceed to the next step.@Deprecated @Support SelectConditionStep<R> or(Boolean condition)
or(Condition)
or
or(Field)
instead. Due to ambiguity between
calling this method using Field.equals(Object)
argument, vs. calling the other method via a
Field.equal(Object)
argument, this method will be
removed in the future.Operator.OR
operator and proceed to the next step.@Support @PlainSQL SelectConditionStep<R> or(SQL sql)
Operator.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!
DSL.condition(SQL)
,
SQL
@Support @PlainSQL SelectConditionStep<R> or(String sql)
Operator.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!
DSL.condition(String)
,
SQL
@Support @PlainSQL SelectConditionStep<R> or(String sql, Object... bindings)
Operator.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!
@Support @PlainSQL SelectConditionStep<R> or(String sql, QueryPart... parts)
Operator.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!
@Support SelectConditionStep<R> orNot(Condition condition)
Operator.OR
operator and proceed to the next step.@Support SelectConditionStep<R> orNot(Field<Boolean> condition)
Operator.OR
operator and proceed to the next step.@Deprecated @Support SelectConditionStep<R> orNot(Boolean condition)
orNot(Condition)
or
orNot(Field)
instead. Due to ambiguity between
calling this method using Field.equals(Object)
argument, vs. calling the other method via a
Field.equal(Object)
argument, this method will be
removed in the future.Operator.OR
operator and proceed to the next step.@Support SelectConditionStep<R> orExists(Select<?> select)
Operator.OR
operator and proceed to the next step.@Support SelectConditionStep<R> orNotExists(Select<?> select)
Operator.OR
operator and proceed to the next step.Copyright © 2017. All Rights Reserved.