public interface MergeOnStep<R extends Record>
Merge's DSL API.
 
 Example: 
 DSLContext create = DSL.using(configuration);
 create.mergeInto(table)
       .using(select)
       .on(condition)
       .whenMatchedThenUpdate()
       .set(field1, value1)
       .set(field2, value2)
       .whenNotMatchedThenInsert(field1, field2)
       .values(value1, value2)
       .execute();
 
| Modifier and Type | Method and Description | 
|---|---|
| MergeOnConditionStep<R> | on(java.lang.Boolean condition)Deprecated. 
 - 3.8.0 - [#4763] - Use  on(Condition...)oron(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. | 
| MergeOnConditionStep<R> | on(Condition... conditions)Provide join conditions and proceed to the next step, connecting them
 with each other with  Operator.AND. | 
| MergeOnConditionStep<R> | on(Field<java.lang.Boolean> condition)Provide join conditions and proceed to the next step | 
| MergeOnConditionStep<R> | on(SQL sql)Provide join conditions and proceed to the next step
 
 NOTE: When inserting plain SQL into jOOQ objects, you must
 guarantee syntax integrity. | 
| MergeOnConditionStep<R> | on(java.lang.String sql)Provide join conditions and proceed to the next step
 
 NOTE: When inserting plain SQL into jOOQ objects, you must
 guarantee syntax integrity. | 
| MergeOnConditionStep<R> | on(java.lang.String sql,
  java.lang.Object... bindings)Provide join conditions and proceed to the next step
 
 NOTE: When inserting plain SQL into jOOQ objects, you must
 guarantee syntax integrity. | 
| MergeOnConditionStep<R> | on(java.lang.String sql,
  QueryPart... parts)Provide join conditions and proceed to the next step
 
 NOTE: When inserting plain SQL into jOOQ objects, you must
 guarantee syntax integrity. | 
@Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) MergeOnConditionStep<R> on(Condition... conditions)
Operator.AND.@Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) MergeOnConditionStep<R> on(Field<java.lang.Boolean> condition)
@Deprecated @Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) MergeOnConditionStep<R> on(java.lang.Boolean condition)
on(Condition...) or
             on(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(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) @PlainSQL MergeOnConditionStep<R> on(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(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) @PlainSQL MergeOnConditionStep<R> on(java.lang.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(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) @PlainSQL MergeOnConditionStep<R> on(java.lang.String sql, java.lang.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(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) @PlainSQL MergeOnConditionStep<R> on(java.lang.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!
Copyright © 2018. All Rights Reserved.