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] Commented: (DERBY-1253) Verify that we don't raise SQLFeatureNotSupportedException for mandatory methods
Date Wed, 03 May 2006 09:05:48 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1253?page=comments#action_12377540 ] 

Dyre Tjeldvoll commented on DERBY-1253:

Thanks for committing Rick.

> 1) Commented out the Blob/Clob exclusions because Lance has said that these methods are

Should we not comment out the Blob/Clob related methods in PreparedStatement and CallableStatement,
as well? From the spec it appears that they too are mandatory if you support Blob/Clob.

I'm unsure about Connection.create[BC]lob, though. The spec draft marks them as optional,
but does not have the same caveat which make the methods mandatory if you support the datatype.

2) Added Connection.createStruct() and createArray() to the exclusions list since Kristian
has filled these in now

Not sure I understand the last comment. If those methods have been added, you would want to
REMOVE them from the exclusion list, wouldn't you? Or do you mean that these methods now throw
Unsupported, and did not do so before?

> 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