-
- All Superinterfaces:
Attachable
,AutoCloseable
,Delete<R>
,DeleteFinalStep<R>
,DeleteLimitStep<R>
,DeleteOrderByStep<R>
,DeleteReturningStep<R>
,Flow.Publisher<Integer>
,org.reactivestreams.Publisher<Integer>
,Query
,QueryPart
,RowCountQuery
,Serializable
,Statement
public interface DeleteConditionStep<R extends Record> extends DeleteOrderByStep<R>
This type is used for theDelete
's DSL API.Example:
DSLContext create = DSL.using(configuration); create.delete(table) .where(field1.greaterThan(100)) .execute();
Referencing
XYZ*Step
types directly from client codeIt 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:- They're operating on mutable implementations (as of jOOQ 3.x)
- They're less composable and not easy to get right when dynamic SQL gets complex
- They're less readable
- They might have binary incompatible changes between minor releases
- Author:
- Lukas Eder
-
-
Method Summary
All Methods Instance Methods Abstract Methods Deprecated Methods Modifier and Type Method Description DeleteConditionStep<R>
and(Boolean condition)
Deprecated.- 3.8.0 - [#4763] - Useand(Condition)
(typically withDSL.trueCondition()
,DSL.falseCondition()
, orDSL.noCondition()
as the parameter) orand(Field)
instead.DeleteConditionStep<R>
and(String sql)
Combine the currently assembled conditions with another one using theOperator.AND
operatorDeleteConditionStep<R>
and(String sql, Object... bindings)
Combine the currently assembled conditions with another one using theOperator.AND
operatorDeleteConditionStep<R>
and(String sql, QueryPart... parts)
Combine the currently assembled conditions with another one using theOperator.AND
operatorDeleteConditionStep<R>
and(Condition condition)
Combine the currently assembled conditions with another one using theOperator.AND
operatorDeleteConditionStep<R>
and(Field<Boolean> condition)
Combine the currently assembled conditions with another one using theOperator.AND
operatorDeleteConditionStep<R>
and(SQL sql)
Combine the currently assembled conditions with another one using theOperator.AND
operatorDeleteConditionStep<R>
andExists(Select<?> select)
Combine the currently assembled conditions with an EXISTS clause using theOperator.AND
operatorDeleteConditionStep<R>
andNot(Boolean condition)
Deprecated.- 3.8.0 - [#4763] - UseandNot(Condition)
(typically withDSL.trueCondition()
,DSL.falseCondition()
, orDSL.noCondition()
as the parameter) orandNot(Field)
instead.DeleteConditionStep<R>
andNot(Condition condition)
Combine the currently assembled conditions with a negated other one using theOperator.AND
operatorDeleteConditionStep<R>
andNot(Field<Boolean> condition)
Combine the currently assembled conditions with a negated other one using theOperator.AND
operatorDeleteConditionStep<R>
andNotExists(Select<?> select)
Combine the currently assembled conditions with a NOT EXISTS clause using theOperator.AND
operatorDeleteConditionStep<R>
or(Boolean condition)
Deprecated.- 3.8.0 - [#4763] - Useor(Condition)
(typically withDSL.trueCondition()
,DSL.falseCondition()
, orDSL.noCondition()
as the parameter) oror(Field)
instead.DeleteConditionStep<R>
or(String sql)
Combine the currently assembled conditions with another one using theOperator.OR
operatorDeleteConditionStep<R>
or(String sql, Object... bindings)
Combine the currently assembled conditions with another one using theOperator.OR
operatorDeleteConditionStep<R>
or(String sql, QueryPart... parts)
Combine the currently assembled conditions with another one using theOperator.OR
operatorDeleteConditionStep<R>
or(Condition condition)
Combine the currently assembled conditions with another one using theOperator.OR
operatorDeleteConditionStep<R>
or(Field<Boolean> condition)
Combine the currently assembled conditions with another one using theOperator.OR
operatorDeleteConditionStep<R>
or(SQL sql)
Combine the currently assembled conditions with another one using theOperator.OR
operatorDeleteConditionStep<R>
orExists(Select<?> select)
Combine the currently assembled conditions with an EXISTS clause using theOperator.OR
operatorDeleteConditionStep<R>
orNot(Boolean condition)
Deprecated.- 3.8.0 - [#4763] - UseorNot(Condition)
(typically withDSL.trueCondition()
,DSL.falseCondition()
, orDSL.noCondition()
as the parameter) ororNot(Field)
instead.DeleteConditionStep<R>
orNot(Condition condition)
Combine the currently assembled conditions with a negated other one using theOperator.OR
operatorDeleteConditionStep<R>
orNot(Field<Boolean> condition)
Combine the currently assembled conditions with a negated other one using theOperator.OR
operatorDeleteConditionStep<R>
orNotExists(Select<?> select)
Combine the currently assembled conditions with a NOT EXISTS clause using theOperator.OR
operator-
Methods inherited from interface org.jooq.Attachable
attach, configuration, detach
-
Methods inherited from interface org.jooq.DeleteLimitStep
limit, limit
-
Methods inherited from interface org.jooq.DeleteOrderByStep
orderBy, orderBy, orderBy
-
Methods inherited from interface org.jooq.DeleteReturningStep
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
-
Methods inherited from interface java.util.concurrent.Flow.Publisher
subscribe
-
Methods inherited from interface org.jooq.Query
bind, bind, cancel, close, execute, executeAsync, executeAsync, getBindValues, getParam, getParams, getSQL, getSQL, getSQL, isExecutable, keepStatement, poolable, queryTimeout
-
-
-
-
Method Detail
-
and
@Support DeleteConditionStep<R> and(Condition condition)
Combine the currently assembled conditions with another one using theOperator.AND
operator
-
and
@Support DeleteConditionStep<R> and(Field<Boolean> condition)
Combine the currently assembled conditions with another one using theOperator.AND
operator
-
and
@Deprecated @Support DeleteConditionStep<R> and(Boolean condition)
Deprecated.- 3.8.0 - [#4763] - Useand(Condition)
(typically withDSL.trueCondition()
,DSL.falseCondition()
, orDSL.noCondition()
as the parameter) orand(Field)
instead. Due to ambiguity between calling this method usingField.equals(Object)
argument, vs. calling the other method via aField.equal(Object)
argument, this method will be removed in the future.Combine the currently assembled conditions with another one using theOperator.AND
operator
-
and
@Support @PlainSQL DeleteConditionStep<R> and(SQL sql)
Combine the currently assembled conditions with another one using theOperator.AND
operatorNOTE: 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!
- See Also:
DSL.condition(SQL)
,SQL
-
and
@Support @PlainSQL DeleteConditionStep<R> and(String sql)
Combine the currently assembled conditions with another one using theOperator.AND
operatorNOTE: 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!
- See Also:
DSL.condition(String)
,SQL
-
and
@Support @PlainSQL DeleteConditionStep<R> and(String sql, Object... bindings)
Combine the currently assembled conditions with another one using theOperator.AND
operatorNOTE: 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
@Support @PlainSQL DeleteConditionStep<R> and(String sql, QueryPart... parts)
Combine the currently assembled conditions with another one using theOperator.AND
operatorNOTE: 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!
-
andNot
@Support DeleteConditionStep<R> andNot(Condition condition)
Combine the currently assembled conditions with a negated other one using theOperator.AND
operator
-
andNot
@Support DeleteConditionStep<R> andNot(Field<Boolean> condition)
Combine the currently assembled conditions with a negated other one using theOperator.AND
operator
-
andNot
@Deprecated @Support DeleteConditionStep<R> andNot(Boolean condition)
Deprecated.- 3.8.0 - [#4763] - UseandNot(Condition)
(typically withDSL.trueCondition()
,DSL.falseCondition()
, orDSL.noCondition()
as the parameter) orandNot(Field)
instead. Due to ambiguity between calling this method usingField.equals(Object)
argument, vs. calling the other method via aField.equal(Object)
argument, this method will be removed in the future.Combine the currently assembled conditions with a negated other one using theOperator.AND
operator
-
andExists
@Support DeleteConditionStep<R> andExists(Select<?> select)
Combine the currently assembled conditions with an EXISTS clause using theOperator.AND
operator
-
andNotExists
DeleteConditionStep<R> andNotExists(Select<?> select)
Combine the currently assembled conditions with a NOT EXISTS clause using theOperator.AND
operator
-
or
@Support DeleteConditionStep<R> or(Condition condition)
Combine the currently assembled conditions with another one using theOperator.OR
operator
-
or
@Support DeleteConditionStep<R> or(Field<Boolean> condition)
Combine the currently assembled conditions with another one using theOperator.OR
operator
-
or
@Deprecated @Support DeleteConditionStep<R> or(Boolean condition)
Deprecated.- 3.8.0 - [#4763] - Useor(Condition)
(typically withDSL.trueCondition()
,DSL.falseCondition()
, orDSL.noCondition()
as the parameter) oror(Field)
instead. Due to ambiguity between calling this method usingField.equals(Object)
argument, vs. calling the other method via aField.equal(Object)
argument, this method will be removed in the future.Combine the currently assembled conditions with another one using theOperator.OR
operator
-
or
@Support @PlainSQL DeleteConditionStep<R> or(SQL sql)
Combine the currently assembled conditions with another one using theOperator.OR
operatorNOTE: 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!
- See Also:
DSL.condition(SQL)
,SQL
-
or
@Support @PlainSQL DeleteConditionStep<R> or(String sql)
Combine the currently assembled conditions with another one using theOperator.OR
operatorNOTE: 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!
- See Also:
DSL.condition(String)
,SQL
-
or
@Support @PlainSQL DeleteConditionStep<R> or(String sql, Object... bindings)
Combine the currently assembled conditions with another one using theOperator.OR
operatorNOTE: 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
@Support @PlainSQL DeleteConditionStep<R> or(String sql, QueryPart... parts)
Combine the currently assembled conditions with another one using theOperator.OR
operatorNOTE: 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!
-
orNot
@Support DeleteConditionStep<R> orNot(Condition condition)
Combine the currently assembled conditions with a negated other one using theOperator.OR
operator
-
orNot
@Support DeleteConditionStep<R> orNot(Field<Boolean> condition)
Combine the currently assembled conditions with a negated other one using theOperator.OR
operator
-
orNot
@Deprecated @Support DeleteConditionStep<R> orNot(Boolean condition)
Deprecated.- 3.8.0 - [#4763] - UseorNot(Condition)
(typically withDSL.trueCondition()
,DSL.falseCondition()
, orDSL.noCondition()
as the parameter) ororNot(Field)
instead. Due to ambiguity between calling this method usingField.equals(Object)
argument, vs. calling the other method via aField.equal(Object)
argument, this method will be removed in the future.Combine the currently assembled conditions with a negated other one using theOperator.OR
operator
-
orExists
@Support DeleteConditionStep<R> orExists(Select<?> select)
Combine the currently assembled conditions with an EXISTS clause using theOperator.OR
operator
-
orNotExists
@Support DeleteConditionStep<R> orNotExists(Select<?> select)
Combine the currently assembled conditions with a NOT EXISTS clause using theOperator.OR
operator
-
-