@Generated(value="This class was generated using jOOQ-tools") public interface SelectSeekStepN<R extends Record> extends SelectLimitStep<R>
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 | 
|---|---|
| SelectSeekLimitStep<R> | seek(Field<?>... fields)Add a synthetic  SEEK AFTERclause to the query. | 
| SelectSeekLimitStep<R> | seek(Object... values)Add a synthetic  SEEK AFTERclause to the query. | 
| SelectSeekLimitStep<R> | seekAfter(Field<?>... fields)Add a synthetic  SEEK AFTERclause to the query. | 
| SelectSeekLimitStep<R> | seekAfter(Object... values)Add a synthetic  SEEK AFTERclause to the query. | 
| SelectSeekLimitStep<R> | seekBefore(Field<?>... fields)Deprecated. 
 - [#7461] - SEEK BEFORE is not implemented correctly | 
| SelectSeekLimitStep<R> | seekBefore(Object... values)Deprecated. 
 - [#7461] - SEEK BEFORE is not implemented correctly | 
limit, limit, limit, limit, limit, limit, offset, offsetforShare, forUpdate, withCheckOption, withReadOnlyoptionexcept, exceptAll, intersect, intersectAll, union, unionAllgetQueryfetchCount, getSelectbind, bind, 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, queryTimeout, resultSetConcurrency, resultSetHoldability, resultSetType, spliterator, streamcancel, close, execute, executeAsync, executeAsync, getBindValues, getParam, getParams, getSQL, getSQL, getSQL, isExecutableattach, configuration, detachSelectSeekLimitStep<R> seek(Object... values)
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<?>... fields)
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(Object... values)
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<?>... fields)
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.
@Deprecated SelectSeekLimitStep<R> seekBefore(Object... values)
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.
@Deprecated SelectSeekLimitStep<R> seekBefore(Field<?>... fields)
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 © 2019. All rights reserved.