org.jooq

Interface MergeOnStep<R extends Record>

public interface MergeOnStep<R extends Record>

This type is used for the 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();
 

Author:

Lukas Eder

Method Summary

Modifier and Type	Method and Description
MergeOnConditionStep<R>	on(Boolean condition) Provide join conditions and proceed to the next step
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<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(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(String sql, 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(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.

Method Detail

on

@Support(value={CUBRID,DB2,HSQLDB,ORACLE,SQLSERVER,SYBASE})
MergeOnConditionStep<R> on(Condition... conditions)

Provide join conditions and proceed to the next step, connecting them with each other with Operator.AND.

on

@Support(value={CUBRID,DB2,HSQLDB,ORACLE,SQLSERVER,SYBASE})
MergeOnConditionStep<R> on(Field<Boolean> condition)

Provide join conditions and proceed to the next step

on

@Support(value={CUBRID,DB2,HSQLDB,ORACLE,SQLSERVER,SYBASE})
MergeOnConditionStep<R> on(Boolean condition)

Provide join conditions and proceed to the next step

on

@Support(value={CUBRID,DB2,HSQLDB,ORACLE,SQLSERVER,SYBASE})
 @PlainSQL
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. 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(SQL), SQL

on

@Support(value={CUBRID,DB2,HSQLDB,ORACLE,SQLSERVER,SYBASE})
 @PlainSQL
MergeOnConditionStep<R> on(String sql)

Provide join conditions 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:

DSL.condition(String), SQL

on

@Support(value={CUBRID,DB2,HSQLDB,ORACLE,SQLSERVER,SYBASE})
 @PlainSQL
MergeOnConditionStep<R> on(String sql,
                                                                                                    Object... bindings)

Provide join conditions 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:

DSL.condition(String, Object...), SQL

on

@Support(value={CUBRID,DB2,HSQLDB,ORACLE,SQLSERVER,SYBASE})
 @PlainSQL
MergeOnConditionStep<R> on(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. 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...), SQL