Top Description Methods
org.jooq

public Interface InsertOnConflictWhereStep<R extends org.jooq.Record>

extends InsertReturningStep<R extends Record>
Known Direct Subinterfaces
org.jooq.InsertOnDuplicateSetMoreStep
Imports
org.jetbrains.annotations.*, java.util.Collection, org.jooq.impl.DSL

Deprecated

as a consequence of InsertReturningStep being deprecated. See corresponding docs for further information.

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)
      .onConflict(field1)
      .doUpdate()
      .set(field2, value2)
      .where(field3.eq(value5))
      .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:

Author
Lukas Eder

Method Summary

Modifier and TypeMethod and Description
public @NotNull InsertOnConflictConditionStep<R>
where(Condition condition)

Deprecated as a consequence of Condition and InsertOnConflictConditionStep being deprecated.
Add a WHERE clause to the INSERT statement's ON DUPLICATE KEY UPDATE or ON CONFLICT … DO UPDATE clause.
public @NotNull InsertOnConflictConditionStep<R>
where(Condition... conditions)

Deprecated as a consequence of Condition and InsertOnConflictConditionStep being deprecated.
Add a WHERE clause to the INSERT statement's ON DUPLICATE KEY UPDATE or ON CONFLICT … DO UPDATE clause, connecting them with each other using Operator#AND.
public @NotNull InsertOnConflictConditionStep<R>
where(Collection<? extends Condition> conditions)

Deprecated as a consequence of InsertOnConflictConditionStep being deprecated.
Add a WHERE clause to the INSERT statement's ON DUPLICATE KEY UPDATE or ON CONFLICT … DO UPDATE clause, connecting them with each other using Operator#AND.
public @NotNull InsertOnConflictConditionStep<R>
where(Field<Boolean> field)

Deprecated as a consequence of Field and InsertOnConflictConditionStep being deprecated.
Add a WHERE clause to the INSERT statement's ON DUPLICATE KEY UPDATE or ON CONFLICT … DO UPDATE clause.
public @NotNull InsertOnConflictConditionStep<R>
where(SQL sql)

Deprecated as a consequence of InsertOnConflictConditionStep being deprecated.
Add a WHERE clause to the INSERT statement's ON DUPLICATE KEY UPDATE or ON CONFLICT … DO UPDATE clause.
public @NotNull InsertOnConflictConditionStep<R>
where(String sql)

Deprecated as a consequence of InsertOnConflictConditionStep being deprecated.
Add a WHERE clause to the INSERT statement's ON DUPLICATE KEY UPDATE or ON CONFLICT … DO UPDATE clause.
public @NotNull InsertOnConflictConditionStep<R>
where(String sql, Object... bindings)

Deprecated as a consequence of InsertOnConflictConditionStep being deprecated.
Add a WHERE clause to the INSERT statement's ON DUPLICATE KEY UPDATE or ON CONFLICT … DO UPDATE clause.
public @NotNull InsertOnConflictConditionStep<R>
where(String sql, QueryPart... parts)

Deprecated as a consequence of InsertOnConflictConditionStep being deprecated.
Add a WHERE clause to the INSERT statement's ON DUPLICATE KEY UPDATE or ON CONFLICT … DO UPDATE clause.
public @NotNull InsertOnConflictConditionStep<R>
whereExists(Select<?> select)

Deprecated as a consequence of InsertOnConflictConditionStep being deprecated.
Add a WHERE EXISTS clause to the INSERT statement's ON DUPLICATE KEY UPDATE or ON CONFLICT … DO UPDATE clause.
public @NotNull InsertOnConflictConditionStep<R>
whereNotExists(Select<?> select)

Deprecated as a consequence of InsertOnConflictConditionStep being deprecated.
Add a WHERE NOT EXISTS clause to the INSERT statement's ON DUPLICATE KEY UPDATE or ON CONFLICT … DO UPDATE clause.
Inherited from org.jooq.InsertReturningStep:
returningreturningreturningreturningResultreturningResultreturningResultreturningResultreturningResultreturningResultreturningResultreturningResultreturningResultreturningResultreturningResultreturningResultreturningResultreturningResultreturningResultreturningResultreturningResultreturningResultreturningResultreturningResultreturningResultreturningResultreturningResultreturningResult

Method Detail

whereback to summary
public @NotNull InsertOnConflictConditionStep<R> where(Condition condition)

Deprecated

as a consequence of Condition and InsertOnConflictConditionStep being deprecated. See corresponding docs for further information.

Add a WHERE clause to the INSERT statement's ON DUPLICATE KEY UPDATE or ON CONFLICT … DO UPDATE clause.

