public interface DeleteWhereStep<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> | where(Boolean condition)Deprecated. 
 - 3.8.0 - [#4763] - Use  where(Condition)orwhere(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. | 
| 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. | 
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, returningResultbind, bind, cancel, close, execute, executeAsync, executeAsync, getBindValues, getParam, getParams, getSQL, getSQL, getSQL, isExecutable, keepStatement, queryTimeoutattach, configuration, detach@Support DeleteConditionStep<R> where(Condition condition)
Operator.AND.@Support DeleteConditionStep<R> where(Condition... conditions)
Operator.AND.@Support DeleteConditionStep<R> where(Collection<? extends Condition> conditions)
Operator.AND.@Support DeleteConditionStep<R> where(Field<Boolean> condition)
@Deprecated @Support DeleteConditionStep<R> where(Boolean condition)
where(Condition) 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.@Support @PlainSQL DeleteConditionStep<R> where(SQL sql)
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> where(String sql)
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> where(String sql, Object... bindings)
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> where(String sql, QueryPart... parts)
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> whereExists(Select<?> select)
@Support DeleteConditionStep<R> whereNotExists(Select<?> select)
Copyright © 2019. All rights reserved.