public interface MergeOnConditionStep<R extends Record> extends MergeMatchedStep<R>
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> |
and(Boolean condition)
Deprecated.
- 3.8.0 - [#4763] - Use
and(Condition) or
and(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. |
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(Field<Boolean> condition)
Combine the currently assembled conditions with another one using the
Operator.AND operator and proceed to the next step. |
MergeOnConditionStep<R> |
and(SQL 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)
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> |
and(String sql,
QueryPart... parts)
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(Boolean condition)
Deprecated.
- 3.8.0 - [#4763] - Use
andNot(Condition) or
andNot(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. |
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> |
andNot(Field<Boolean> 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(Boolean condition)
Deprecated.
- 3.8.0 - [#4763] - Use
or(Condition) or
or(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. |
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(Field<Boolean> condition)
Combine the currently assembled conditions with another one using the
Operator.OR operator and proceed to the next step. |
MergeOnConditionStep<R> |
or(SQL 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)
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> |
or(String sql,
QueryPart... parts)
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(Boolean condition)
Deprecated.
- 3.8.0 - [#4763] - Use
orNot(Condition) or
orNot(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. |
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> |
orNot(Field<Boolean> 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. |
whenMatchedThenUpdate
whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert, whenNotMatchedThenInsert
bind, bind, cancel, close, execute, executeAsync, executeAsync, getBindValues, getParam, getParams, getSQL, getSQL, getSQL, isExecutable, keepStatement, queryTimeout
attach, detach
@Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) MergeOnConditionStep<R> and(Condition condition)
Operator.AND
operator and proceed to the next step.@Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) MergeOnConditionStep<R> and(Field<Boolean> condition)
Operator.AND
operator and proceed to the next step.@Deprecated @Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) MergeOnConditionStep<R> and(Boolean condition)
and(Condition)
or
and(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.Operator.AND
operator and proceed to the next step.@Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) @PlainSQL MergeOnConditionStep<R> and(SQL sql)
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!
DSL.condition(SQL)
,
SQL
@Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) @PlainSQL MergeOnConditionStep<R> and(String sql)
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!
DSL.condition(String)
,
SQL
@Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) @PlainSQL MergeOnConditionStep<R> and(String sql, Object... bindings)
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!
DSL.condition(String, Object...)
,
SQL
@Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) @PlainSQL MergeOnConditionStep<R> and(String sql, QueryPart... parts)
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!
DSL.condition(String, QueryPart...)
,
SQL
@Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) MergeOnConditionStep<R> andNot(Condition condition)
Operator.AND
operator and proceed to the next step.@Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) MergeOnConditionStep<R> andNot(Field<Boolean> condition)
Operator.AND
operator and proceed to the next step.@Deprecated @Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) MergeOnConditionStep<R> andNot(Boolean condition)
andNot(Condition)
or
andNot(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.Operator.AND
operator and proceed to the next step.@Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) MergeOnConditionStep<R> andExists(Select<?> select)
Operator.AND
operator and proceed to the next step.@Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) MergeOnConditionStep<R> andNotExists(Select<?> select)
Operator.AND
operator and proceed to the next step.@Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) MergeOnConditionStep<R> or(Condition condition)
Operator.OR
operator and proceed to the next step.@Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) MergeOnConditionStep<R> or(Field<Boolean> condition)
Operator.OR
operator and proceed to the next step.@Deprecated @Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) MergeOnConditionStep<R> or(Boolean condition)
or(Condition)
or
or(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.Operator.OR
operator and proceed to the next step.@Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) @PlainSQL MergeOnConditionStep<R> or(SQL sql)
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!
DSL.condition(SQL)
,
SQL
@Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) @PlainSQL MergeOnConditionStep<R> or(String sql)
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!
DSL.condition(String)
,
SQL
@Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) @PlainSQL MergeOnConditionStep<R> or(String sql, Object... bindings)
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!
DSL.condition(String, Object...)
,
SQL
@Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) @PlainSQL MergeOnConditionStep<R> or(String sql, QueryPart... parts)
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!
DSL.condition(String, QueryPart...)
,
SQL
@Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) MergeOnConditionStep<R> orNot(Condition condition)
Operator.OR
operator and proceed to the next step.@Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) MergeOnConditionStep<R> orNot(Field<Boolean> condition)
Operator.OR
operator and proceed to the next step.@Deprecated @Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) MergeOnConditionStep<R> orNot(Boolean condition)
orNot(Condition)
or
orNot(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.Operator.OR
operator and proceed to the next step.@Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) MergeOnConditionStep<R> orExists(Select<?> select)
Operator.OR
operator and proceed to the next step.@Support(value={CUBRID,DB2,FIREBIRD_3_0,HSQLDB,ORACLE,SQLSERVER,SYBASE}) MergeOnConditionStep<R> orNotExists(Select<?> select)
Operator.OR
operator and proceed to the next step.Copyright © 2016. All Rights Reserved.