org.jooq
Interface MergeOnConditionStep<R extends Record>

All Superinterfaces:
Adapter, Attachable, Merge<R>, MergeFinalStep<R>, MergeMatchedStep<R>, MergeNotMatchedStep<R>, Query, QueryPart, Serializable

public interface MergeOnConditionStep<R extends Record>
extends MergeMatchedStep<R>

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

Example:

 Factory create = new Factory();

 create.mergeInto(table)
       .using(select)
       .on(condition)
       .whenMatchedThenUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .whenNotMatchedThenInsert(field1, field2)
       .values(value1, value2)
       .execute();
 

Author:
Lukas Eder

Method Summary
 MergeOnConditionStep<R> and(Condition condition)
          Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.
 MergeOnConditionStep<R> and(String sql)
          Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.
 MergeOnConditionStep<R> and(String sql, Object... bindings)
          Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.
 MergeOnConditionStep<R> andExists(Select<?> select)
          Combine the currently assembled conditions with an EXISTS clause using the Operator.AND operator and proceed to the next step.
 MergeOnConditionStep<R> andNot(Condition condition)
          Combine the currently assembled conditions with a negated other one using the Operator.AND operator and proceed to the next step.
 MergeOnConditionStep<R> andNotExists(Select<?> select)
          Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.AND operator and proceed to the next step.
 MergeOnConditionStep<R> or(Condition condition)
          Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.
 MergeOnConditionStep<R> or(String sql)
          Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.
 MergeOnConditionStep<R> or(String sql, Object... bindings)
          Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.
 MergeOnConditionStep<R> orExists(Select<?> select)
          Combine the currently assembled conditions with an EXISTS clause using the Operator.OR operator and proceed to the next step.
 MergeOnConditionStep<R> orNot(Condition condition)
          Combine the currently assembled conditions with a negated other one using the Operator.OR operator and proceed to the next step.
 MergeOnConditionStep<R> orNotExists(Select<?> select)
          Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.OR operator and proceed to the next step.
 
Methods inherited from interface org.jooq.MergeMatchedStep
whenMatchedThenUpdate
 
Methods inherited from interface org.jooq.MergeNotMatchedStep
whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert
 
Methods inherited from interface org.jooq.Query
bind, bind, execute, getBindValues, getParam, getParams, getSQL, getSQL
 
Methods inherited from interface org.jooq.Attachable
attach
 
Methods inherited from interface org.jooq.Adapter
internalAPI
 

Method Detail

and

MergeOnConditionStep<R> and(Condition condition)
Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.


and

MergeOnConditionStep<R> and(String sql)
Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.

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

MergeOnConditionStep<R> and(String sql,
                            Object... bindings)
Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.

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

andNot

MergeOnConditionStep<R> andNot(Condition condition)
Combine the currently assembled conditions with a negated other one using the Operator.AND operator and proceed to the next step.


andExists

MergeOnConditionStep<R> andExists(Select<?> select)
Combine the currently assembled conditions with an EXISTS clause using the Operator.AND operator and proceed to the next step.


andNotExists

MergeOnConditionStep<R> andNotExists(Select<?> select)
Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.AND operator and proceed to the next step.


or

MergeOnConditionStep<R> or(Condition condition)
Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.


or

MergeOnConditionStep<R> or(String sql)
Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.

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

MergeOnConditionStep<R> or(String sql,
                           Object... bindings)
Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.

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

orNot

MergeOnConditionStep<R> orNot(Condition condition)
Combine the currently assembled conditions with a negated other one using the Operator.OR operator and proceed to the next step.


orExists

MergeOnConditionStep<R> orExists(Select<?> select)
Combine the currently assembled conditions with an EXISTS clause using the Operator.OR operator and proceed to the next step.


orNotExists

MergeOnConditionStep<R> orNotExists(Select<?> select)
Combine the currently assembled conditions with a NOT EXISTS clause using the Operator.OR operator and proceed to the next step.



Copyright © 2012. All Rights Reserved.