db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anurag Shekhar (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-940) Add JDBC 4 Wrapper support
Date Fri, 10 Feb 2006 20:18:08 GMT
    [ http://issues.apache.org/jira/browse/DERBY-940?page=comments#action_12365963 ] 

Anurag Shekhar commented on DERBY-940:

JDBC 4.0 interface wrapper java.sql.Wrapper is meant to provide a
standurd way to access vender specific extention to jdbc calls. The
method isWrapperFor is to check if the object is implementing a
perticular object or not and unWrap returns the handle of the object
which implements the vender specific interface using which the vender
specific method can be invoked.

for example in case of oracle one can get the handle of
oracle.jdbc.OracleStatement and invoke oracle specific calls.

In case of derby we have two jdbc driver Emdeded driver Network Client
driver but these classes don't implement from common interface and in
most cases derby doesn't have any properitory set of interfaces
equivalent of jdbc interface. 

I am thinking to create new interface for all the classes required to
have wrapper impimentation. These interfaces will have non standurd
methods which are common to both types of driver. Doing this will make
sure the application code doesn't changes if the application want to
switch from embeded mode to network client of vice versa. 

These interface will also extend from respective sql interface so that
jdbc methods will be available to the application even after unwrapping
the object to derby interface. 

> Add JDBC 4 Wrapper support
> --------------------------
>          Key: DERBY-940
>          URL: http://issues.apache.org/jira/browse/DERBY-940
>      Project: Derby
>         Type: New Feature
>     Reporter: Rick Hillegas
>     Assignee: Anurag Shekhar

> As described in the JDBC 4 spec, sections 21 and 3.1.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message