public interface SelectConnectByConditionStep extends SelectStartWithStep
Select's DSL API when selecting generic
Record types.
Example:
-- 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
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 |
and(Condition condition)
Combine the currently assembled conditions with another one using the
Operator.AND operator and proceed to the next step. |
SelectConnectByConditionStep |
and(String sql)
Combine the currently assembled conditions with another one using the
Operator.AND operator and proceed to the next step. |
SelectConnectByConditionStep |
and(String sql,
Object... bindings)
Combine the currently assembled conditions with another one using the
Operator.AND operator and proceed to the next step. |
SelectConnectByConditionStep |
and(String sql,
QueryPart... parts)
Combine the currently assembled conditions with another one using the
Operator.AND operator and proceed to the next step. |
startWith, startWith, startWith, startWithgroupBy, groupByorderBy, orderBy, orderBy, orderBy, orderSiblingsBy, orderSiblingsBy, orderSiblingsBy, orderSiblingsByforShare, forUpdategetQuerybind, bind, fetch, fetch, fetch, fetch, fetch, fetch, fetch, fetch, fetch, fetch, fetch, fetchAny, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArray, fetchArrays, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchGroups, fetchInto, fetchInto, fetchInto, fetchLater, fetchLater, fetchLazy, fetchLazy, fetchMany, fetchMap, fetchMap, fetchMap, fetchMap, fetchMap, fetchMaps, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOne, fetchOneArray, fetchOneMap, fetchResultSet, getRecordType, getResult, keepStatement, maxRows, queryTimeoutcancel, close, execute, getBindValues, getParam, getParams, getSQL, getSQL, isExecutableinternalAPI@Support(value={CUBRID,ORACLE}) SelectConnectByConditionStep and(Condition condition)
Operator.AND operator and proceed to the next step.@Support(value={CUBRID,ORACLE}) SelectConnectByConditionStep 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!
Factory.condition(String)@Support(value={CUBRID,ORACLE}) SelectConnectByConditionStep 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!
Factory.condition(String, Object...)@Support(value={CUBRID,ORACLE}) SelectConnectByConditionStep 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!
Copyright © 2013. All Rights Reserved.