db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-253) Client should throw not implemented exception for depricated setUnicodeStream/getUnicodeStream
Date Thu, 13 Jul 2006 11:15:34 GMT
     [ http://issues.apache.org/jira/browse/DERBY-253?page=all ]

Knut Anders Hatlen updated DERBY-253:

    Derby Info: [Release Note Needed]

Yes, I think we should mention this in the release notes. Here's my proposal:


PreparedStatement.setUnicodeStream() and ResultSet.getUnicodeStream()
throw SQLException when invoked after upgrading to Apache Derby 10.2.


Calling either of these methods will result in an exception with
SQLSTATE 0A000 and message: "Feature not implemented: ..."


PreparedStatement.setUnicodeStream() and ResultSet.getUnicodeStream()
have been deprecated since JDBC 2.0. Derby's implemetation of these
methods was broken, and it was decided that the methods should throw a
not-implemented exception instead of being fixed.


This was an intentional change. No Derby product solution is offered.


Use setCharacterStream() and getCharacterStream() instead of
setUnicodeStream() and getUnicodeStream().

> 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, JDBC
>     Versions:
>     Reporter: Kathey Marsden
>     Assignee: Olav Sandstaa
>      Fix For:
>  Attachments: derby253.diff
> setUnicodeStream and getUnicodeStream are deprecated API's 
> Network client
> PreparedStatement.setUnicodeStream() and ResultSet.getUnicodeStream() should throw not
implemented exceptions rather than trying to handle these calls.
> Note: The current client implementation of setUnicodeStream() and getUnicodeStream()
are broken and can cause unexpected errors

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