Forgot to mention that I have run derbyall with no errors using JDK 1.5
on Solaris 10 x86.
..olav
Olav Sandstaa (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-253?page=all ]
Olav Sandstaa updated DERBY-253:
--------------------------------
Attachment: derby253.diff
This patch replaces the existing implementation of setUnicodeStream and
getUnicodeStream in the client driver to just throw a SQL exception with SQL
state equal to feature not implemented.
The following files are changed:
M
java/testing/org/apache/derbyTesting/functionTests/master/DerbyNetClient/parameterMapping.out
M java/client/org/apache/derby/client/am/PreparedStatement.java
M java/client/org/apache/derby/client/am/ResultSet.java
The patch is ready for review and commit.
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: 10.1.1.0
Reporter: Kathey Marsden
Assignee: Olav Sandstaa
Fix For: 10.2.0.0
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
