db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-942) Add JDBC4 Ease of Development Support
Date Thu, 01 Jun 2006 12:19:31 GMT
     [ http://issues.apache.org/jira/browse/DERBY-942?page=all ]

Kristian Waagan updated DERBY-942:

    Attachment: derby-942-connectiontest-rewrite.stat

'derby-942-connectiontest-rewrite.diff' rewrites ConnectionTest to only test a single connection
implementation class. Which class is tested, depends on what 'BaseJDBCTestCase.getConnection()'
The test is also added to the 'jdbcxa40' suite, but I could not see this suite being run as
part of any other suites (including derbyall).
The parts that were removed from the test, can be tested by using the 'derbyTesting.xa.single'
property instead. I assume this will be used when the jdbcxa40 suite is being run.

Suite jdbc40 passed without failures. Derbyall has not been run for this JDBC4-only patch.

Please commit.

> Add JDBC4 Ease of Development Support
> -------------------------------------
>          Key: DERBY-942
>          URL: http://issues.apache.org/jira/browse/DERBY-942
>      Project: Derby
>         Type: New Feature

>   Components: JDBC
>     Reporter: Rick Hillegas
>     Assignee: Anurag Shekhar
>      Fix For:
>  Attachments: TestDbMetaData.diff, TestQueryObject.diff, derby-942-connectiontest-rewrite.diff,
derby-942-connectiontest-rewrite.stat, derby-942-enable-connectionTest.diff, derby-942-enable-connectionTest.stat,
derby-942.diff, derby-942_2.diff
> As described in the JDBC 4 spec, sections 20.1, 20.2, and 3.1.
> The Ease of Development extensions provide a way to create tabular DataSets from queries
and tuple signatures. The jdk ships with a factory for creating these DataSets, which is a
class which implements the QueryObjectGenerator interface. A database can write its own custom
QueryObjectGenerator, or just ship with the default, jdk-shipped version. For this task, we
will simply wire the default jdk-shipped factory into the appropriate methods: Connection.createQueryObject()
and DataSource.createQueryObject().

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