- All Known Subinterfaces:
MergeMatchedSetMoreStep<R>
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();
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 TypeMethodDescription@NotNull MergeMatchedSetMoreStep
<R> Set multiple values forUPDATE
in theMERGE
statement'sWHEN MATCHED
clause.<T> @NotNull MergeMatchedSetMoreStep
<R> Set values forUPDATE
in theMERGE
statement'sWHEN MATCHED
clause.<T> @NotNull MergeMatchedSetMoreStep
<R> Set values forUPDATE
in theMERGE
statement'sWHEN MATCHED
clause.<T> @NotNull MergeMatchedSetMoreStep
<R> Set values forUPDATE
in theMERGE
statement'sWHEN MATCHED
clause.@NotNull MergeMatchedSetMoreStep
<R> Set multiple values forUPDATE
in theMERGE
statement'sWHEN MATCHED
clause.<T> @NotNull MergeMatchedSetMoreStep
<R> Set anull
value forUPDATE
in theMERGE
statement'sWHEN MATCHED
clause.
-
Method Details
-
set
@NotNull @CheckReturnValue @Support({CUBRID,DB2,DERBY,EXASOL,FIREBIRD_3_0,H2,HANA,HSQLDB,INFORMIX,ORACLE,POSTGRES_15,SNOWFLAKE,SQLSERVER,SYBASE,TERADATA,VERTICA}) <T> @NotNull MergeMatchedSetMoreStep<R> set(Field<T> field, T value) Set values forUPDATE
in theMERGE
statement'sWHEN MATCHED
clause. -
set
@NotNull @CheckReturnValue @Support({CUBRID,DB2,DERBY,EXASOL,FIREBIRD_3_0,H2,HANA,HSQLDB,INFORMIX,ORACLE,POSTGRES_15,SNOWFLAKE,SQLSERVER,SYBASE,TERADATA,VERTICA}) <T> @NotNull MergeMatchedSetMoreStep<R> set(Field<T> field, Field<T> value) Set values forUPDATE
in theMERGE
statement'sWHEN MATCHED
clause. -
set
@NotNull @CheckReturnValue @Support({CUBRID,DB2,DERBY,EXASOL,FIREBIRD_3_0,H2,HANA,HSQLDB,INFORMIX,ORACLE,POSTGRES_15,SNOWFLAKE,SQLSERVER,SYBASE,TERADATA,VERTICA}) <T> @NotNull MergeMatchedSetMoreStep<R> set(Field<T> field, Select<? extends Record1<T>> value) Set values forUPDATE
in theMERGE
statement'sWHEN MATCHED
clause. -
setNull
@NotNull @CheckReturnValue @Support({CUBRID,DB2,DERBY,EXASOL,FIREBIRD_3_0,H2,HANA,HSQLDB,INFORMIX,ORACLE,POSTGRES_15,SNOWFLAKE,SQLSERVER,SYBASE,TERADATA,VERTICA}) <T> @NotNull MergeMatchedSetMoreStep<R> setNull(Field<T> field) Set anull
value forUPDATE
in theMERGE
statement'sWHEN MATCHED
clause.This method is convenience for calling
set(Field, Object)
, without the necessity of casting the Javanull
literal to(T)
. -
set
-
set
@NotNull @CheckReturnValue @Support({CUBRID,DB2,DERBY,EXASOL,FIREBIRD_3_0,H2,HANA,HSQLDB,INFORMIX,ORACLE,POSTGRES_15,SNOWFLAKE,SQLSERVER,SYBASE,TERADATA,VERTICA}) @NotNull MergeMatchedSetMoreStep<R> set(Record record) Set multiple values forUPDATE
in theMERGE
statement'sWHEN MATCHED
clause.This is the same as calling
set(Map)
with the argument record treated as aMap<Field<?>, Object>
, except that theRecord.touched()
flags (orRecord.modified()
flags, depending on the query'sSettings.getRecordDirtyTracking()
configuration) are taken into consideration in order to update only touched (or modified) values.- See Also:
-