db-derby-dev mailing list archives

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

Rick Hillegas updated DERBY-1253:

    Attachment: bug1253_wireIn.diff

Attaching bug1253_wireIn.diff. This adds the UnsupportedVetter test to the jdbc4 test suite.
Committed at subversion revision 410694. Touches the following files:

M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\UnsupportedVetter.java
M      java\testing\org\apache\derbyTesting\functionTests\suites\jdbc40.runall

Added special markers to the mandatory LOB-supporting methods which Derby does not implement.
See the class header of UnsupportedVetter for instructions on how to vet strictly and disclose
this compliance gap.

At this point, this test will track additional flexing of the JDBC4 spec.

> 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_forwarding.diff, bug1253_verifier.diff, bug1253_verifier2.diff,
bug1253_verifier3_complianceChapter.diff, bug1253_verifier4_networkResultSet.diff, bug1253_wireIn.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