[
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-05-aa-executeLargeUpdatePS.diff
Attaching derby-6000-05-aa-executeLargeUpdatePS.diff. This patch adds JDBC 4.2
large update support to PreparedStatements. I am running tests now.
This patch adds the following method to the embedded and client implementations
of PreparedStatement:
public long executeLargeUpdate()
Touches the following files:
--------------
M java/engine/org/apache/derby/iapi/jdbc/BrokeredPreparedStatement.java
M java/engine/org/apache/derby/iapi/jdbc/EnginePreparedStatement.java
M java/engine/org/apache/derby/impl/jdbc/EmbedPreparedStatement.java
Embedded changes.
--------------
M java/client/org/apache/derby/client/am/PreparedStatement.java
M java/client/org/apache/derby/client/am/LogicalPreparedStatement.java
Client changes.
--------------
M
java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/StatementTest.java
M
java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/PreparedStatementTest.java
New tests.
> 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, 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
