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 DivideByOnConditionStep | on(Condition condition)
Deprecated
as a consequence of
Add a division condition to the Condition being deprecated.
DIVIDE BY clause, connecting
them with each other with Operator#AND.
|
| public @NotNull DivideByOnConditionStep | on(Condition... conditions)
Deprecated
as a consequence of
Add a division condition to the Condition being deprecated.
DIVIDE BY clause, connecting
them with each other with Operator#AND.
|
| public @NotNull DivideByOnConditionStep | |
| public @NotNull DivideByOnConditionStep | |
| public @NotNull DivideByOnConditionStep | |
| public @NotNull DivideByOnConditionStep | |
| public @NotNull DivideByOnConditionStep |
| on | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep on(Condition condition)
Deprecated as a consequence of Add a division condition to the | |
| on | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep on(Condition... conditions)
Deprecated as a consequence of Add a division condition to the | |
| on | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep on(Field<Boolean> condition)
Deprecated as a consequence of Add a division condition to the | |
| on | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep on(SQL sql) Add a division condition to the 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 DivideByOnConditionStep on(String sql) Add a division condition to the 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 DivideByOnConditionStep on(String sql, Object... bindings) Add a division condition to the 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 DivideByOnConditionStep on(String sql, QueryPart... parts) Add a division condition to the 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! | |