org.jooq

Interface DeleteConditionStep<R extends Record>

All Superinterfaces:

Attachable, Delete<R>, DeleteFinalStep<R>, DeleteReturningStep<R>, Query, QueryPart, Serializable

public interface DeleteConditionStep<R extends Record>
extends DeleteFinalStep<R>, DeleteReturningStep<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();
 

Author:

Lukas Eder

Method Summary

Modifier and Type	Method and Description
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(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(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(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(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(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

Methods inherited from interface org.jooq.Query

bind, bind, cancel, close, execute, getBindValues, getParam, getParams, getSQL, getSQL, getSQL, isExecutable, keepStatement, queryTimeout

Methods inherited from interface org.jooq.QueryPart

equals, hashCode, toString

Methods inherited from interface org.jooq.Attachable

attach, detach

Methods inherited from interface org.jooq.DeleteReturningStep

returning, returning, returning

Method Detail

and

@Support
DeleteConditionStep<R> and(Condition condition)

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

and

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

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

and

@Support
 @PlainSQL
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)

and

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

and

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

andNot

@Support
DeleteConditionStep<R> andNot(Condition condition)

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

andNot

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

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

andExists

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

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

andNotExists

DeleteConditionStep<R> andNotExists(Select<?> select)

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

or

@Support
DeleteConditionStep<R> or(Condition condition)

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

or

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

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

or

@Support
 @PlainSQL
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)

or

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

or

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

orNot

@Support
DeleteConditionStep<R> orNot(Condition condition)

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

orNot

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

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

orExists

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

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

orNotExists

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

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