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, 21 Apr 2006 12:29:06 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1180?page=all ]

Kristian Waagan updated DERBY-1180:
-----------------------------------

    Attachment: derby-1180-1a-embedded.diff
                derby-1180-1a-embedded.stat

'derby-1180-1a-embedded.diff' addresses missing JDBC4 signatures on the embedded side. There
are still 3 missing signatures reported by jdbc4/VerifySignatures.junit, but these will go
away when another bug is fixed (don't know Jira number).

Tests have been written for most of the methods added, except for the Clob/Blob methods and
the Brokered* classes. All tests will be submitted with the patch for the network client side.
The tests I do have run cleanly, and since all these methods throw not implemented, I think
it is okay to commit this patch before the tests are in place. Adding the tests now will cause
errors when running with DerbyNetClient. 

Rick's patches ('bug1180_embeddedStarter.diff' and 'bug1180_1.diff') have either been incorporated
into this patch or is committed elsewhere (DERBY-940?). There are no tests for the getParameterMetaData-methods,
so I created DERBY-1242 to track this.

Suite jdbc40 ran without failures.

Patch ready for 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: 10.2.0.0
>     Reporter: Rick Hillegas
>     Assignee: Kristian Waagan
>  Attachments: bug1180_1.diff, bug1180_embeddedStarter.diff, derby-1180-1a-embedded.diff,
derby-1180-1a-embedded.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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message