public interface InsertOnConflictConditionStep<R extends Record> extends InsertFinalStep<R>
Insert
's DSL API.
Example:
DSLContext create = DSL.using(configuration);
create.insertInto(table, field1, field2)
.values(value1, value2)
.values(value3, value4)
.onDuplicateKeyUpdate()
.set(field1, value1)
.set(field2, value2)
.execute();
Modifier and Type | Method and Description |
---|---|
InsertOnConflictConditionStep<R> |
and(Condition condition)
Combine the currently assembled conditions with another one using the
Operator.AND operator and proceed to the next step. |
InsertOnConflictConditionStep<R> |
and(Field<java.lang.Boolean> condition)
Combine the currently assembled conditions with another one using the
Operator.AND operator and proceed to the next step. |
InsertOnConflictConditionStep<R> |
and(SQL sql)
Combine the currently assembled conditions with another one using the
Operator.AND operator and proceed to the next step. |
InsertOnConflictConditionStep<R> |
and(java.lang.String sql)
Combine the currently assembled conditions with another one using the
Operator.AND operator and proceed to the next step. |
InsertOnConflictConditionStep<R> |
and(java.lang.String sql,
java.lang.Object... bindings)
Combine the currently assembled conditions with another one using the
Operator.AND operator and proceed to the next step. |
InsertOnConflictConditionStep<R> |
and(java.lang.String sql,
QueryPart... parts)
Combine the currently assembled conditions with another one using the
Operator.AND operator and proceed to the next step. |
InsertOnConflictConditionStep<R> |
andExists(Select<?> select)
Combine the currently assembled conditions with an EXISTS clause using
the
Operator.AND operator and proceed to the next step. |
InsertOnConflictConditionStep<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. |
InsertOnConflictConditionStep<R> |
andNot(Field<java.lang.Boolean> condition)
Combine the currently assembled conditions with a negated other one using
the
Operator.AND operator and proceed to the next step. |
InsertOnConflictConditionStep<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. |
InsertOnConflictConditionStep<R> |
or(Condition condition)
Combine the currently assembled conditions with another one using the
Operator.OR operator and proceed to the next step. |
InsertOnConflictConditionStep<R> |
or(Field<java.lang.Boolean> condition)
Combine the currently assembled conditions with another one using the
Operator.OR operator and proceed to the next step. |
InsertOnConflictConditionStep<R> |
or(SQL sql)
Combine the currently assembled conditions with another one using the
Operator.OR operator and proceed to the next step. |
InsertOnConflictConditionStep<R> |
or(java.lang.String sql)
Combine the currently assembled conditions with another one using the
Operator.OR operator and proceed to the next step. |
InsertOnConflictConditionStep<R> |
or(java.lang.String sql,
java.lang.Object... bindings)
Combine the currently assembled conditions with another one using the
Operator.OR operator and proceed to the next step. |
InsertOnConflictConditionStep<R> |
or(java.lang.String sql,
QueryPart... parts)
Combine the currently assembled conditions with another one using the
Operator.OR operator and proceed to the next step. |
InsertOnConflictConditionStep<R> |
orExists(Select<?> select)
Combine the currently assembled conditions with an EXISTS clause using
the
Operator.OR operator and proceed to the next step. |
InsertOnConflictConditionStep<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. |
InsertOnConflictConditionStep<R> |
orNot(Field<java.lang.Boolean> condition)
Combine the currently assembled conditions with a negated other one using
the
Operator.OR operator and proceed to the next step. |
InsertOnConflictConditionStep<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. |
bind, bind, cancel, close, execute, executeAsync, executeAsync, getBindValues, getParam, getParams, getSQL, getSQL, getSQL, isExecutable, keepStatement, queryTimeout
attach, configuration, detach
@Support(value=POSTGRES_9_5) InsertOnConflictConditionStep<R> and(Condition condition)
Operator.AND
operator and proceed to the next step.@Support(value=POSTGRES_9_5) InsertOnConflictConditionStep<R> and(Field<java.lang.Boolean> condition)
Operator.AND
operator and proceed to the next step.@Support(value=POSTGRES_9_5) @PlainSQL InsertOnConflictConditionStep<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=POSTGRES_9_5) @PlainSQL InsertOnConflictConditionStep<R> and(java.lang.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=POSTGRES_9_5) @PlainSQL InsertOnConflictConditionStep<R> and(java.lang.String sql, java.lang.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!
@Support(value=POSTGRES_9_5) @PlainSQL InsertOnConflictConditionStep<R> and(java.lang.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!
@Support(value=POSTGRES_9_5) InsertOnConflictConditionStep<R> andNot(Condition condition)
Operator.AND
operator and proceed to the next step.@Support(value=POSTGRES_9_5) InsertOnConflictConditionStep<R> andNot(Field<java.lang.Boolean> condition)
Operator.AND
operator and proceed to the next step.@Support(value=POSTGRES_9_5) InsertOnConflictConditionStep<R> andExists(Select<?> select)
Operator.AND
operator and proceed to the next step.@Support(value=POSTGRES_9_5) InsertOnConflictConditionStep<R> andNotExists(Select<?> select)
Operator.AND
operator and proceed to the next step.@Support(value=POSTGRES_9_5) InsertOnConflictConditionStep<R> or(Condition condition)
Operator.OR
operator and proceed to the next step.@Support(value=POSTGRES_9_5) InsertOnConflictConditionStep<R> or(Field<java.lang.Boolean> condition)
Operator.OR
operator and proceed to the next step.@Support(value=POSTGRES_9_5) @PlainSQL InsertOnConflictConditionStep<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=POSTGRES_9_5) @PlainSQL InsertOnConflictConditionStep<R> or(java.lang.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=POSTGRES_9_5) @PlainSQL InsertOnConflictConditionStep<R> or(java.lang.String sql, java.lang.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!
@Support(value=POSTGRES_9_5) @PlainSQL InsertOnConflictConditionStep<R> or(java.lang.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!
@Support(value=POSTGRES_9_5) InsertOnConflictConditionStep<R> orNot(Condition condition)
Operator.OR
operator and proceed to the next step.@Support(value=POSTGRES_9_5) InsertOnConflictConditionStep<R> orNot(Field<java.lang.Boolean> condition)
Operator.OR
operator and proceed to the next step.@Support(value=POSTGRES_9_5) InsertOnConflictConditionStep<R> orExists(Select<?> select)
Operator.OR
operator and proceed to the next step.@Support(value=POSTGRES_9_5) InsertOnConflictConditionStep<R> orNotExists(Select<?> select)
Operator.OR
operator and proceed to the next step.Copyright © 2018. All Rights Reserved.