db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
Subject Re: [jira] Commented: (DERBY-253) Client should throw not implemented exception for depricated setUnicodeStream/getUnicodeStream
Date Wed, 01 Jun 2005 15:14:28 GMT
Olav Sandstaa (JIRA) wrote:

>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. 
>
>  
>
Hi Olav,

I updated the Jira entry so it is (hopefully)  more clear.  It had some
out of date test information.
I think parameterMapping is the right place to test these calls.  They
should throw not implemented exceptions for both embedded and client.  I
believe they already do for embedded.  It would be good if the client
matches the embedded SQLState for this exception.

Kathey





Mime
View raw message