Re: [jira] Commented: (DERBY-1283) Fill in a deprecated but mandatory JDBC3 method: PreparedStatement.setUnicodeStream()

[Lance J. Andersen]

Actually the intent has always been there, just not clearly articulated. If a driver claims to support a data type such as Blob/Clob/Array...etc... it is expected that all methods on the interface are fully implemented and just do not throw an exception. It is just JDBC 4.0 that i am taking the time to make this clearer. If your driver or backend does not support the datatype then all methods on the interface must throw SQLFeatureNotSupportedException for JDBC 4 and SQLException for JDBC 3. Daniel John Debrunner wrote: Lance J. Andersen wrote: The compliance chapter has seen significant clarifications for JDBC 4 to clarify what is and is not required. If you implement and interface for a data type such as blob/clob all methods must be implemented otherwise you do not support the data type. So this is a JDBC 4.0 requirement, not a JDBC 3.0 requirement. Just trying to understand. Dan.