[ http://issues.apache.org/jira/browse/DERBY-1283?page=comments#action_12377662 ]
Daniel John Debrunner commented on DERBY-1283: ---------------------------------------------- Seems strange to implement a deprecated api. Section 6.7 says "Deprecation refers to a class, interface, constructor, method or field that is no longer recommended and may cease to exist in a future version." Why would Derby implement a method we don't want applications to use? > 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
