db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olav Sandstaa (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-253) Client should throw not implemented exception for depricated setUnicodeStream/getUnicodeStream
Date Wed, 01 Jun 2005 14:41:52 GMT
     [ http://issues.apache.org/jira/browse/DERBY-253?page=comments#action_66736 ]
Olav Sandstaa commented on DERBY-253:

I have had some problems trying to reproduce this problem based on the description given in
the Jira report. 

The report refers to the a test named "conn/blobclob4BLOB.java", but I am unable to locate
any test with name. There is a test named "jdbcapi/blobclob4BLOB.java" and initially I thought
this was the right test to use, but I can not find that this test is doing any calls to setUnicodeStream/getUnicodeStream.

There is a test called "jdbcapi/parameterMapping.java" that does a lot of calls to setUnicodeStream/getUnicodeStream
which are disabled when running with the network client. I suspect this is the right test
to use for reproducing this problem. 

Since I am new to the Derby code and test harness I would appreciate that someone told me
if I am on the wrong track to reproduce this problem.

> 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:
>     Reporter: Kathey Marsden
>     Assignee: Olav Sandstaa
>     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:
For more information on JIRA, see:

View raw message