org.jooq

Interface DeleteWhereStep<R extends Record>

All Superinterfaces:

Attachable, AutoCloseable, Delete<R>, DeleteFinalStep<R>, DeleteLimitStep<R>, DeleteOrderByStep<R>, DeleteReturningStep<R>, org.reactivestreams.Publisher<Integer>, Query, QueryPart, RowCountQuery, Serializable, Statement

All Known Subinterfaces:

DeleteUsingStep<R>

public interface DeleteWhereStep<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 and Description
DeleteConditionStep<R>	where(Boolean condition) Deprecated. - 3.8.0 - [#4763] - Use where(Condition) (typically with DSL.trueCondition(), DSL.falseCondition(), or DSL.noCondition() as the parameter) or where(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>	where(Collection<? extends Condition> conditions) Add conditions to the query, connecting them with each other with Operator.AND.
DeleteConditionStep<R>	where(Condition... conditions) Add conditions to the query, connecting them with each other with Operator.AND.
DeleteConditionStep<R>	where(Condition condition) Add conditions to the query, connecting them with each other with Operator.AND.
DeleteConditionStep<R>	where(Field<Boolean> condition) Add conditions to the query.
DeleteConditionStep<R>	where(SQL sql) Add conditions to the query.
DeleteConditionStep<R>	where(String sql) Add conditions to the query.
DeleteConditionStep<R>	where(String sql, Object... bindings) Add conditions to the query.
DeleteConditionStep<R>	where(String sql, QueryPart... parts) Add conditions to the query.
DeleteConditionStep<R>	whereExists(Select<?> select) Add an EXISTS clause to the query.
DeleteConditionStep<R>	whereNotExists(Select<?> select) Add a NOT EXISTS clause to the query.

Methods inherited from interface org.jooq.DeleteOrderByStep

orderBy, orderBy, orderBy

Methods inherited from interface org.jooq.DeleteLimitStep

limit, limit

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

Methods inherited from interface org.jooq.Attachable

attach, configuration, detach

Methods inherited from interface org.reactivestreams.Publisher

subscribe

Method Detail

where

@Support
DeleteConditionStep<R> where(Condition condition)

Add conditions to the query, connecting them with each other with Operator.AND.

where

@Support
DeleteConditionStep<R> where(Condition... conditions)

Add conditions to the query, connecting them with each other with Operator.AND.

where

@Support
DeleteConditionStep<R> where(Collection<? extends Condition> conditions)

Add conditions to the query, connecting them with each other with Operator.AND.

where

@Support
DeleteConditionStep<R> where(Field<Boolean> condition)

Add conditions to the query.

where

@Deprecated
 @Support
DeleteConditionStep<R> where(Boolean condition)

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

Add conditions to the query.

where

@Support
 @PlainSQL
DeleteConditionStep<R> where(SQL sql)

Add conditions to the query.

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

where

@Support
 @PlainSQL
DeleteConditionStep<R> where(String sql)

Add conditions to the query.

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

where

@Support
 @PlainSQL
DeleteConditionStep<R> where(String sql,
                                                   Object... bindings)

Add conditions to the query.

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

where

@Support
 @PlainSQL
DeleteConditionStep<R> where(String sql,
                                                   QueryPart... parts)

Add conditions to the query.

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

whereExists

@Support
DeleteConditionStep<R> whereExists(Select<?> select)

Add an EXISTS clause to the query.

whereNotExists

@Support
DeleteConditionStep<R> whereNotExists(Select<?> select)

Add a NOT EXISTS clause to the query.