[ http://issues.apache.org/jira/browse/DERBY-1283?page=comments#action_12377820 ]
Rick Hillegas commented on DERBY-1283: -------------------------------------- Dan's comment kicked off a lively discussion on derby-dev, under the subject line "[jira] Commented: (DERBY-1283) Fill in a deprecated but mandatory JDBC3 method: PreparedStatement.setUnicodeStream()". I would like to capture some of that discussion here. Lance says: Very simple, just because it is deprecated, it does not mean it can be ignored. Bottom line, it is required to be there. There are no plans to remove these methods from JDBC. Lance continues later on: Prior versions of the JDBC specification were not clear or concise as to what a developer and or a user could expect. This as a JDBC driver developer while at Sybase i found extremely frustrating. These methods have been in the JDBC spec since 1.0. We will not be removing them from the spec and just because something is deprecated, it does not mean that it should not be implemented or ignored. It just means that there are alternative methods that are recommended. Also in my working with the Java SE team, they discourage deprecating methods via the javadoc tag as it adds unnecessary noise at compile time where as a simple note in the spec/javadoc can point users to the preferred method. As far as your question below, it is impossible to determine what methods are and are not required from the JDBC 3.0 specification. This is something that i have addressed in JDBC 4.0. Dan then notes: Then this is about JDBC 4.0 compliance and not JDBC 3.0. I don't see how you can change the rules for JDBC 3.0 compliance with a release of the JDBC 4.0 specification. I believe that Sun in the past has confirmed JDBC drivers including Derby & Cloudscape pre-open source as being JDBC 3.0 compliant, seems wrong to say, oh now there's additional work to do. To which Lance responds: There has never been a TCK to validate JDBC compliance end to end. What there has been is a test suite to validate the requirements of a JDBC driver in a J2EE environment. and the latest version is for J2EE 1.3 with JDBC 2.x. Passing this allows for a tagline to be used by driver vendors. > Fill in a deprecated but mandatory JDBC3 method: > PreparedStatement.setUnicodeStream() > ------------------------------------------------------------------------------------- > > Key: DERBY-1283 > URL: http://issues.apache.org/jira/browse/DERBY-1283 > Project: Derby > Type: Improvement > Components: JDBC > Versions: 10.2.0.0 > Reporter: Rick Hillegas > Fix For: 10.2.0.0 > > For JDBC3 compliance, implement this method. Right now it throws a > NotImplemented exception. -- 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
