[ http://issues.apache.org/jira/browse/DERBY-253?page=comments#action_12359043 ]
Lance Andersen commented on DERBY-253: -------------------------------------- If you are not going to implement this feature, it should throw a SQLException per section 6.2 of the JDBC 3.0 spec (same requirement in JDBC 4 though we are considering adding a new non-transient SQLException as there appears to be a SQLState that we can use... this is under discussion) > 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.1.0 > Reporter: Kathey Marsden > Assignee: Olav Sandstaa > Priority: Minor > > 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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
