org.jooq
Interface UpdateConditionStep<R extends Record>

All Superinterfaces:

Adapter, Attachable, Query, QueryPart, Serializable, Update<R>, UpdateFinalStep<R>

public interface UpdateConditionStep<R extends Record>
extends UpdateFinalStep<R>

This type is used for the Update's DSL API.

Example:

 Factory create = new Factory();

 create.update(table)
       .set(field1, value1)
       .set(field2, value2)
       .where(field1.greaterThan(100))
       .execute();
 

Author:

Lukas Eder

Method Summary

UpdateConditionStep<R>	and(Condition condition) Combine the currently assembled conditions with another one using the Operator.AND operator
UpdateConditionStep<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.
UpdateConditionStep<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.
UpdateConditionStep<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.
UpdateConditionStep<R>	andExists(Select<?> select) Combine the currently assembled conditions with an EXISTS clause using the Operator.AND operator
UpdateConditionStep<R>	andNot(Condition condition) Combine the currently assembled conditions with a negated other one using the Operator.AND operator
UpdateConditionStep<R>	andNotExists(Select<?> select) Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.AND operator
UpdateConditionStep<R>	or(Condition condition) Combine the currently assembled conditions with another one using the Operator.OR operator
UpdateConditionStep<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.
UpdateConditionStep<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.
UpdateConditionStep<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.
UpdateConditionStep<R>	orExists(Select<?> select) Combine the currently assembled conditions with an EXISTS clause using the Operator.OR operator
UpdateConditionStep<R>	orNot(Condition condition) Combine the currently assembled conditions with a negated other one using the Operator.OR operator
UpdateConditionStep<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, execute, getBindValues, getParam, getParams, getSQL, getSQL, isExecutable

Methods inherited from interface org.jooq.QueryPart

attach

Methods inherited from interface org.jooq.Adapter

internalAPI

Method Detail

and

UpdateConditionStep<R> and(Condition condition)

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

and

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

Factory.condition(String)

and

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

Factory.condition(String, Object...)

and

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

Factory.condition(String, QueryPart...)

andNot

UpdateConditionStep<R> andNot(Condition condition)

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

andExists

UpdateConditionStep<R> andExists(Select<?> select)

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

andNotExists

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

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

or

UpdateConditionStep<R> or(Condition condition)

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

or

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

Factory.condition(String)

or

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

Factory.condition(String, Object...)

or

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

Factory.condition(String, QueryPart...)

orNot

UpdateConditionStep<R> orNot(Condition condition)

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

orExists

UpdateConditionStep<R> orExists(Select<?> select)

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

orNotExists

UpdateConditionStep<R> orNotExists(Select<?> select)

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