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
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:
| Modifier and Type | Method and Description |
|---|---|
| public @NotNull SelectOnConditionStep | on(Condition condition)
Deprecated
as a consequence of
Add an Condition being deprecated.
ON clause to the previous JOIN,
connecting them with each other with Operator#AND.
|
| public @NotNull SelectOnConditionStep | on(Condition... conditions)
Deprecated
as a consequence of
Add an Condition being deprecated.
ON clause to the previous JOIN,
connecting them with each other with Operator#AND.
|
| public @NotNull SelectOnConditionStep | |
| public @NotNull SelectOnConditionStep | |
| public @NotNull SelectOnConditionStep | |
| public @NotNull SelectOnConditionStep | |
| public @NotNull SelectOnConditionStep | |
| public @NotNull SelectOnConditionStep | onKey()
Join the previous table on a non-ambiguous foreign key relationship between the two joined tables. |
| public @NotNull SelectOnConditionStep | onKey(TableField<?, ?>... keyFields)
Deprecated
as a consequence of
Join the previous table on a non-ambiguous foreign key relationship
between the two joined tables.
TableField being deprecated.
|
| public @NotNull SelectOnConditionStep | onKey(ForeignKey<?, ?> key)
Join the table on a non-ambiguous foreign key relationship between the two joined tables. |
| public @NotNull SelectJoinStep | |
| public @NotNull SelectJoinStep | using(Collection<? extends Field<?>> fields)
Join the previous table with the |
| on | back to summary |
|---|---|
| public @NotNull SelectOnConditionStep Deprecated as a consequence of Add an
| |
| on | back to summary |
|---|---|
| public @NotNull SelectOnConditionStep Deprecated as a consequence of Add an
| |
| on | back to summary |
|---|---|
| public @NotNull SelectOnConditionStep Deprecated as a consequence of Add an
| |
| on | back to summary |
|---|---|
| public @NotNull SelectOnConditionStep Add an 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 | back to summary |
|---|---|
| public @NotNull SelectOnConditionStep Add an 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 | back to summary |
|---|---|
| public @NotNull SelectOnConditionStep Add an 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 | back to summary |
|---|---|
| public @NotNull SelectOnConditionStep Add an 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 | back to summary |
|---|---|
| public @NotNull SelectOnConditionStep Join the previous table on a non-ambiguous foreign key relationship between the two joined tables.
See
| |
| onKey | back to summary |
|---|---|
| public @NotNull SelectOnConditionStep Deprecated as a consequence of Join the previous table on a non-ambiguous foreign key relationship between the two joined tables.
See
| |
| onKey | back to summary |
|---|---|
| public @NotNull SelectOnConditionStep Join the table on a non-ambiguous foreign key relationship between the two joined tables.
See
| |
| using | back to summary |
|---|---|
| public @NotNull SelectJoinStep Deprecated as a consequence of Join the previous table with the If this is not supported by your RDBMS, then jOOQ will try to emulate this behaviour using the information provided in this query.
| |
| using | back to summary |
|---|---|
| public @NotNull SelectJoinStep Join the previous table with the If this is not supported by your RDBMS, then jOOQ will try to emulate this behaviour using the information provided in this query.
| |