- All Known Subinterfaces:
SelectJoinPartitionByStep<R>
,SelectOptionalOnStep<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
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
Referencing XYZ*Step
types directly from client code
It is usually not recommended to reference any XYZ*Step
types
directly from client code, or assign them to local variables. When writing
dynamic SQL, creating a statement's components dynamically, and passing them
to the DSL API statically is usually a better choice. See the manual's
section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql.
Drawbacks of referencing the XYZ*Step
types directly:
- They're operating on mutable implementations (as of jOOQ 3.x)
- They're less composable and not easy to get right when dynamic SQL gets complex
- They're less readable
- They might have binary incompatible changes between minor releases
- Author:
- Lukas Eder
-
Method Summary
Modifier and TypeMethodDescription@NotNull SelectOnConditionStep<R>
Add anON
clause to the previousJOIN
.@NotNull SelectOnConditionStep<R>
Add anON
clause to the previousJOIN
.@NotNull SelectOnConditionStep<R>
Add anON
clause to the previousJOIN
.@NotNull SelectOnConditionStep<R>
@NotNull SelectOnConditionStep<R>
@NotNull SelectOnConditionStep<R>
Add anON
clause to the previousJOIN
.@NotNull SelectOnConditionStep<R>
Add anON
clause to the previousJOIN
.@NotNull SelectOnConditionStep<R>
onKey()
Join the previous table on a non-ambiguous foreign key relationship between the two joined tables.@NotNull SelectOnConditionStep<R>
onKey
(ForeignKey<?, ?> key) Join the table on a non-ambiguous foreign key relationship between the two joined tables.@NotNull SelectOnConditionStep<R>
onKey
(TableField<?, ?>... keyFields) Join the previous table on a non-ambiguous foreign key relationship between the two joined tables.@NotNull SelectJoinStep<R>
using
(Collection<? extends Field<?>> fields) Join the previous table with theUSING(column [, column…])
syntax.@NotNull SelectJoinStep<R>
Join the previous table with theUSING(column [, column…])
syntax.
-
Method Details
-
on
-
on
-
on
Add anON
clause to the previousJOIN
. -
on
Add anON
clause to the previousJOIN
.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!
- See Also:
-
on
Add anON
clause to the previousJOIN
.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!
- See Also:
-
on
@NotNull @CheckReturnValue @Support @PlainSQL @NotNull SelectOnConditionStep<R> on(String sql, Object... bindings) Add anON
clause to the previousJOIN
.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!
-
on
@NotNull @CheckReturnValue @Support @PlainSQL @NotNull SelectOnConditionStep<R> on(String sql, QueryPart... parts) Add anON
clause to the previousJOIN
.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!
-
onKey
@NotNull @CheckReturnValue @Support @NotNull SelectOnConditionStep<R> onKey() throws DataAccessExceptionJoin the previous table on a non-ambiguous foreign key relationship between the two joined tables.See
TableOnStep.onKey(ForeignKey)
for examples.- Throws:
DataAccessException
- If there is no non-ambiguous key definition known to jOOQ. Please note that if you evolve your schema, a previously non-ambiguousON KEY
clause can suddenly become ambiguous on an existing query, so use this clause with care.- See Also:
-
onKey
@NotNull @CheckReturnValue @Support @NotNull SelectOnConditionStep<R> onKey(TableField<?, ?>... keyFields) throws DataAccessExceptionJoin the previous table on a non-ambiguous foreign key relationship between the two joined tables.See
TableOnStep.onKey(ForeignKey)
for examples.- Throws:
DataAccessException
- If there is no non-ambiguous key definition known to jOOQ. Please note that if you evolve your schema, a previously non-ambiguousON KEY
clause can suddenly become ambiguous on an existing query, so use this clause with care.- See Also:
-
onKey
Join the table on a non-ambiguous foreign key relationship between the two joined tables.See
TableOnStep.onKey(ForeignKey)
for examples.- See Also:
-
using
Join the previous table with theUSING(column [, column…])
syntax.If this is not supported by your RDBMS, then jOOQ will try to emulate this behaviour using the information provided in this query.
-
using
@NotNull @CheckReturnValue @Support @NotNull SelectJoinStep<R> using(Collection<? extends Field<?>> fields) Join the previous table with theUSING(column [, column…])
syntax.If this is not supported by your RDBMS, then jOOQ will try to emulate this behaviour using the information provided in this query.
-