Module org.jooq

Package org.jooq

Interface DeleteConditionStep<R extends Record>

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 the Delete's DSL API.

Example:

 DSLContext create = DSL.using(configuration);

 create.delete(table)
       .where(field1.greaterThan(100))
       .execute();
 

Referencing 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:

• 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

Modifier and Type	Method	Description
@NotNull DeleteConditionStep<R>	and(Boolean condition)	Deprecated. - 3.8.0 - [#4763] - Use and(Condition) (typically with DSL.trueCondition(), DSL.falseCondition(), or DSL.noCondition() as the parameter) or and(Field) instead.
@NotNull DeleteConditionStep<R>	and(String sql)	Combine the currently assembled conditions with another one using the Operator.AND operator
@NotNull DeleteConditionStep<R>	and(String sql, Object... bindings)	Combine the currently assembled conditions with another one using the Operator.AND operator
@NotNull DeleteConditionStep<R>	and(String sql, QueryPart... parts)	Combine the currently assembled conditions with another one using the Operator.AND operator
@NotNull DeleteConditionStep<R>	and(Condition condition)	Combine the currently assembled conditions with another one using the Operator.AND operator
@NotNull DeleteConditionStep<R>	and(Field<Boolean> condition)	Combine the currently assembled conditions with another one using the Operator.AND operator
@NotNull DeleteConditionStep<R>	and(SQL sql)	Combine the currently assembled conditions with another one using the Operator.AND operator
@NotNull DeleteConditionStep<R>	andExists(Select<?> select)	Combine the currently assembled conditions with an EXISTS clause using the Operator.AND operator
@NotNull DeleteConditionStep<R>	andNot(Boolean condition)	Deprecated. - 3.8.0 - [#4763] - Use andNot(Condition) (typically with DSL.trueCondition(), DSL.falseCondition(), or DSL.noCondition() as the parameter) or andNot(Field) instead.
@NotNull DeleteConditionStep<R>	andNot(Condition condition)	Combine the currently assembled conditions with a negated other one using the Operator.AND operator
@NotNull DeleteConditionStep<R>	andNot(Field<Boolean> condition)	Combine the currently assembled conditions with a negated other one using the Operator.AND operator
@NotNull DeleteConditionStep<R>	andNotExists(Select<?> select)	Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.AND operator
@NotNull DeleteConditionStep<R>	or(Boolean condition)	Deprecated. - 3.8.0 - [#4763] - Use or(Condition) (typically with DSL.trueCondition(), DSL.falseCondition(), or DSL.noCondition() as the parameter) or or(Field) instead.
@NotNull DeleteConditionStep<R>	or(String sql)	Combine the currently assembled conditions with another one using the Operator.OR operator
@NotNull DeleteConditionStep<R>	or(String sql, Object... bindings)	Combine the currently assembled conditions with another one using the Operator.OR operator
@NotNull DeleteConditionStep<R>	or(String sql, QueryPart... parts)	Combine the currently assembled conditions with another one using the Operator.OR operator
@NotNull DeleteConditionStep<R>	or(Condition condition)	Combine the currently assembled conditions with another one using the Operator.OR operator
@NotNull DeleteConditionStep<R>	or(Field<Boolean> condition)	Combine the currently assembled conditions with another one using the Operator.OR operator
@NotNull DeleteConditionStep<R>	or(SQL sql)	Combine the currently assembled conditions with another one using the Operator.OR operator
@NotNull DeleteConditionStep<R>	orExists(Select<?> select)	Combine the currently assembled conditions with an EXISTS clause using the Operator.OR operator
@NotNull DeleteConditionStep<R>	orNot(Boolean condition)	Deprecated. - 3.8.0 - [#4763] - Use orNot(Condition) (typically with DSL.trueCondition(), DSL.falseCondition(), or DSL.noCondition() as the parameter) or orNot(Field) instead.
@NotNull DeleteConditionStep<R>	orNot(Condition condition)	Combine the currently assembled conditions with a negated other one using the Operator.OR operator
@NotNull DeleteConditionStep<R>	orNot(Field<Boolean> condition)	Combine the currently assembled conditions with a negated other one using the Operator.OR operator
@NotNull DeleteConditionStep<R>	orNotExists(Select<?> select)	Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.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.reactivestreams.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

Methods inherited from interface org.jooq.QueryPart

equals, hashCode, toString

Method Detail

and

@NotNull
@Support
@NotNull DeleteConditionStep<R> and(Condition condition)

Combine the currently assembled conditions with another one using the Operator.AND operator

and

@NotNull
@Support
@NotNull DeleteConditionStep<R> and(Field<Boolean> condition)

Combine the currently assembled conditions with another one using the Operator.AND operator

and

@Deprecated
@NotNull
@Support
@NotNull DeleteConditionStep<R> and(Boolean condition)

Deprecated.

- 3.8.0 - [#4763] - Use and(Condition) (typically with DSL.trueCondition(), DSL.falseCondition(), or DSL.noCondition() as the parameter) 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.

Combine the currently assembled conditions with another one using the Operator.AND operator

and

@NotNull
@Support
@PlainSQL
@NotNull 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. 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

@NotNull
@Support
@PlainSQL
@NotNull 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. 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

@NotNull
@Support
@PlainSQL
@NotNull 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. 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, Object...), DSL.sql(String, Object...), SQL

and

@NotNull
@Support
@PlainSQL
@NotNull 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. 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, QueryPart...), DSL.sql(String, QueryPart...), SQL

andNot

@NotNull
@Support
@NotNull DeleteConditionStep<R> andNot(Condition condition)

Combine the currently assembled conditions with a negated other one using the Operator.AND operator

andNot

@NotNull
@Support
@NotNull DeleteConditionStep<R> andNot(Field<Boolean> condition)

Combine the currently assembled conditions with a negated other one using the Operator.AND operator

andNot

@Deprecated
@NotNull
@Support
@NotNull DeleteConditionStep<R> andNot(Boolean condition)

Deprecated.

- 3.8.0 - [#4763] - Use andNot(Condition) (typically with DSL.trueCondition(), DSL.falseCondition(), or DSL.noCondition() as the parameter) 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.

Combine the currently assembled conditions with a negated other one using the Operator.AND operator

andExists

@NotNull
@Support
@NotNull DeleteConditionStep<R> andExists(Select<?> select)

Combine the currently assembled conditions with an EXISTS clause using the Operator.AND operator

andNotExists

@NotNull
@Support
@NotNull DeleteConditionStep<R> andNotExists(Select<?> select)

Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.AND operator

or

@NotNull
@Support
@NotNull DeleteConditionStep<R> or(Condition condition)

Combine the currently assembled conditions with another one using the Operator.OR operator

or

@NotNull
@Support
@NotNull DeleteConditionStep<R> or(Field<Boolean> condition)

Combine the currently assembled conditions with another one using the Operator.OR operator

or

@Deprecated
@NotNull
@Support
@NotNull DeleteConditionStep<R> or(Boolean condition)

Deprecated.

- 3.8.0 - [#4763] - Use or(Condition) (typically with DSL.trueCondition(), DSL.falseCondition(), or DSL.noCondition() as the parameter) 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.

Combine the currently assembled conditions with another one using the Operator.OR operator

or

@NotNull
@Support
@PlainSQL
@NotNull 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. 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

@NotNull
@Support
@PlainSQL
@NotNull 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. 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

@NotNull
@Support
@PlainSQL
@NotNull 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. 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, Object...), DSL.sql(String, Object...), SQL

or

@NotNull
@Support
@PlainSQL
@NotNull 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. 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, QueryPart...), DSL.sql(String, QueryPart...), SQL

orNot

@NotNull
@Support
@NotNull DeleteConditionStep<R> orNot(Condition condition)

Combine the currently assembled conditions with a negated other one using the Operator.OR operator

orNot

@NotNull
@Support
@NotNull DeleteConditionStep<R> orNot(Field<Boolean> condition)

Combine the currently assembled conditions with a negated other one using the Operator.OR operator

orNot

@Deprecated
@NotNull
@Support
@NotNull DeleteConditionStep<R> orNot(Boolean condition)

Deprecated.

- 3.8.0 - [#4763] - Use orNot(Condition) (typically with DSL.trueCondition(), DSL.falseCondition(), or DSL.noCondition() as the parameter) 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.

Combine the currently assembled conditions with a negated other one using the Operator.OR operator

orExists

@NotNull
@Support
@NotNull DeleteConditionStep<R> orExists(Select<?> select)

Combine the currently assembled conditions with an EXISTS clause using the Operator.OR operator

orNotExists

@NotNull
@Support
@NotNull DeleteConditionStep<R> orNotExists(Select<?> select)

Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.OR operator