Top Description Methods
org.jooq

public Interface SelectSeekStep13<R extends org.jooq.Record, T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13>

extends SelectLimitStep<R extends Record>
Known Direct Implementers
org.jooq.impl.SelectImpl
Imports
org.jetbrains.annotations.NotNull
This type is used for the 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
Its equivalent in jOOQ 

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();
Refer to the manual for more details
Author
Lukas Eder

Method Summary

Modifier and TypeMethod and Description
public @NotNull 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.

public @NotNull 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)

Deprecated as a consequence of Field being deprecated.
Add a synthetic SEEK AFTER clause to the query.
public @NotNull 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.

public @NotNull 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)

Deprecated as a consequence of Field being deprecated.
Add a synthetic SEEK AFTER clause to the query.
public @NotNull 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)

Deprecated - [#7461] - SEEK BEFORE is not implemented correctly
Add a synthetic SEEK BEFORE clause to the query.
public @NotNull 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)

Deprecated - [#7461] - SEEK BEFORE is not implemented correctly
Add a synthetic SEEK BEFORE clause to the query.
Inherited from org.jooq.SelectLimitStep:
limitlimitlimitlimitlimitlimitoffsetoffset

Method Detail

seekback to summary
public @NotNull 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.

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:

  1. The SQL generated from the 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.
  2. The 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 table.col1, table.col2, ... 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.

Annotations
@NotNull
@CheckReturnValue
@Support
See Also
http://use-the-index-luke.com/sql/partial-results/fetch-next-page, https://blog.jooq.org/faster-sql-paging-with-jooq-using-the-seek-method, seekAfter(Object, Object, Object, Object, Object, Object, Object, Object, Object, Object, Object, Object, Object)
seekback to summary
public @NotNull 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)

Deprecated

as a consequence of Field being deprecated. See corresponding docs for further information.

Add a synthetic 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:

  1. The SQL generated from the 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.
  2. The 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 table.col1, table.col2, ... 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.

Annotations
@NotNull
@CheckReturnValue
@Support
See Also
http://use-the-index-luke.com/sql/partial-results/fetch-next-page, https://blog.jooq.org/faster-sql-paging-with-jooq-using-the-seek-method, seekAfter(Field, Field, Field, Field, Field, Field, Field, Field, Field, Field, Field, Field, Field)
seekAfterback to summary
public @NotNull 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.

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:

  1. The SQL generated from the 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.
  2. The 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 table.col1, table.col2, ... 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.

Annotations
@NotNull
@CheckReturnValue
@Support
See Also
http://use-the-index-luke.com/sql/partial-results/fetch-next-page, https://blog.jooq.org/faster-sql-paging-with-jooq-using-the-seek-method
seekAfterback to summary
public @NotNull 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)

Deprecated

as a consequence of Field being deprecated. See corresponding docs for further information.

Add a synthetic 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:

  1. The SQL generated from the 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.
  2. The 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 table.col1, table.col2, ... 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.

Annotations
@NotNull
@CheckReturnValue
@Support
See Also
http://use-the-index-luke.com/sql/partial-results/fetch-next-page, https://blog.jooq.org/faster-sql-paging-with-jooq-using-the-seek-method
seekBeforeback to summary
public @NotNull 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)

Deprecated

- [#7461] - SEEK BEFORE is not implemented correctly

Add a synthetic 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:

  1. The SQL generated from the 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.
  2. The 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 table.col1, table.col2, ... 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.

Annotations
@Deprecated
@NotNull
@CheckReturnValue
@Support
See Also
http://use-the-index-luke.com/sql/partial-results/fetch-next-page, https://blog.jooq.org/faster-sql-paging-with-jooq-using-the-seek-method
seekBeforeback to summary
public @NotNull 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)

Deprecated

- [#7461] - SEEK BEFORE is not implemented correctly

Add a synthetic 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:

  1. The SQL generated from the 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.
  2. The 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 table.col1, table.col2, ... 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.

Annotations
@Deprecated
@NotNull
@CheckReturnValue
@Support
See Also
http://use-the-index-luke.com/sql/partial-results/fetch-next-page, https://blog.jooq.org/faster-sql-paging-with-jooq-using-the-seek-method