@Generated(value="This class was generated using jOOQ-tools") public interface SelectSeekStep13<R extends Record,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12,T13> extends SelectLimitStep<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 |
---|---|
SelectSeekLimitStep<R> |
seek(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)
Add a synthetic
SEEK AFTER clause to the query. |
SelectSeekLimitStep<R> |
seek(T1 t1,
T2 t2,
T3 t3,
T4 t4,
T5 t5,
T6 t6,
T7 t7,
T8 t8,
T9 t9,
T10 t10,
T11 t11,
T12 t12,
T13 t13)
Add a synthetic
SEEK AFTER clause to the query. |
SelectSeekLimitStep<R> |
seekAfter(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)
Add a synthetic
SEEK AFTER clause to the query. |
SelectSeekLimitStep<R> |
seekAfter(T1 t1,
T2 t2,
T3 t3,
T4 t4,
T5 t5,
T6 t6,
T7 t7,
T8 t8,
T9 t9,
T10 t10,
T11 t11,
T12 t12,
T13 t13)
Add a synthetic
SEEK AFTER clause to the query. |
SelectSeekLimitStep<R> |
seekBefore(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)
Add a synthetic
SEEK BEFORE clause to the query. |
SelectSeekLimitStep<R> |
seekBefore(T1 t1,
T2 t2,
T3 t3,
T4 t4,
T5 t5,
T6 t6,
T7 t7,
T8 t8,
T9 t9,
T10 t10,
T11 t11,
T12 t12,
T13 t13)
Add a synthetic
SEEK BEFORE clause to the query. |
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
SelectSeekLimitStep<R> seek(T1 t1, T2 t2, T3 t3, T4 t4, T5 t5, T6 t6, T7 t7, T8 t8, T9 t9, T10 t10, T11 t11, T12 t12, T13 t13)
SEEK AFTER
clause to the query.
The synthetic SEEK AFTER
clause is an alternative way to specify
an OFFSET
, and thus to perform paging in a SQL query. This
can be advantageous for two reasons:
SEEK AFTER
clause is a regular
predicate, which can be used by query plan optimisers to choose an
appropriate index. The SQL standard OFFSET
clause will need
to skip N
rows in memory.SEEK AFTER
clause is stable with respect to new data being
inserted or data being deleted while paging through pages.
Example:
DSL.using(configuration)
.selectFrom(TABLE)
.orderBy(ID, CODE)
.seek(3, "abc")
.fetch();
The above query will render the following SQL statement:
SELECT * FROM table
WHERE (id, code) > (3, 'abc')
ORDER BY id ASC, code ASC
The actual row value expression predicate may be expanded into this equivalent predicate:
WHERE (id > 3) OR (id = 3 AND code > 'abc')
The SEEK AFTER
method currently does not support seeking
NULL
values, or operating with NULLS FIRST
,
NULLS LAST
clauses in the ORDER BY
clause.
SelectSeekLimitStep<R> seek(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)
SEEK AFTER
clause to the query.
The synthetic SEEK AFTER
clause is an alternative way to specify
an OFFSET
, and thus to perform paging in a SQL query. This
can be advantageous for two reasons:
SEEK AFTER
clause is a regular
predicate, which can be used by query plan optimisers to choose an
appropriate index. The SQL standard OFFSET
clause will need
to skip N
rows in memory.SEEK AFTER
clause is stable with respect to new data being
inserted or data being deleted while paging through pages.
Example:
DSL.using(configuration)
.selectFrom(TABLE)
.orderBy(ID, CODE)
.seek(3, "abc")
.fetch();
The above query will render the following SQL statement:
SELECT * FROM table
WHERE (id, code) > (3, 'abc')
ORDER BY id ASC, code ASC
The actual row value expression predicate may be expanded into this equivalent predicate:
WHERE (id > 3) OR (id = 3 AND code > 'abc')
The SEEK AFTER
method currently does not support seeking
NULL
values, or operating with NULLS FIRST
,
NULLS LAST
clauses in the ORDER BY
clause.
SelectSeekLimitStep<R> seekAfter(T1 t1, T2 t2, T3 t3, T4 t4, T5 t5, T6 t6, T7 t7, T8 t8, T9 t9, T10 t10, T11 t11, T12 t12, T13 t13)
SEEK AFTER
clause to the query.
The synthetic SEEK AFTER
clause is an alternative way to specify
an OFFSET
, and thus to perform paging in a SQL query. This
can be advantageous for two reasons:
SEEK AFTER
clause is a regular
predicate, which can be used by query plan optimisers to choose an
appropriate index. The SQL standard OFFSET
clause will need
to skip N
rows in memory.SEEK AFTER
clause is stable with respect to new data being
inserted or data being deleted while paging through pages.
Example:
DSL.using(configuration)
.selectFrom(TABLE)
.orderBy(ID, CODE)
.seekAfter(3, "abc")
.fetch();
The above query will render the following SQL statement:
SELECT * FROM table
WHERE (id, code) > (3, 'abc')
ORDER BY id ASC, code ASC
The actual row value expression predicate may be expanded into this equivalent predicate:
WHERE (id > 3) OR (id = 3 AND code > 'abc')
The SEEK AFTER
method currently does not support seeking
NULL
values, or operating with NULLS FIRST
,
NULLS LAST
clauses in the ORDER BY
clause.
SelectSeekLimitStep<R> seekAfter(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)
SEEK AFTER
clause to the query.
The synthetic SEEK AFTER
clause is an alternative way to specify
an OFFSET
, and thus to perform paging in a SQL query. This
can be advantageous for two reasons:
SEEK AFTER
clause is a regular
predicate, which can be used by query plan optimisers to choose an
appropriate index. The SQL standard OFFSET
clause will need
to skip N
rows in memory.SEEK AFTER
clause is stable with respect to new data being
inserted or data being deleted while paging through pages.
Example:
DSL.using(configuration)
.selectFrom(TABLE)
.orderBy(ID, CODE)
.seekAfter(3, "abc")
.fetch();
The above query will render the following SQL statement:
SELECT * FROM table
WHERE (id, code) > (3, 'abc')
ORDER BY id ASC, code ASC
The actual row value expression predicate may be expanded into this equivalent predicate:
WHERE (id > 3) OR (id = 3 AND code > 'abc')
The SEEK AFTER
method currently does not support seeking
NULL
values, or operating with NULLS FIRST
,
NULLS LAST
clauses in the ORDER BY
clause.
SelectSeekLimitStep<R> seekBefore(T1 t1, T2 t2, T3 t3, T4 t4, T5 t5, T6 t6, T7 t7, T8 t8, T9 t9, T10 t10, T11 t11, T12 t12, T13 t13)
SEEK BEFORE
clause to the query.
The synthetic SEEK BEFORE
clause is an alternative way to specify
an OFFSET
, and thus to perform paging in a SQL query. This
can be advantageous for two reasons:
SEEK BEFORE
clause is a regular
predicate, which can be used by query plan optimisers to choose an
appropriate index. The SQL standard OFFSET
clause will need
to skip N
rows in memory.SEEK BEFORE
clause is stable with respect to new data being
inserted or data being deleted while paging through pages.
Example:
DSL.using(configuration)
.selectFrom(TABLE)
.orderBy(ID, CODE)
.seekBefore(3, "abc")
.fetch();
The above query will render the following SQL statement:
SELECT * FROM table
WHERE (id, code) < (3, 'abc')
ORDER BY id ASC, code ASC
The actual row value expression predicate may be expanded into this equivalent predicate:
WHERE (id < 3) OR (id = 3 AND code < 'abc')
The SEEK BEFORE
method currently does not support seeking
NULL
values, or operating with NULLS FIRST
,
NULLS LAST
clauses in the ORDER BY
clause.
SelectSeekLimitStep<R> seekBefore(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)
SEEK BEFORE
clause to the query.
The synthetic SEEK BEFORE
clause is an alternative way to specify
an OFFSET
, and thus to perform paging in a SQL query. This
can be advantageous for two reasons:
SEEK BEFORE
clause is a regular
predicate, which can be used by query plan optimisers to choose an
appropriate index. The SQL standard OFFSET
clause will need
to skip N
rows in memory.SEEK BEFORE
clause is stable with respect to new data being
inserted or data being deleted while paging through pages.
Example:
DSL.using(configuration)
.selectFrom(TABLE)
.orderBy(ID, CODE)
.seekBefore(3, "abc")
.fetch();
The above query will render the following SQL statement:
SELECT * FROM table
WHERE (id, code) < (3, 'abc')
ORDER BY id ASC, code ASC
The actual row value expression predicate may be expanded into this equivalent predicate:
WHERE (id < 3) OR (id = 3 AND code < 'abc')
The SEEK BEFORE
method currently does not support seeking
NULL
values, or operating with NULLS FIRST
,
NULLS LAST
clauses in the ORDER BY
clause.
Copyright © 2018. All Rights Reserved.