Rick Hillegas wrote:
> Lance J. Andersen wrote:
> ...
>
>>
>> If you want to ask the question a different way and revisit whether
>> setUniCodeStream can be considered optional, then do so please and i
>> will consider it and have that discussion with the EG. JDBC drivers
>> that have been around since the early days implemented this method.
>>
>
> I think this would be a useful discussion to have with the EG. It
> would be great if deprecation made a method optional even though the
> method remained in the api.
>
I agree that it would be a good discussion to have and honestly I don't
have a strong opinion one way or another about how it should be. I do
think that regardless of whether deprecation makes a method optional or
not, it would be really good to have clear wording somewhere saying that
it does or does not. I am guessing there are folks that are just as in
the dark as I have been that "deprecated but mandatory" methods exist.
Kathey
|