[#7310] Improve documentation

This commit is contained in:
lukaseder 2018-04-04 08:54:25 +02:00
parent 8965e98149
commit 38841ea8d5
3 changed files with 30 additions and 3 deletions

View File

@ -16422,7 +16422,16 @@ public class CaseInsensitiveOrderProvider implements Comparator<Definition> {
</ul>
<p>
Semantically, the above types are exactly equivalent, although the new types do away with the many flaws of the JDBC types.
Semantically, the above types are exactly equivalent, although the new types do away with the many flaws of the JDBC types. If there is no JDBC type for an equivalent JSR 310 type, then the JSR 310 type is generated by default. This includes
</p>
<ul>
<li><reference class="java.time.OffsetTime"/> (for SQL <code>TIME WITH TIME ZONE</code>)</li>
<li><reference class="java.time.OffsetDateTime"/> (for SQL <code>TIMESTAMP WITH TIME ZONE</code>)</li>
</ul>
<p>
To get more fine-grained control of the above, you may wish to consider applying <reference id="data-type-rewrites" title="data type rewriting"/>.
</p>
<p>

View File

@ -16607,7 +16607,16 @@ public class CaseInsensitiveOrderProvider implements Comparator<Definition> {
</ul>
<p>
Semantically, the above types are exactly equivalent, although the new types do away with the many flaws of the JDBC types.
Semantically, the above types are exactly equivalent, although the new types do away with the many flaws of the JDBC types. If there is no JDBC type for an equivalent JSR 310 type, then the JSR 310 type is generated by default. This includes
</p>
<ul>
<li><reference class="java.time.OffsetTime"/> (for SQL <code>TIME WITH TIME ZONE</code>)</li>
<li><reference class="java.time.OffsetDateTime"/> (for SQL <code>TIMESTAMP WITH TIME ZONE</code>)</li>
</ul>
<p>
To get more fine-grained control of the above, you may wish to consider applying <reference id="data-type-rewrites" title="data type rewriting"/>.
</p>
<p>

View File

@ -16123,7 +16123,16 @@ configuration {
</ul>
<p>
Semantically, the above types are exactly equivalent, although the new types do away with the many flaws of the JDBC types.
Semantically, the above types are exactly equivalent, although the new types do away with the many flaws of the JDBC types. If there is no JDBC type for an equivalent JSR 310 type, then the JSR 310 type is generated by default. This includes
</p>
<ul>
<li><reference class="java.time.OffsetTime"/> (for SQL <code>TIME WITH TIME ZONE</code>)</li>
<li><reference class="java.time.OffsetDateTime"/> (for SQL <code>TIMESTAMP WITH TIME ZONE</code>)</li>
</ul>
<p>
To get more fine-grained control of the above, you may wish to consider applying <reference id="data-type-rewrites" title="data type rewriting"/>.
</p>
<p>