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

Attaching derby-6000-12-aa-CallableStatement.registerOutParameter.diff. This 
patch adds the new JDBC 4.2 registerOutParameter overloads to 
CallableStatement. I am running tests now.

This patch adds the following new overloads to the embedded and client 
implementations of java.sql.CallableStatement:

    public void registerOutParameter(int parameterIndex, SQLType sqlType)
    public void registerOutParameter(int parameterIndex, SQLType sqlType,int 
scale)
    public void registerOutParameter(int parameterIndex, SQLType sqlType, 
java.lang.String typeName)
    public void registerOutParameter(java.lang.String parameterName, SQLType 
sqlType)
    public void registerOutParameter(java.lang.String parameterName, SQLType 
sqlType, int scale)
    public void registerOutParameter(java.lang.String parameterName, SQLType 
sqlType, java.lang.String typeName)

This patch also corrects the behavior of the following CallableStatement 
methods. Derby was throwing an "unimplemented feature" exception. For drivers 
which don't need the typeName argument, the correct behavior is to ignore it:

    public void registerOutParameter(int parameterIndex, int sqlType, 
java.lang.String typeName)
    public void registerOutParameter(java.lang.String parameterName, int 
sqlType, java.lang.String typeName)


Touches the following files:

-------------

A       java/engine/org/apache/derby/iapi/jdbc/BrokeredCallableStatement42.java
M       java/engine/org/apache/derby/iapi/jdbc/BrokeredConnection40.java
M       java/engine/org/apache/derby/iapi/jdbc/BrokeredConnection42.java
A       java/engine/org/apache/derby/impl/jdbc/EmbedCallableStatement42.java
M       java/engine/org/apache/derby/impl/jdbc/EmbedCallableStatement.java
M       java/engine/org/apache/derby/jdbc/Driver42.java

Embedded changes.

-------------

M       
java/client/org/apache/derby/client/net/ClientJDBCObjectFactoryImpl42.java
A       java/client/org/apache/derby/client/am/LogicalCallableStatement42.java
A       java/client/org/apache/derby/client/am/CallableStatement42.java
M       java/client/org/apache/derby/client/am/CallableStatement.java

Client changes.

-------------

M       
java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/XA40Test.java
M       
java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/PreparedStatementTest42.java

New tests. At this point, PreparedStatementTest42 should probably be renamed to 
something like SQLTypeTest42. That can be done in a later patch.

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