Deprecated
as a consequence of MergeNotMatchedStep being deprecated. See corresponding docs for further information.
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();
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 MergeMatchedThenStep | whenMatchedAnd(Condition condition)
Deprecated
as a consequence of
Add the Condition being deprecated.
WHEN MATCHED AND clause to the
MERGE statement.
|
| public @NotNull MergeMatchedThenStep | whenMatchedAnd(Field<Boolean> condition)
Deprecated
as a consequence of
Add the Field being deprecated.
WHEN MATCHED AND clause to the
MERGE statement.
|
| public @NotNull MergeMatchedThenStep | |
| public @NotNull MergeMatchedThenStep | |
| public @NotNull MergeMatchedThenStep | whenMatchedAnd(String sql, Object... bindings)
Add the |
| public @NotNull MergeMatchedThenStep | whenMatchedAnd(String sql, QueryPart... parts)
Add the |
| public @NotNull MergeMatchedStep | whenMatchedThenDelete()
Deprecated
as a consequence of
Add the MergeMatchedStep being deprecated.
WHEN MATCHED THEN DELETE clause to the
MERGE statement.
|
| public @NotNull MergeMatchedSetStep |
| whenMatchedAnd | back to summary |
|---|---|
| public @NotNull MergeMatchedThenStep Deprecated as a consequence of Add the | |
| whenMatchedAnd | back to summary |
|---|---|
| public @NotNull MergeMatchedThenStep Deprecated as a consequence of Add the | |
| whenMatchedAnd | back to summary |
|---|---|
| public @NotNull MergeMatchedThenStep Add the 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! | |
| whenMatchedAnd | back to summary |
|---|---|
| public @NotNull MergeMatchedThenStep Add the 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! | |
| whenMatchedAnd | back to summary |
|---|---|
| public @NotNull MergeMatchedThenStep Add the 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!
| |
| whenMatchedAnd | back to summary |
|---|---|
| public @NotNull MergeMatchedThenStep Add the 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!
| |
| whenMatchedThenDelete | back to summary |
|---|---|
| public @NotNull MergeMatchedStep Deprecated as a consequence of Add the | |
| whenMatchedThenUpdate | back to summary |
|---|---|
| public @NotNull MergeMatchedSetStep Add the | |