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] Updated: (DERBY-1051) A new method in CommonDataSource added which is not present in jdbc4 stub classes
Date Sun, 26 Feb 2006 17:07:05 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1051?page=all ]

Anurag Shekhar updated DERBY-1051:

    Attachment: derby-1051.diff

Description of the patch
Added new methods to EmbeddedDataSource40 and clientDataSource40 

Added new class

All these classes extend from Datasource too so added methods which are not ment for these
These methods will throw exception with sql state set to NOT_IMPELMENTED.
Added test case to check if they throw expected exception.

added entry in tools/jar/extraDBMSclasses.properties to include the jdbc40 DataSource classes
in derby.jar
added additonal target in build.xml to uncomment class name of jdbc40 DataSource classes in
if built with jdk1.6 support

> A new method in CommonDataSource added which is not present in jdbc4 stub classes
> ---------------------------------------------------------------------------------
>          Key: DERBY-1051
>          URL: http://issues.apache.org/jira/browse/DERBY-1051
>      Project: Derby
>         Type: Improvement
>  Environment: all
>     Reporter: Anurag Shekhar
>     Assignee: Anurag Shekhar
>  Attachments: derby-1051.diff
> A new method getQueryObjectGenerator is added in CommonDataSource. This effects all the
DataSource (XADataSource, PooledDataSource and DataSource). Because of this new method we
will need to have seperate classes for all the DataSouce Implementation for jdbc4 and privious
version as the return type QueryObjectGenerator is a class introduced in jdbc4.
> Spec allows the implementation to return null if no QueryObjectGenerator implementation
is provided by the driver.

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