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 | and(Condition condition)
Deprecated
as a consequence of
Combine the currently assembled conditions with another one using the
Condition being deprecated.
Operator#AND operator.
|
| public @NotNull DivideByOnConditionStep | and(Field<Boolean> condition)
Deprecated
as a consequence of
Combine the currently assembled conditions with another one using the
Field being deprecated.
Operator#AND operator.
|
| public @NotNull DivideByOnConditionStep | and(SQL sql)
Combine the currently assembled conditions with another one using the
|
| public @NotNull DivideByOnConditionStep | and(String sql)
Combine the currently assembled conditions with another one using the
|
| public @NotNull DivideByOnConditionStep | and(String sql, Object... bindings)
Combine the currently assembled conditions with another one using the
|
| public @NotNull DivideByOnConditionStep | and(String sql, QueryPart... parts)
Combine the currently assembled conditions with another one using the
|
| public @NotNull DivideByOnConditionStep | andExists(Select<?> select)
Combine the currently assembled conditions with an |
| public @NotNull DivideByOnConditionStep | andNot(Condition condition)
Deprecated
as a consequence of
Combine the currently assembled conditions with a negated other one using
the Condition being deprecated.
Operator#AND operator.
|
| public @NotNull DivideByOnConditionStep | andNot(Field<Boolean> condition)
Deprecated
as a consequence of
Combine the currently assembled conditions with a negated other one using
the Field being deprecated.
Operator#AND operator.
|
| public @NotNull DivideByOnConditionStep | andNotExists(Select<?> select)
Combine the currently assembled conditions with a |
| public @NotNull DivideByOnConditionStep | or(Condition condition)
Deprecated
as a consequence of
Combine the currently assembled conditions with another one using the
Condition being deprecated.
Operator#OR operator.
|
| public @NotNull DivideByOnConditionStep | or(Field<Boolean> condition)
Deprecated
as a consequence of
Combine the currently assembled conditions with another one using the
Field being deprecated.
Operator#OR operator.
|
| public @NotNull DivideByOnConditionStep | or(SQL sql)
Combine the currently assembled conditions with another one using the
|
| public @NotNull DivideByOnConditionStep | or(String sql)
Combine the currently assembled conditions with another one using the
|
| public @NotNull DivideByOnConditionStep | or(String sql, Object... bindings)
Combine the currently assembled conditions with another one using the
|
| public @NotNull DivideByOnConditionStep | or(String sql, QueryPart... parts)
Combine the currently assembled conditions with another one using the
|
| public @NotNull DivideByOnConditionStep | orExists(Select<?> select)
Combine the currently assembled conditions with an |
| public @NotNull DivideByOnConditionStep | orNot(Condition condition)
Deprecated
as a consequence of
Combine the currently assembled conditions with a negated other one using
the Condition being deprecated.
Operator#OR operator.
|
| public @NotNull DivideByOnConditionStep | orNot(Field<Boolean> condition)
Deprecated
as a consequence of
Combine the currently assembled conditions with a negated other one using
the Field being deprecated.
Operator#OR operator.
|
| public @NotNull DivideByOnConditionStep | orNotExists(Select<?> select)
Combine the currently assembled conditions with a |
| and | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep and(Condition condition)
Deprecated as a consequence of Combine the currently assembled conditions with another one using the
| |
| and | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep and(Field<Boolean> condition)
Deprecated as a consequence of Combine the currently assembled conditions with another one using the
| |
| and | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep and(SQL sql) Combine the currently assembled conditions with another one using 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! | |
| and | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep and(String sql) Combine the currently assembled conditions with another one using 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! | |
| and | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep and(String sql, Object... bindings) Combine the currently assembled conditions with another one using 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! | |
| and | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep and(String sql, QueryPart... parts) Combine the currently assembled conditions with another one using 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! | |
| andExists | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep andExists(Select<?> select) Combine the currently assembled conditions with an | |
| andNot | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep andNot(Condition condition)
Deprecated as a consequence of Combine the currently assembled conditions with a negated other one using
the | |
| andNot | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep andNot(Field<Boolean> condition)
Deprecated as a consequence of Combine the currently assembled conditions with a negated other one using
the | |
| andNotExists | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep andNotExists(Select<?> select) Combine the currently assembled conditions with a | |
| or | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep or(Condition condition)
Deprecated as a consequence of Combine the currently assembled conditions with another one using the
| |
| or | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep or(Field<Boolean> condition)
Deprecated as a consequence of Combine the currently assembled conditions with another one using the
| |
| or | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep or(SQL sql) Combine the currently assembled conditions with another one using 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! | |
| or | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep or(String sql) Combine the currently assembled conditions with another one using 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! | |
| or | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep or(String sql, Object... bindings) Combine the currently assembled conditions with another one using 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! | |
| or | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep or(String sql, QueryPart... parts) Combine the currently assembled conditions with another one using 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! | |
| orExists | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep orExists(Select<?> select) Combine the currently assembled conditions with an | |
| orNot | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep orNot(Condition condition)
Deprecated as a consequence of Combine the currently assembled conditions with a negated other one using
the | |
| orNot | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep orNot(Field<Boolean> condition)
Deprecated as a consequence of Combine the currently assembled conditions with a negated other one using
the | |
| orNotExists | back to summary |
|---|---|
| public @NotNull DivideByOnConditionStep orNotExists(Select<?> select) Combine the currently assembled conditions with a | |