Issue Details (XML | Word | Printable)

Key: DERBY-253
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Olav Sandstaa
Reporter: Kathey Marsden
Votes: 1
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
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:
  Size
File Licensed for inclusion in ASF works derby253.diff 2006-07-12 07:55 PM Olav Sandstaa 30 kB
Issue Links:
Reference
 

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: Ascending order - Click to sort in descending order
Daniel John Debrunner made changes - 04/May/05 06:45 AM
Field Original Value New Value
Comment [ 64262 ]
Olav Sandstaa made changes - 24/May/05 05:22 PM
Assignee Olav Sandstaa [ olav ]
Olav Sandstaa made changes - 24/May/05 05:23 PM
Status Open [ 1 ] In Progress [ 3 ]
Kathey Marsden made changes - 02/Jun/05 12:06 AM
Description setUnicodeStream and getUnicodeStream are depricated API's and
not supported for Network client but can throw unexpected
error messages.

To reproduce uncomment the "if (! isDB2jNet)" around unicode
tests in conn/blobclob4BLOB.java

setUnicodeStream and getUnicodeStream are deprecated API's

Network client
PreparedStatement.setUnicodeStream() and PreparedStatement.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
Kathey Marsden made changes - 02/Jun/05 12:12 AM
Description setUnicodeStream and getUnicodeStream are deprecated API's

Network client
PreparedStatement.setUnicodeStream() and PreparedStatement.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
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
Dyre Tjeldvoll made changes - 13/Jun/06 08:30 PM
Priority Minor [ 4 ] Major [ 3 ]
Fix Version/s 10.2.0.0 [ 11187 ]
Component/s JDBC [ 11407 ]
Olav Sandstaa made changes - 12/Jul/06 07:55 PM
Attachment derby253.diff [ 12336734 ]
Olav Sandstaa made changes - 12/Jul/06 07:55 PM
Derby Info [Patch Available]
Olav Sandstaa made changes - 13/Jul/06 05:05 PM
Derby Info [Patch Available]
Olav Sandstaa made changes - 13/Jul/06 05:42 PM
Resolution Fixed [ 1 ]
Status In Progress [ 3 ] Resolved [ 5 ]
Knut Anders Hatlen made changes - 13/Jul/06 06:15 PM
Derby Info [Release Note Needed]
Kristian Waagan made changes - 31/Jul/06 02:03 PM
Link This issue is related to DERBY-1615 [ DERBY-1615 ]
Kathey Marsden made changes - 14/May/07 04:38 PM
Status Resolved [ 5 ] Closed [ 6 ]