org.jooq

Interface InsertOnConflictConditionStep<R extends Record>

All Superinterfaces:

Attachable, AutoCloseable, Insert<R>, InsertFinalStep<R>, Query, QueryPart, Serializable, Statement

public interface InsertOnConflictConditionStep<R extends Record>
extends InsertFinalStep<R>

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

Referencing XYZ*Step types directly from client code

It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql.

Drawbacks of referencing the XYZ*Step types directly:

• They're operating on mutable implementations (as of jOOQ 3.x)
• They're less composable and not easy to get right when dynamic SQL gets complex
• They're less readable
• They might have binary incompatible changes between minor releases

Author:

Lukas Eder

Method Summary

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<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(String sql) Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.
InsertOnConflictConditionStep<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.
InsertOnConflictConditionStep<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.
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<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<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(String sql) Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.
InsertOnConflictConditionStep<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.
InsertOnConflictConditionStep<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.
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<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.

Methods inherited from interface org.jooq.Query

bind, bind, cancel, close, execute, executeAsync, executeAsync, getBindValues, getParam, getParams, getSQL, getSQL, getSQL, isExecutable, keepStatement, queryTimeout

Methods inherited from interface org.jooq.QueryPart

equals, hashCode, toString

Methods inherited from interface org.jooq.Attachable

attach, configuration, detach

Method Detail

and

@Support(value={AURORA_POSTGRES,POSTGRES_9_5})
InsertOnConflictConditionStep<R> and(Condition condition)

Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.

and

@Support(value={AURORA_POSTGRES,POSTGRES_9_5})
InsertOnConflictConditionStep<R> and(Field<Boolean> condition)

Combine the currently assembled conditions with another one using the Operator.AND operator and proceed to the next step.

and

@Support(value={AURORA_POSTGRES,POSTGRES_9_5})
 @PlainSQL
InsertOnConflictConditionStep<R> and(SQL 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:

DSL.condition(SQL), SQL

and

@Support(value={AURORA_POSTGRES,POSTGRES_9_5})
 @PlainSQL
InsertOnConflictConditionStep<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:

DSL.condition(String), SQL

and

@Support(value={AURORA_POSTGRES,POSTGRES_9_5})
 @PlainSQL
InsertOnConflictConditionStep<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:

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

and

@Support(value={AURORA_POSTGRES,POSTGRES_9_5})
 @PlainSQL
InsertOnConflictConditionStep<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.

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...), DSL.sql(String, QueryPart...), SQL

andNot

@Support(value={AURORA_POSTGRES,POSTGRES_9_5})
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.

andNot

@Support(value={AURORA_POSTGRES,POSTGRES_9_5})
InsertOnConflictConditionStep<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.

andExists

@Support(value={AURORA_POSTGRES,POSTGRES_9_5})
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.

andNotExists

@Support(value={AURORA_POSTGRES,POSTGRES_9_5})
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.

or

@Support(value={AURORA_POSTGRES,POSTGRES_9_5})
InsertOnConflictConditionStep<R> or(Condition condition)

Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.

or

@Support(value={AURORA_POSTGRES,POSTGRES_9_5})
InsertOnConflictConditionStep<R> or(Field<Boolean> condition)

Combine the currently assembled conditions with another one using the Operator.OR operator and proceed to the next step.

or

@Support(value={AURORA_POSTGRES,POSTGRES_9_5})
 @PlainSQL
InsertOnConflictConditionStep<R> or(SQL 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:

DSL.condition(SQL), SQL

or

@Support(value={AURORA_POSTGRES,POSTGRES_9_5})
 @PlainSQL
InsertOnConflictConditionStep<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:

DSL.condition(String), SQL

or

@Support(value={AURORA_POSTGRES,POSTGRES_9_5})
 @PlainSQL
InsertOnConflictConditionStep<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:

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

or

@Support(value={AURORA_POSTGRES,POSTGRES_9_5})
 @PlainSQL
InsertOnConflictConditionStep<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.

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...), DSL.sql(String, QueryPart...), SQL

orNot

@Support(value={AURORA_POSTGRES,POSTGRES_9_5})
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.

orNot

@Support(value={AURORA_POSTGRES,POSTGRES_9_5})
InsertOnConflictConditionStep<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.

orExists

@Support(value={AURORA_POSTGRES,POSTGRES_9_5})
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.

orNotExists

@Support(value={AURORA_POSTGRES,POSTGRES_9_5})
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.