You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <de...@db.apache.org> on 2005/05/02 18:16:12 UTC
[jira] Commented: (DERBY-253) Client should throw not implemented exception for depricated setUnicodeStream/getUnicodeStream
[ http://issues.apache.org/jira/browse/DERBY-253?page=comments#action_64262 ]
Daniel John Debrunner commented on DERBY-253:
---------------------------------------------
What should the behaviour be? I think unimplemented is correct, implementing methods that are not intended to be used seems wrong.
> Client should throw not implemented exception for depricated setUnicodeStream/getUnicodeStream
> ----------------------------------------------------------------------------------------------
>
> Key: DERBY-253
> URL: http://issues.apache.org/jira/browse/DERBY-253
> Project: Derby
> Type: Bug
> Components: Network Client
> Versions: 10.1.0.0
> Reporter: Kathey Marsden
> Priority: Minor
>
> setUnicodeStream and getUnicodeStream are depricated API's and
> not supported for Network client but can throw unexpected
> error messages.
> To reproduce uncomment the "if (! isDB2jNet)" around unicode
> tests in conn/blobclob4BLOB.java
--
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
Re: [jira] Commented: (DERBY-253) Client should throw not implemented
exception for depricated setUnicodeStream/getUnicodeStream
Posted by Kathey Marsden <km...@sbcglobal.net>.
Lance J. Andersen wrote:
> There are still a fair amount of applications which utilize these
> methods. I am not removing these methods in JDBC 4 and infact I
> actually clarified the api docs for them.
>
> Derby should implement these IMHO.
We are making a new JDBC driver and these are deprecated methods. We
throw not implemented exceptions for embedded and right now in the
client, they are there but are broken (can cause protocol errors and
loss of connection). I guess if you wanted to spend a lot of time to
implement them for both embedded and client, I wouldn't object strongly
to having them, but in general my vote would be to throw a not
implemented exception like we do for embedded at least for now.
Thanks
Kathey
Re: [jira] Commented: (DERBY-253) Client should throw not implemented
exception for depricated setUnicodeStream/getUnicodeStream
Posted by "Lance J. Andersen" <La...@Sun.COM>.
There are still a fair amount of applications which utilize these
methods. I am not removing these methods in JDBC 4 and infact I
actually clarified the api docs for them.
Derby should implement these IMHO.
Regards
Lance
Daniel John Debrunner (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-253?page=comments#action_64262 ]
>
>Daniel John Debrunner commented on DERBY-253:
>---------------------------------------------
>
>What should the behaviour be? I think unimplemented is correct, implementing methods that are not intended to be used seems wrong.
>
>
>
>>Client should throw not implemented exception for depricated setUnicodeStream/getUnicodeStream
>>----------------------------------------------------------------------------------------------
>>
>> Key: DERBY-253
>> URL: http://issues.apache.org/jira/browse/DERBY-253
>> Project: Derby
>> Type: Bug
>> Components: Network Client
>> Versions: 10.1.0.0
>> Reporter: Kathey Marsden
>> Priority: Minor
>>
>>
>
>
>
>>setUnicodeStream and getUnicodeStream are depricated API's and
>>not supported for Network client but can throw unexpected
>>error messages.
>>To reproduce uncomment the "if (! isDB2jNet)" around unicode
>>tests in conn/blobclob4BLOB.java
>>
>>
>
>
>