Java class for UpdateUnchangedRecords. + * + *
The following schema fragment specifies the expected content contained within this class. + *
+ *
+ * <simpleType name="UpdateUnchangedRecords">
+ * <restriction base="{http://www.w3.org/2001/XMLSchema}string">
+ * <enumeration value="NEVER"/>
+ * <enumeration value="SET_PRIMARY_KEY_TO_ITSELF"/>
+ * <enumeration value="SET_NON_PRIMARY_KEY_TO_THEMSELVES"/>
+ * <enumeration value="SET_NON_PRIMARY_KEY_TO_RECORD_VALUES"/>
+ * </restriction>
+ * </simpleType>
+ *
+ *
+ */
+@XmlType(name = "UpdateUnchangedRecords")
+@XmlEnum
+public enum UpdateUnchangedRecords {
+
+ NEVER,
+ SET_PRIMARY_KEY_TO_ITSELF,
+ SET_NON_PRIMARY_KEY_TO_THEMSELVES,
+ SET_NON_PRIMARY_KEY_TO_RECORD_VALUES;
+
+ public String value() {
+ return name();
+ }
+
+ public static UpdateUnchangedRecords fromValue(String v) {
+ return valueOf(v);
+ }
+
+}
diff --git a/jOOQ/src/main/java/org/jooq/impl/UpdatableRecordImpl.java b/jOOQ/src/main/java/org/jooq/impl/UpdatableRecordImpl.java
index 1fd365f39c..30e9a52181 100644
--- a/jOOQ/src/main/java/org/jooq/impl/UpdatableRecordImpl.java
+++ b/jOOQ/src/main/java/org/jooq/impl/UpdatableRecordImpl.java
@@ -38,6 +38,7 @@
package org.jooq.impl;
import static java.lang.Boolean.TRUE;
+import static java.util.Arrays.asList;
// ...
import static org.jooq.SQLDialect.SQLITE;
import static org.jooq.conf.SettingsTools.updatablePrimaryKeys;
@@ -308,13 +309,15 @@ public class UpdatableRecordImpl+Use this for single-schema environments, or when all objects are made +available using synonyms]]>
+This setting does not affect any plain SQL usage.]]>
+This setting does not affect any plain SQL usage.]]>
+@deprecated - 3.12.0 - [#5909] - Use {@link RenderQuotedNames} and {@link RenderNameCase} instead.]]>
:name (such as supported by Oracle, JPA, Spring), but
+vendor specific parameters may look differently. This flag can be used to determine the prefix to be
+used by named parameters, such as @ for SQL Server's @name or $
+for PostgreSQL's $name.
+
+"Named indexed" parameters can be obtained in the same way by specifingy {@code ParamType#NAMED} and not
+providing a name to parameters, resulting in :1 or @1 or $1, etc.]]>
INNER JOIN, if it is optional in the output dialect.]]>OUTER JOIN, if it is optional in the output dialect.]]>
+Older databases did not support OFFSET .. FETCH pagination, so jOOQ emulates it using derived
+tables and ROWNUM (Oracle 11g and older) or ROW_NUMBER() (e.g. DB2,
+SQL Server, etc.) filtering. While these subqueries are ordered, the ordering is not
+guaranteed to be stable in the outer most queries. It may be stable (and e.g. in Oracle,
+it mostly is, if queries are not parallel, or joined to other queries, etc.), so the excess
+ORDER BY clause may add some additional performance overhead. This setting forces
+jOOQ to not generate the additional ORDER BY clause.
+
+For details, see https://github.com/jOOQ/jOOQ/issues/7609.]]>
OUTPUT clause.
+
+SQL Server supports an OUTPUT clause in most DML statements, whose behaviour
+is almost identical to RETURNING in Firebird, Oracle, PostgreSQL. Users who
+want to prevent jOOQ from rendering this OUTPUT clause can deactivate this flag
+to revert to jOOQ calling {@code java.sql.Statement#getGeneratedKeys()} instead, which
+is only supported for single row inserts.
+
+This OUTPUT clause does not support fetching trigger generated values. In order
+to fetch trigger generated values, {@link #fetchTriggerValuesAfterSQLServerOutput} needs to
+be enabled as well.
+
+For details, see https://github.com/jOOQ/jOOQ/issues/4498.]]>
false jOOQ will only render parenthesis pairs around queries combined with set operators when required.
+This is for example the case when set operators are nested, when non-associative operators like EXCEPT are used, or when the queries are rendered as derived tables.
+
+When this setting is set to true the queries combined with set operators will always be surrounded by a parenthesis pair.
+
+For details, see https://github.com/jOOQ/jOOQ/issues/3676 and https://github.com/jOOQ/jOOQ/issues/9751.]]>
+SQL Server OUTPUT statements do not support fetching trigger generated values.
+This is a limitation of the {@link #renderOutputForSQLServerReturningClause}. An additional
+MERGE statement can run a second query if (and only if) the primary key has been
+included in the OUTPUT clause.
+
+For details, see https://github.com/jOOQ/jOOQ/issues/4498.]]>
(+) (Oracle, DB2) or *= (SQL Server) for outer join
+support. For backwards compatibility with older RDBMS versions, ANSI joins in jOOQ code may be
+converted to equivalent table lists in generated SQL using this flag.
++This flag has a limited implementation that supports inner joins (in most cases) and outer joins +(only for simple comparison predicates). +
+This feature is available in the commercial distribution only.]]>
(+) (Oracle, DB2) or *= (SQL Server) for outer join
+support. Migrating such join syntax is tedious. The jOOQ parser can parse the old syntax and
+this flag enables the transformation to ANSI join syntax.
++This flag has not been implemented yet! +
+This feature is available in the commercial distribution only.]]>