public interface SelectConnectByStep<R extends Record> extends SelectGroupByStep<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 |
---|---|
SelectConnectByConditionStep<R> |
connectBy(java.lang.Boolean condition)
Deprecated.
- 3.8.0 - [#4763] - Use
connectBy(Condition) or
connectBy(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. |
SelectConnectByConditionStep<R> |
connectBy(Condition condition)
Add an Oracle-specific
CONNECT BY clause to the query |
SelectConnectByConditionStep<R> |
connectBy(Field<java.lang.Boolean> condition)
Add an Oracle-specific
CONNECT BY clause to the query |
SelectConnectByConditionStep<R> |
connectBy(SQL sql)
Add an Oracle-specific
CONNECT BY clause to the query
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. |
SelectConnectByConditionStep<R> |
connectBy(java.lang.String sql)
Add an Oracle-specific
CONNECT BY clause to the query
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. |
SelectConnectByConditionStep<R> |
connectBy(java.lang.String sql,
java.lang.Object... bindings)
Add an Oracle-specific
CONNECT BY clause to the query
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. |
SelectConnectByConditionStep<R> |
connectBy(java.lang.String sql,
QueryPart... parts)
Add an Oracle-specific
CONNECT BY clause to the query
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. |
SelectConnectByConditionStep<R> |
connectByNoCycle(java.lang.Boolean condition)
Deprecated.
- 3.8.0 - [#4763] - Use
connectByNoCycle(Condition)
or connectByNoCycle(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. |
SelectConnectByConditionStep<R> |
connectByNoCycle(Condition condition)
Add an Oracle-specific
CONNECT BY NOCYCLE clause to the
query |
SelectConnectByConditionStep<R> |
connectByNoCycle(Field<java.lang.Boolean> condition)
Add an Oracle-specific
CONNECT BY NOCYCLE clause to the
query |
SelectConnectByConditionStep<R> |
connectByNoCycle(SQL sql)
Add an Oracle-specific
CONNECT BY NOCYCLE clause to the
query
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. |
SelectConnectByConditionStep<R> |
connectByNoCycle(java.lang.String sql)
Add an Oracle-specific
CONNECT BY NOCYCLE clause to the
query
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. |
SelectConnectByConditionStep<R> |
connectByNoCycle(java.lang.String sql,
java.lang.Object... bindings)
Add an Oracle-specific
CONNECT BY NOCYCLE clause to the
query
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. |
SelectConnectByConditionStep<R> |
connectByNoCycle(java.lang.String sql,
QueryPart... parts)
Add an Oracle-specific
CONNECT BY NOCYCLE clause to the
query
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. |
SelectConnectByAfterStartWithStep<R> |
startWith(java.lang.Boolean condition)
Deprecated.
- 3.8.0 - [#4763] - Use
startWith(Condition) or
startWith(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. |
SelectConnectByAfterStartWithStep<R> |
startWith(Condition condition)
Add an Oracle-specific
START WITH clause to the query's
CONNECT BY clause. |
SelectConnectByAfterStartWithStep<R> |
startWith(Field<java.lang.Boolean> condition)
Add an Oracle-specific
START WITH clause to the query's
CONNECT BY clause. |
SelectConnectByAfterStartWithStep<R> |
startWith(SQL sql)
Add an Oracle-specific
START WITH clause to the query's
CONNECT BY clause. |
SelectConnectByAfterStartWithStep<R> |
startWith(java.lang.String sql)
Add an Oracle-specific
START WITH clause to the query's
CONNECT BY clause. |
SelectConnectByAfterStartWithStep<R> |
startWith(java.lang.String sql,
java.lang.Object... bindings)
Add an Oracle-specific
START WITH clause to the query's
CONNECT BY clause. |
SelectConnectByAfterStartWithStep<R> |
startWith(java.lang.String sql,
QueryPart... parts)
Add an Oracle-specific
START WITH clause to the query's
CONNECT BY clause. |
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, 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, 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, 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, queryTimeout, resultSetConcurrency, resultSetHoldability, resultSetType, spliterator, stream
cancel, close, execute, executeAsync, executeAsync, getBindValues, getParam, getParams, getSQL, getSQL, getSQL, isExecutable
attach, configuration, detach
@Support(value={CUBRID,INFORMIX,ORACLE}) SelectConnectByConditionStep<R> connectBy(Condition condition)
CONNECT BY
clause to the query@Support(value={CUBRID,INFORMIX,ORACLE}) SelectConnectByConditionStep<R> connectBy(Field<java.lang.Boolean> condition)
CONNECT BY
clause to the query@Deprecated @Support(value={CUBRID,INFORMIX,ORACLE}) SelectConnectByConditionStep<R> connectBy(java.lang.Boolean condition)
connectBy(Condition)
or
connectBy(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.CONNECT BY
clause to the query@Support(value={CUBRID,INFORMIX,ORACLE}) @PlainSQL SelectConnectByConditionStep<R> connectBy(SQL sql)
CONNECT BY
clause to the query
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(value={CUBRID,INFORMIX,ORACLE}) @PlainSQL SelectConnectByConditionStep<R> connectBy(java.lang.String sql)
CONNECT BY
clause to the query
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(value={CUBRID,INFORMIX,ORACLE}) @PlainSQL SelectConnectByConditionStep<R> connectBy(java.lang.String sql, java.lang.Object... bindings)
CONNECT BY
clause to the query
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(value={CUBRID,INFORMIX,ORACLE}) @PlainSQL SelectConnectByConditionStep<R> connectBy(java.lang.String sql, QueryPart... parts)
CONNECT BY
clause to the query
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(value={CUBRID,INFORMIX,ORACLE}) SelectConnectByConditionStep<R> connectByNoCycle(Condition condition)
CONNECT BY NOCYCLE
clause to the
query@Support(value={CUBRID,INFORMIX,ORACLE}) SelectConnectByConditionStep<R> connectByNoCycle(Field<java.lang.Boolean> condition)
CONNECT BY NOCYCLE
clause to the
query@Deprecated @Support(value={CUBRID,INFORMIX,ORACLE}) SelectConnectByConditionStep<R> connectByNoCycle(java.lang.Boolean condition)
connectByNoCycle(Condition)
or connectByNoCycle(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.CONNECT BY NOCYCLE
clause to the
query@Support(value={CUBRID,INFORMIX,ORACLE}) @PlainSQL SelectConnectByConditionStep<R> connectByNoCycle(SQL sql)
CONNECT BY NOCYCLE
clause to the
query
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(value={CUBRID,INFORMIX,ORACLE}) @PlainSQL SelectConnectByConditionStep<R> connectByNoCycle(java.lang.String sql)
CONNECT BY NOCYCLE
clause to the
query
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(value={CUBRID,INFORMIX,ORACLE}) @PlainSQL SelectConnectByConditionStep<R> connectByNoCycle(java.lang.String sql, java.lang.Object... bindings)
CONNECT BY NOCYCLE
clause to the
query
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(value={CUBRID,INFORMIX,ORACLE}) @PlainSQL SelectConnectByConditionStep<R> connectByNoCycle(java.lang.String sql, QueryPart... parts)
CONNECT BY NOCYCLE
clause to the
query
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(value={CUBRID,INFORMIX,ORACLE}) SelectConnectByAfterStartWithStep<R> startWith(Condition condition)
START WITH
clause to the query's
CONNECT BY
clause.@Support(value={CUBRID,INFORMIX,ORACLE}) SelectConnectByAfterStartWithStep<R> startWith(Field<java.lang.Boolean> condition)
START WITH
clause to the query's
CONNECT BY
clause.@Deprecated @Support(value={CUBRID,INFORMIX,ORACLE}) SelectConnectByAfterStartWithStep<R> startWith(java.lang.Boolean condition)
startWith(Condition)
or
startWith(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.START WITH
clause to the query's
CONNECT BY
clause.@Support(value={CUBRID,INFORMIX,ORACLE}) @PlainSQL SelectConnectByAfterStartWithStep<R> startWith(SQL sql)
START WITH
clause to the query's
CONNECT BY
clause.
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(value={CUBRID,INFORMIX,ORACLE}) @PlainSQL SelectConnectByAfterStartWithStep<R> startWith(java.lang.String sql)
START WITH
clause to the query's
CONNECT BY
clause.
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(value={CUBRID,INFORMIX,ORACLE}) @PlainSQL SelectConnectByAfterStartWithStep<R> startWith(java.lang.String sql, java.lang.Object... bindings)
START WITH
clause to the query's
CONNECT BY
clause.
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(value={CUBRID,INFORMIX,ORACLE}) @PlainSQL SelectConnectByAfterStartWithStep<R> startWith(java.lang.String sql, QueryPart... parts)
START WITH
clause to the query's
CONNECT BY
clause.
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! *
Copyright © 2018. All Rights Reserved.