[
https://issues.apache.org/jira/browse/DERBY-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573481#comment-13573481
]
Rick Hillegas commented on DERBY-6000:
--------------------------------------
Thanks for looking at that patch, Knut. I was working from the specdiffs, which
give the method name as getMaxLogicalLOBSize(). I've tripped across some other
cases where names in the specdiffs don't agree with what's in the actual Open
JDK 8 classes. I'll correct this one.
I'll ask Lance if he has any advice about what this method should return on
Derby. Seems to me there are at least 2 theories about this:
o 4294967294 - The maximum number of bytes which an in-memory CLOB can consume.
This is misleading for people interested in the maximum number of bytes which
can be stored in the database.
o 2147483647 - The maximum number of bytes in a LOB stored in the database.
This is misleading for people who are interested in the memory representation.
Thanks,
-Rick
> Implement support for JDBC 4.2
> ------------------------------
>
> Key: DERBY-6000
> URL: https://issues.apache.org/jira/browse/DERBY-6000
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
> Reporter: Rick Hillegas
> Attachments: derby-6000-01-aa-executeLargeUpdateEmbedded.diff,
> derby-6000-02-ad-executeLargeUpdateClient.diff,
> derby-6000-03-aa-executeLargeBatch.diff,
> derby-6000-04-aa-setLargeMaxRows.diff,
> derby-6000-05-aa-executeLargeUpdatePS.diff,
> derby-6000-06-aa-DatabaseMetaData.diff,
> derby-6000-07-ab-batchUpdateException.diff,
> derby-6000-08-aa-batchUpdateExceptionConstructor.diff, JDBC_4.2_Changes.html
>
>
> Open JDK 8 will include maintenance rev 4.2 of JDBC. The public discussion of
> JDBC 4.2 will take place here: http://openjdk.java.net/jeps/170. We will want
> to build Derby support for JDBC 4.2 after a public spec appears. At this
> time, it is unclear what Derby release will carry this support.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
