[#DERBY-253] Client should throw not implemented exception for depricated setUnicodeStream/getUnicodeStream

Derby

Client should throw not implemented exception for depricated setUnicodeStream/getUnicodeStream

Created: 01/May/05 01:33 PM Updated: 14/May/07 04:38 PM

Return to search

Component/s:

JDBC, Network Client

Affects Version/s:

10.1.1.0

Fix Version/s:

10.2.1.6

Time Tracking:

Not Specified

File Attachments:

	File Name	Date Attached	Attached By	Size
	derby253.diff	2006-07-12 07:55 PM	Olav Sandstaa	30 kB

Issue Links:

Reference

This issue is related to:

~~DERBY-1615~~ Rewrite the Clob implementation in the client driver

Issue & fix info:	Release Note Needed
Resolution Date:	13/Jul/06 05:42 PM

Description

« Hide

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

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

Repository	Revision	Date	User	Message
ASF	#421570	Thu Jul 13 09:55:04 UTC 2006	kahatlen	~~DERBY-253~~: Client should throw not implemented exception for depricated setUnicodeStream/getUnicodeStream 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. Patch contributed by Olav Sandstå.
				Files Changed
				MODIFY /db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/master/DerbyNetClient/parameterMapping.out MODIFY /db/derby/code/trunk/java/client/org/apache/derby/client/am/ResultSet.java MODIFY /db/derby/code/trunk/java/client/org/apache/derby/client/am/PreparedStatement.java