db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lance J. Andersen" <Lance.Ander...@Sun.COM>
Subject Re: [jira] Commented: (DERBY-1283) Fill in a deprecated but mandatory JDBC3 method: PreparedStatement.setUnicodeStream()
Date Thu, 04 May 2006 02:17:11 GMT
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.

Daniel John Debrunner (JIRA) wrote:
>     [ 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.
>>     
>
>   

Mime
View raw message