public interface DeleteConditionStep<R extends Record> extends DeleteReturningStep<R>
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 |
---|---|
DeleteConditionStep<R> |
and(Boolean condition)
Deprecated.
- 3.8.0 - [#4763] - Use
and(Condition) or
and(Field) instead. Due to ambiguity between calling
this method using Field.equals(Object) argument, vs.
calling the other method via a Field.equal(Object)
argument, this method will be removed in the future. |
DeleteConditionStep<R> |
and(Condition condition)
Combine the currently assembled conditions with another one using the
Operator.AND operator |
DeleteConditionStep<R> |
and(Field<Boolean> condition)
Combine the currently assembled conditions with another one using the
Operator.AND operator |
DeleteConditionStep<R> |
and(SQL sql)
Combine the currently assembled conditions with another one using the
Operator.AND operator
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. |
DeleteConditionStep<R> |
and(String sql)
Combine the currently assembled conditions with another one using the
Operator.AND operator
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. |
DeleteConditionStep<R> |
and(String sql,
Object... bindings)
Combine the currently assembled conditions with another one using the
Operator.AND operator
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. |
DeleteConditionStep<R> |
and(String sql,
QueryPart... parts)
Combine the currently assembled conditions with another one using the
Operator.AND operator
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. |
DeleteConditionStep<R> |
andExists(Select<?> select)
Combine the currently assembled conditions with an EXISTS clause using
the
Operator.AND operator |
DeleteConditionStep<R> |
andNot(Boolean condition)
Deprecated.
- 3.8.0 - [#4763] - Use
andNot(Condition) or
andNot(Field) instead. Due to ambiguity between
calling this method using Field.equals(Object)
argument, vs. calling the other method via a
Field.equal(Object) argument, this method will be
removed in the future. |
DeleteConditionStep<R> |
andNot(Condition condition)
Combine the currently assembled conditions with a negated other one using
the
Operator.AND operator |
DeleteConditionStep<R> |
andNot(Field<Boolean> condition)
Combine the currently assembled conditions with a negated other one using
the
Operator.AND operator |
DeleteConditionStep<R> |
andNotExists(Select<?> select)
Combine the currently assembled conditions with a NOT EXISTS clause using
the
Operator.AND operator |
DeleteConditionStep<R> |
or(Boolean condition)
Deprecated.
- 3.8.0 - [#4763] - Use
or(Condition) or
or(Field) instead. Due to ambiguity between calling
this method using Field.equals(Object) argument, vs.
calling the other method via a Field.equal(Object)
argument, this method will be removed in the future. |
DeleteConditionStep<R> |
or(Condition condition)
Combine the currently assembled conditions with another one using the
Operator.OR operator |
DeleteConditionStep<R> |
or(Field<Boolean> condition)
Combine the currently assembled conditions with another one using the
Operator.OR operator |
DeleteConditionStep<R> |
or(SQL sql)
Combine the currently assembled conditions with another one using the
Operator.OR operator
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. |
DeleteConditionStep<R> |
or(String sql)
Combine the currently assembled conditions with another one using the
Operator.OR operator
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. |
DeleteConditionStep<R> |
or(String sql,
Object... bindings)
Combine the currently assembled conditions with another one using the
Operator.OR operator
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. |
DeleteConditionStep<R> |
or(String sql,
QueryPart... parts)
Combine the currently assembled conditions with another one using the
Operator.OR operator
NOTE: When inserting plain SQL into jOOQ objects, you must
guarantee syntax integrity. |
DeleteConditionStep<R> |
orExists(Select<?> select)
Combine the currently assembled conditions with an EXISTS clause using
the
Operator.OR operator |
DeleteConditionStep<R> |
orNot(Boolean condition)
Deprecated.
- 3.8.0 - [#4763] - Use
orNot(Condition) or
orNot(Field) instead. Due to ambiguity between
calling this method using Field.equals(Object)
argument, vs. calling the other method via a
Field.equal(Object) argument, this method will be
removed in the future. |
DeleteConditionStep<R> |
orNot(Condition condition)
Combine the currently assembled conditions with a negated other one using
the
Operator.OR operator |
DeleteConditionStep<R> |
orNot(Field<Boolean> condition)
Combine the currently assembled conditions with a negated other one using
the
Operator.OR operator |
DeleteConditionStep<R> |
orNotExists(Select<?> select)
Combine the currently assembled conditions with a NOT EXISTS clause using
the
Operator.OR operator |
returning, returning, returning, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult, returningResult
bind, bind, cancel, close, execute, executeAsync, executeAsync, getBindValues, getParam, getParams, getSQL, getSQL, getSQL, isExecutable, keepStatement, queryTimeout
attach, configuration, detach
@Support DeleteConditionStep<R> and(Condition condition)
Operator.AND
operator@Support DeleteConditionStep<R> and(Field<Boolean> condition)
Operator.AND
operator@Deprecated @Support DeleteConditionStep<R> and(Boolean condition)
and(Condition)
or
and(Field)
instead. Due to ambiguity between calling
this method using Field.equals(Object)
argument, vs.
calling the other method via a Field.equal(Object)
argument, this method will be removed in the future.Operator.AND
operator@Support @PlainSQL DeleteConditionStep<R> and(SQL sql)
Operator.AND
operator
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!
DSL.condition(SQL)
,
SQL
@Support @PlainSQL DeleteConditionStep<R> and(String sql)
Operator.AND
operator
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!
DSL.condition(String)
,
SQL
@Support @PlainSQL DeleteConditionStep<R> and(String sql, Object... bindings)
Operator.AND
operator
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!
@Support @PlainSQL DeleteConditionStep<R> and(String sql, QueryPart... parts)
Operator.AND
operator
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!
@Support DeleteConditionStep<R> andNot(Condition condition)
Operator.AND
operator@Support DeleteConditionStep<R> andNot(Field<Boolean> condition)
Operator.AND
operator@Deprecated @Support DeleteConditionStep<R> andNot(Boolean condition)
andNot(Condition)
or
andNot(Field)
instead. Due to ambiguity between
calling this method using Field.equals(Object)
argument, vs. calling the other method via a
Field.equal(Object)
argument, this method will be
removed in the future.Operator.AND
operator@Support DeleteConditionStep<R> andExists(Select<?> select)
Operator.AND
operatorDeleteConditionStep<R> andNotExists(Select<?> select)
Operator.AND
operator@Support DeleteConditionStep<R> or(Condition condition)
Operator.OR
operator@Support DeleteConditionStep<R> or(Field<Boolean> condition)
Operator.OR
operator@Deprecated @Support DeleteConditionStep<R> or(Boolean condition)
or(Condition)
or
or(Field)
instead. Due to ambiguity between calling
this method using Field.equals(Object)
argument, vs.
calling the other method via a Field.equal(Object)
argument, this method will be removed in the future.Operator.OR
operator@Support @PlainSQL DeleteConditionStep<R> or(SQL sql)
Operator.OR
operator
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!
DSL.condition(SQL)
,
SQL
@Support @PlainSQL DeleteConditionStep<R> or(String sql)
Operator.OR
operator
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!
DSL.condition(String)
,
SQL
@Support @PlainSQL DeleteConditionStep<R> or(String sql, Object... bindings)
Operator.OR
operator
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!
@Support @PlainSQL DeleteConditionStep<R> or(String sql, QueryPart... parts)
Operator.OR
operator
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!
@Support DeleteConditionStep<R> orNot(Condition condition)
Operator.OR
operator@Support DeleteConditionStep<R> orNot(Field<Boolean> condition)
Operator.OR
operator@Deprecated @Support DeleteConditionStep<R> orNot(Boolean condition)
orNot(Condition)
or
orNot(Field)
instead. Due to ambiguity between
calling this method using Field.equals(Object)
argument, vs. calling the other method via a
Field.equal(Object)
argument, this method will be
removed in the future.Operator.OR
operator@Support DeleteConditionStep<R> orExists(Select<?> select)
Operator.OR
operator@Support DeleteConditionStep<R> orNotExists(Select<?> select)
Operator.OR
operatorCopyright © 2019. All rights reserved.