Deprecated
as a consequence of MergeMatchedDeleteStep 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 MergeMatchedDeleteStep | where(Condition condition)
Deprecated
as a consequence of
Add an additional Condition and MergeMatchedDeleteStep being deprecated.
WHERE clause to the preceding
WHEN MATCHED THEN UPDATE clause.
|
| public @NotNull MergeMatchedDeleteStep | where(Field<Boolean> condition)
Deprecated
as a consequence of
Add an additional Field and MergeMatchedDeleteStep being deprecated.
WHERE clause to the preceding
WHEN MATCHED THEN UPDATE clause.
|
| where | back to summary |
|---|---|
| public @NotNull MergeMatchedDeleteStep Deprecated as a consequence of Add an additional
In Oracle, this will produce:
In SQL Server, this will produce:
| |
| where | back to summary |
|---|---|
| public @NotNull MergeMatchedDeleteStep Deprecated as a consequence of Add an additional
In Oracle, this will produce:
In SQL Server, this will produce:
| |