[
https://issues.apache.org/jira/browse/DERBY-5488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13141226#comment-13141226
]
Rick Hillegas commented on DERBY-5488:
--------------------------------------
Thanks for helping me puzzle through these issues, Kristian. The default
behavior of these methods is to measure positions and lengths in characters (I
have just confirmed this with JDBC spec lead Lance Andersen). That's what Derby
does already and that seems to me to be the portable usage. What the new,
optional arguments let you do is ask the database to measure positions and
lengths in octets. I think that octet-lengths are not likely to be portable.
That is because the octet-lengths will vary depending on whether the engine
code is written in Java or C. For C databases, octet-lengths will vary
depending on the default encoding for the engine. I think we have a good
portability story here. Thanks.
> Add remaining JDBC 4.1 bits which did not appear in the Java 7 javadoc.
> -----------------------------------------------------------------------
>
> Key: DERBY-5488
> URL: https://issues.apache.org/jira/browse/DERBY-5488
> Project: Derby
> Issue Type: Improvement
> Components: JDBC, SQL
> Affects Versions: 10.9.0.0
> Reporter: Rick Hillegas
> Attachments: JDBC_4.1_Supplement.html
>
>
> In addition to the JDBC 4.1 bits which were visible in the Java 7 javadoc, a
> couple other items appear in the JDBC 4.1 Maintenance Review spec. This spec
> has been published on the JCP website at
> http://download.oracle.com/otndocs/jcp/jdbc-4_1-mrel-eval-spec/index.html. I
> will attach a functional spec for the remaining bits.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
