github/jooq
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[jOOQ/jOOQ#16484] Fix Javadoc of Settings.renderCoalesceToEmptyStringInConcat

Browse Source
This commit is contained in:
Lukas Eder 2024-03-19 16:28:21 +01:00
parent 1490028bd2
commit 5ad5f81ed2
2 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
jOOQ/src/main/java/org/jooq/conf/Settings.java
View File

@ -1140,10 +1140,10 @@ public class Settings
}
/**
* Whether stored function calls should be wrapped in scalar subqueries.
* Whether string concatenation operands should be coalesced to empty strings.
* <p>
* Oracle 11g (and potentially, other databases too) implements scalar subquery caching. With this flag
* set to true, users can automatically profit from this feature in all SQL statements.
* Some dialects treat <code>NULL</code> values as empty strings when concatenating strings (e.g. Oracle). For
* compatibility reasons, this flag allows for replicating this behaviour also elsewhere.
* <p>
* This feature is available in the commercial distribution only.
*
@ -1157,10 +1157,10 @@ public class Settings
}
/**
* Whether stored function calls should be wrapped in scalar subqueries.
* Whether string concatenation operands should be coalesced to empty strings.
* <p>
* Oracle 11g (and potentially, other databases too) implements scalar subquery caching. With this flag
* set to true, users can automatically profit from this feature in all SQL statements.
* Some dialects treat <code>NULL</code> values as empty strings when concatenating strings (e.g. Oracle). For
* compatibility reasons, this flag allows for replicating this behaviour also elsewhere.
* <p>
* This feature is available in the commercial distribution only.
*
@ -6995,10 +6995,10 @@ public class Settings
}
/**
* Whether stored function calls should be wrapped in scalar subqueries.
* Whether string concatenation operands should be coalesced to empty strings.
* <p>
* Oracle 11g (and potentially, other databases too) implements scalar subquery caching. With this flag
* set to true, users can automatically profit from this feature in all SQL statements.
* Some dialects treat <code>NULL</code> values as empty strings when concatenating strings (e.g. Oracle). For
* compatibility reasons, this flag allows for replicating this behaviour also elsewhere.
* <p>
* This feature is available in the commercial distribution only.
*

6
jOOQ/src/main/resources/org/jooq/xsd/jooq-runtime-3.20.0.xsd
View File

@ -195,10 +195,10 @@ unless DML joins are supported.]]></jxb:javadoc></jxb:property></appinfo></annot
</element>
<element name="renderCoalesceToEmptyStringInConcat" type="boolean" minOccurs="0" maxOccurs="1" default="false">
<annotation><appinfo><jxb:property><jxb:javadoc><![CDATA[Whether stored function calls should be wrapped in scalar subqueries.
<annotation><appinfo><jxb:property><jxb:javadoc><![CDATA[Whether string concatenation operands should be coalesced to empty strings.
<p>
Oracle 11g (and potentially, other databases too) implements scalar subquery caching. With this flag
set to true, users can automatically profit from this feature in all SQL statements.
Some dialects treat <code>NULL</code> values as empty strings when concatenating strings (e.g. Oracle). For
compatibility reasons, this flag allows for replicating this behaviour also elsewhere.
<p>
This feature is available in the commercial distribution only.]]></jxb:javadoc></jxb:property></appinfo></annotation>
</element>