Annotations
@NotNull
@CheckReturnValue
@Support:CUBRID, DERBY, H2, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB
whereback to summary
public @NotNull InsertOnConflictConditionStep<R> where(Condition... conditions)

Deprecated

as a consequence of Condition and InsertOnConflictConditionStep being deprecated. See corresponding docs for further information.

Add a WHERE clause to the INSERT statement's ON DUPLICATE KEY UPDATE or ON CONFLICT … DO UPDATE clause, connecting them with each other using Operator#AND.

Annotations
@NotNull
@CheckReturnValue
@Support:CUBRID, DERBY, H2, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB
whereback to summary
public @NotNull InsertOnConflictConditionStep<R> where(Collection<? extends Condition> conditions)

Deprecated

as a consequence of InsertOnConflictConditionStep being deprecated. See corresponding docs for further information.

Add a WHERE clause to the INSERT statement's ON DUPLICATE KEY UPDATE or ON CONFLICT … DO UPDATE clause, connecting them with each other using Operator#AND.

Annotations
@NotNull
@CheckReturnValue
@Support:CUBRID, DERBY, H2, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB
whereback to summary
public @NotNull InsertOnConflictConditionStep<R> where(Field<Boolean> field)

Deprecated

as a consequence of Field and InsertOnConflictConditionStep being deprecated. See corresponding docs for further information.

Add a WHERE clause to the INSERT statement's ON DUPLICATE KEY UPDATE or ON CONFLICT … DO UPDATE clause.

Annotations
@NotNull
@CheckReturnValue
@Support:CUBRID, DERBY, H2, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB
whereback to summary
public @NotNull InsertOnConflictConditionStep<R> where(SQL sql)

Deprecated

as a consequence of InsertOnConflictConditionStep being deprecated. See corresponding docs for further information.

Add a WHERE clause to the INSERT statement's ON DUPLICATE KEY UPDATE or ON CONFLICT … DO UPDATE clause.

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!

Annotations
@NotNull
@CheckReturnValue
@Support:CUBRID, DERBY, H2, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB
@PlainSQL
See Also
DSL#condition(SQL), SQL
whereback to summary
public @NotNull InsertOnConflictConditionStep<R> where(String sql)

Deprecated

as a consequence of InsertOnConflictConditionStep being deprecated. See corresponding docs for further information.

Add a WHERE clause to the INSERT statement's ON DUPLICATE KEY UPDATE or ON CONFLICT … DO UPDATE clause.

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!

Annotations
@NotNull
@CheckReturnValue
@Support:CUBRID, DERBY, H2, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB
@PlainSQL
See Also
DSL#condition(String), SQL
whereback to summary
public @NotNull InsertOnConflictConditionStep<R> where(String sql, Object... bindings)

Deprecated

as a consequence of InsertOnConflictConditionStep being deprecated. See corresponding docs for further information.

Add a WHERE clause to the INSERT statement's ON DUPLICATE KEY UPDATE or ON CONFLICT … DO UPDATE clause.

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!

Annotations
@NotNull
@CheckReturnValue
@Support:CUBRID, DERBY, H2, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB
@PlainSQL
See Also
DSL#condition(String, Object...), DSL#sql(String, Object...), SQL
whereback to summary
public @NotNull InsertOnConflictConditionStep<R> where(String sql, QueryPart... parts)

Deprecated

as a consequence of InsertOnConflictConditionStep being deprecated. See corresponding docs for further information.

Add a WHERE clause to the INSERT statement's ON DUPLICATE KEY UPDATE or ON CONFLICT … DO UPDATE clause.

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!

Annotations
@NotNull
@CheckReturnValue
@Support:CUBRID, DERBY, H2, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB
@PlainSQL
See Also
DSL#condition(String, QueryPart...), DSL#sql(String, QueryPart...), SQL
whereExistsback to summary
public @NotNull InsertOnConflictConditionStep<R> whereExists(Select<?> select)

Deprecated

as a consequence of InsertOnConflictConditionStep being deprecated. See corresponding docs for further information.

Add a WHERE EXISTS clause to the INSERT statement's ON DUPLICATE KEY UPDATE or ON CONFLICT … DO UPDATE clause.

Annotations
@NotNull
@CheckReturnValue
@Support:CUBRID, DERBY, H2, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB
whereNotExistsback to summary
public @NotNull InsertOnConflictConditionStep<R> whereNotExists(Select<?> select)

Deprecated

as a consequence of InsertOnConflictConditionStep being deprecated. See corresponding docs for further information.

Add a WHERE NOT EXISTS clause to the INSERT statement's ON DUPLICATE KEY UPDATE or ON CONFLICT … DO UPDATE clause.

Annotations
@NotNull
@CheckReturnValue
@Support:CUBRID, DERBY, H2, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB