[
https://issues.apache.org/jira/browse/DERBY-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576959#comment-13576959
]
Rick Hillegas commented on DERBY-6000:
--------------------------------------
Concerning DatabaseMetaData.getMaxLogicalLobSize(), JDBC spec lead Lance
Andersen suggests that Derby should return 0, the default, which means
"unknown".
> 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,
> derby-6000-09-ac-setObjectPS.diff,
> derby-6000-10-aa-rename_getMaxLogicalLobSize.diff,
> derby-6000-11-aa-ResultSet.updateObject.diff,
> derby-6000-12-aa-CallableStatement.registerOutParameter.diff,
> derby-6000-12-ab-CallableStatement.registerOutParameter.diff,
> derby-6000-13-aa-fixJavadoc.diff, derby-6000-14-aa-unsupportedVetter.diff,
> derby-6000-15-aa-CallableStatement.setObject.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
