Deprecated
as a consequence of DeleteOrderByStep being deprecated. See corresponding docs for further information.
Delete's DSL API.
Example:
DSLContext create = DSL.using(configuration);
create.delete(table)
.where(field1.greaterThan(100))
.execute();
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 DeleteConditionStep | and(Condition condition)
Deprecated
as a consequence of
Combine the currently assembled conditions with another one using the
Condition and DeleteConditionStep being deprecated.
Operator#AND operator
|
| public @NotNull DeleteConditionStep | and(Field<Boolean> condition)
Deprecated
as a consequence of
Combine the currently assembled conditions with another one using the
Field and DeleteConditionStep being deprecated.
Operator#AND operator
|
| public @NotNull DeleteConditionStep | and(SQL sql)
Deprecated
as a consequence of
Combine the currently assembled conditions with another one using the
DeleteConditionStep being deprecated.
Operator#AND operatorNote When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. |
| public @NotNull DeleteConditionStep | and(String sql)
Deprecated
as a consequence of
Combine the currently assembled conditions with another one using the
DeleteConditionStep being deprecated.
Operator#AND operatorNote When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. |
| public @NotNull DeleteConditionStep | and(String sql, Object... bindings)
Deprecated
as a consequence of
Combine the currently assembled conditions with another one using the
DeleteConditionStep being deprecated.
Operator#AND operatorNote When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. |
| public @NotNull DeleteConditionStep | and(String sql, QueryPart... parts)
Deprecated
as a consequence of
Combine the currently assembled conditions with another one using the
DeleteConditionStep being deprecated.
Operator#AND operatorNote When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. |
| public @NotNull DeleteConditionStep | andExists(Select<?> select)
Deprecated
as a consequence of
Combine the currently assembled conditions with an EXISTS clause using
the DeleteConditionStep being deprecated.
Operator#AND operator
|
| public @NotNull DeleteConditionStep | andNot(Condition condition)
Deprecated
as a consequence of
Combine the currently assembled conditions with a negated other one using
the Condition and DeleteConditionStep being deprecated.
Operator#AND operator
|
| public @NotNull DeleteConditionStep | andNot(Field<Boolean> condition)
Deprecated
as a consequence of
Combine the currently assembled conditions with a negated other one using
the Field and DeleteConditionStep being deprecated.
Operator#AND operator
|
| public @NotNull DeleteConditionStep | andNotExists(Select<?> select)
Deprecated
as a consequence of
Combine the currently assembled conditions with a NOT EXISTS clause using
the DeleteConditionStep being deprecated.
Operator#AND operator
|
| public @NotNull DeleteConditionStep | or(Condition condition)
Deprecated
as a consequence of
Combine the currently assembled conditions with another one using the
Condition and DeleteConditionStep being deprecated.
Operator#OR operator
|
| public @NotNull DeleteConditionStep | or(Field<Boolean> condition)
Deprecated
as a consequence of
Combine the currently assembled conditions with another one using the
Field and DeleteConditionStep being deprecated.
Operator#OR operator
|
| public @NotNull DeleteConditionStep | or(SQL sql)
Deprecated
as a consequence of
Combine the currently assembled conditions with another one using the
DeleteConditionStep being deprecated.
Operator#OR operatorNote When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. |
| public @NotNull DeleteConditionStep | or(String sql)
Deprecated
as a consequence of
Combine the currently assembled conditions with another one using the
DeleteConditionStep being deprecated.
Operator#OR operatorNote When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. |
| public @NotNull DeleteConditionStep | or(String sql, Object... bindings)
Deprecated
as a consequence of
Combine the currently assembled conditions with another one using the
DeleteConditionStep being deprecated.
Operator#OR operatorNote When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. |
| public @NotNull DeleteConditionStep | or(String sql, QueryPart... parts)
Deprecated
as a consequence of
Combine the currently assembled conditions with another one using the
DeleteConditionStep being deprecated.
Operator#OR operatorNote When inserting plain SQL into jOOQ objects, you must guarantee syntax integrity. |
| public @NotNull DeleteConditionStep | orExists(Select<?> select)
Deprecated
as a consequence of
Combine the currently assembled conditions with an EXISTS clause using
the DeleteConditionStep being deprecated.
Operator#OR operator
|
| public @NotNull DeleteConditionStep | orNot(Condition condition)
Deprecated
as a consequence of
Combine the currently assembled conditions with a negated other one using
the Condition and DeleteConditionStep being deprecated.
Operator#OR operator
|
| public @NotNull DeleteConditionStep | orNot(Field<Boolean> condition)
Deprecated
as a consequence of
Combine the currently assembled conditions with a negated other one using
the Field and DeleteConditionStep being deprecated.
Operator#OR operator
|
| public @NotNull DeleteConditionStep | orNotExists(Select<?> select)
Deprecated
as a consequence of
Combine the currently assembled conditions with a NOT EXISTS clause using
the DeleteConditionStep being deprecated.
Operator#OR operator
|
| and | back to summary |
|---|---|
| public @NotNull DeleteConditionStep Deprecated as a consequence of Combine the currently assembled conditions with another one using the
| |
| and | back to summary |
|---|---|
| public @NotNull DeleteConditionStep Deprecated as a consequence of Combine the currently assembled conditions with another one using the
| |
| and | back to summary |
|---|---|
| public @NotNull DeleteConditionStep Deprecated as a consequence of 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 DeleteConditionStep Deprecated as a consequence of 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 DeleteConditionStep Deprecated as a consequence of 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 DeleteConditionStep Deprecated as a consequence of 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 DeleteConditionStep Deprecated as a consequence of Combine the currently assembled conditions with an EXISTS clause using
the
| |
| andNot | back to summary |
|---|---|
| public @NotNull DeleteConditionStep Deprecated as a consequence of Combine the currently assembled conditions with a negated other one using
the
| |
| andNot | back to summary |
|---|---|
| public @NotNull DeleteConditionStep Deprecated as a consequence of Combine the currently assembled conditions with a negated other one using
the
| |
| andNotExists | back to summary |
|---|---|
| public @NotNull DeleteConditionStep Deprecated as a consequence of Combine the currently assembled conditions with a NOT EXISTS clause using
the
| |
| or | back to summary |
|---|---|
| public @NotNull DeleteConditionStep Deprecated as a consequence of Combine the currently assembled conditions with another one using the
| |
| or | back to summary |
|---|---|
| public @NotNull DeleteConditionStep Deprecated as a consequence of Combine the currently assembled conditions with another one using the
| |
| or | back to summary |
|---|---|
| public @NotNull DeleteConditionStep Deprecated as a consequence of 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 DeleteConditionStep Deprecated as a consequence of 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 DeleteConditionStep Deprecated as a consequence of 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 DeleteConditionStep Deprecated as a consequence of 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 DeleteConditionStep Deprecated as a consequence of Combine the currently assembled conditions with an EXISTS clause using
the
| |
| orNot | back to summary |
|---|---|
| public @NotNull DeleteConditionStep Deprecated as a consequence of Combine the currently assembled conditions with a negated other one using
the
| |
| orNot | back to summary |
|---|---|
| public @NotNull DeleteConditionStep Deprecated as a consequence of Combine the currently assembled conditions with a negated other one using
the
| |
| orNotExists | back to summary |
|---|---|
| public @NotNull DeleteConditionStep Deprecated as a consequence of Combine the currently assembled conditions with a NOT EXISTS clause using
the
| |