[
https://issues.apache.org/jira/browse/DERBY-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6000:
---------------------------------
Attachment: derby-6000-08-aa-batchUpdateExceptionConstructor.diff
Attaching derby-6000-08-aa-batchUpdateExceptionConstructor.diff. This patch
adjusts how Derby constructs BatchUpdateExceptions. I am running tests now.
Despite https://jbs.oracle.com/bugs/browse/JDK-8004967 , you can test on Open
JDK 8 by specifying the -noverify switch on the java command line. When I did
this, I tripped across errors in the BatchUpdateTests caused by this behavior
of BatchUpdateException:
o If you use the new constructor which takes long update counts, then you can't
use initCause() to poke a cause into the BatchUpdateException.
This patch fixes those errors by reworking how Derby constructs
BatchUpdateExceptions.
Touches the following files:
------------
M java/engine/org/apache/derby/impl/jdbc/EmbedStatement.java
M java/engine/org/apache/derby/impl/jdbc/Util.java
Embedded changes.
------------
M java/client/org/apache/derby/client/net/ClientJDBCObjectFactoryImpl.java
M
java/client/org/apache/derby/client/net/ClientJDBCObjectFactoryImpl42.java
Client changes.
> 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
