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();
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:
| Modifier and Type | Method and Description |
|---|---|
| public @NotNull InsertOnConflictDoUpdateStep | |
| public @NotNull InsertOnConflictDoUpdateStep | where(Condition... conditions)
Deprecated
as a consequence of
Add a Condition being deprecated.
WHERE clause to supply an index predicate to the
INSERT statement's ON CONFLICT … clause,
connecting them with each other using Operator#AND.
|
| public @NotNull InsertOnConflictDoUpdateStep | where(Collection<? extends Condition> conditions)
Add a |
| public @NotNull InsertOnConflictDoUpdateStep | |
| public @NotNull InsertOnConflictDoUpdateStep | |
| public @NotNull InsertOnConflictDoUpdateStep | |
| public @NotNull InsertOnConflictDoUpdateStep | |
| public @NotNull InsertOnConflictDoUpdateStep |
| where | back to summary |
|---|---|
| public @NotNull InsertOnConflictDoUpdateStep Deprecated as a consequence of Add a
| |
| where | back to summary |
|---|---|
| public @NotNull InsertOnConflictDoUpdateStep Deprecated as a consequence of Add a
| |
| where | back to summary |
|---|---|
| public @NotNull InsertOnConflictDoUpdateStep Add a
| |
| where | back to summary |
|---|---|
| public @NotNull InsertOnConflictDoUpdateStep Deprecated as a consequence of Add a
| |
| where | back to summary |
|---|---|
| public @NotNull InsertOnConflictDoUpdateStep Add a 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!
| |
| where | back to summary |
|---|---|
| public @NotNull InsertOnConflictDoUpdateStep Add a 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!
| |
| where | back to summary |
|---|---|
| public @NotNull InsertOnConflictDoUpdateStep Add a 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!
| |
| where | back to summary |
|---|---|
| public @NotNull InsertOnConflictDoUpdateStep Add a 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!
| |