[ 
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-12-ab-CallableStatement.registerOutParameter.diff

Tests passed cleanly except that they stumbled over a case which canonized the 
previous wrong behavior of CallableStatement.registerOutParameter(int, int, 
String). The first rev of this patch corrected the behavior of that method. The 
wrong behavior canon was added by work on DERBY-1184.

Attaching a new version of the patch, which removes the offending test case: 
derby-6000-12-ab-CallableStatement.registerOutParameter. Committed at 
subversion revision 1444960.

Touches the following additional file:

M       
java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/CallableTest.java

                
> 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, 
> 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

Reply via email to