db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dyre Tjeldvoll (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1253) Verify that we don't raise SQLFeatureNotSupportedException for mandatory methods
Date Tue, 02 May 2006 17:11:47 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1253?page=all ]

Dyre Tjeldvoll updated DERBY-1253:

    Attachment: derby-1253.v1.diff

Attaching a patch that updates the exclude map with additional interfaces and methods.
It still fails, but complains about fewer unsupported methods. I have run the test in embedded
and DerbyNetClient, but I have not run any other tests.

The indentation mode that I use doesn't seem to grok such complicated array initializations,
so the indentation is a bit strange in some places. And I have not even tried to avoid lines
longer than 80 chars here, since that would make the exclude map initialization unreadable...

I'm a bit unsure about what to accept for Blob/Clob. All the methods in these interfaces are
allowed to throw NotImplemented, but I'm wondering if the spec allows only some of them to
be not implemented?

> Verify that we don't raise SQLFeatureNotSupportedException for mandatory methods
> --------------------------------------------------------------------------------
>          Key: DERBY-1253
>          URL: http://issues.apache.org/jira/browse/DERBY-1253
>      Project: Derby
>         Type: Improvement

>   Components: JDBC
>     Versions:
>     Reporter: Rick Hillegas
>     Assignee: Dyre Tjeldvoll
>      Fix For:
>  Attachments: bug1253_verifier.diff, bug1253_verifier2.diff, derby-1253.v1.diff, derby-1253.v1.stat
> The jdk16 javadoc marks optional methods as being able to raise SQLFeatureNotSupportedException.
Make sure that we don't raise this exception for mandatory methods--unless we clearly understand
why we have chosen to deviate from the JDBC spec.

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