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-1180) Add vacuous implementations of missing JDBC4 methods
Date Fri, 28 Apr 2006 15:26:38 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1180?page=all ]

Kristian Waagan updated DERBY-1180:

    Attachment: derby-1180-4a-logcialconnection_and_tests.diff

'derby-1180-4a-logcialconnection_and_tests.diff' is the last planned patch for this issue.
It fixes the missing method signatures in LogicalConneciton. I had to create a factory method
and add a new file.

I have also added a connection test suite, testing both the "regular" conneciton, and the
real connection for PooledConnection and XAConnection. The test is not yet enabled, as there
are two failures: createQueryObject is not implemented in Logical-/BrokeredConnection40. EmbedBrokeredConnectionWrapperTest
is deleted, the tests themselves are moved into ConnectionTest.

There are now 6 missing signatures for client (createStruct/-Array) and 8 for embedded (createStruct/-Array
+ is-/setPoolable). These will be fixed as part of other Jira issues. jdbc40 suite run without
failures on both DerbyNetClient and embedded.

Please review/commit.

> Add vacuous implementations of missing JDBC4 methods
> ----------------------------------------------------
>          Key: DERBY-1180
>          URL: http://issues.apache.org/jira/browse/DERBY-1180
>      Project: Derby
>         Type: New Feature

>   Components: JDBC
>     Versions:
>     Reporter: Rick Hillegas
>     Assignee: Kristian Waagan
>  Attachments: bug1180_1.diff, bug1180_embeddedStarter.diff, derby-1180-1a-embedded.diff,
derby-1180-1a-embedded.stat, derby-1180-2a-client.diff, derby-1180-2a-client.stat, derby-1180-3a-testing.diff,
derby-1180-3a-testing.stat, derby-1180-4a-logcialconnection_and_tests.diff, derby-1180-4a-logcialconnection_and_tests.stat
> If you run the VerifySignatures test, you will see a lot of JDBC4 methods which don't
appear in our implementation yet. We need to add vacuous implementations for these methods
which raise SQLFeatureNotSupportedExceptions. Most of these methods won't need any more attention
because they refer to features (like xml and national strings) which we don't support. We
will open additional JIRAs for the methods which need non-vacuous implementations.

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