You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <de...@db.apache.org> on 2005/05/01 06:39:04 UTC
[jira] Created: (DERBY-253) Client should throw not implemented exception for depricated setUnicodeStream/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
Versions: 10.1.0.0
Reporter: Kathey Marsden
Priority: Minor
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
--
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
[jira] Closed: (DERBY-253) Client should throw not implemented
exception for depricated setUnicodeStream/getUnicodeStream
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden closed DERBY-253.
--------------------------------
> Client should throw not implemented exception for depricated setUnicodeStream/getUnicodeStream
> ----------------------------------------------------------------------------------------------
>
> Key: DERBY-253
> URL: https://issues.apache.org/jira/browse/DERBY-253
> Project: Derby
> Issue Type: Bug
> Components: JDBC, Network Client
> Affects Versions: 10.1.1.0
> Reporter: Kathey Marsden
> Assigned To: Olav Sandstaa
> Fix For: 10.2.1.6
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-253) Client should throw not implemented
exception for depricated setUnicodeStream/getUnicodeStream
Posted by "Olav Sandstaa (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-253?page=all ]
Olav Sandstaa updated DERBY-253:
--------------------------------
Derby Info: [Patch Available]
> 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
--
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
Re: [jira] Commented: (DERBY-253) Client should throw not implemented
exception for depricated setUnicodeStream/getUnicodeStream
Posted by Kathey Marsden <km...@sbcglobal.net>.
Lance J. Andersen wrote:
> There are still a fair amount of applications which utilize these
> methods. I am not removing these methods in JDBC 4 and infact I
> actually clarified the api docs for them.
>
> Derby should implement these IMHO.
We are making a new JDBC driver and these are deprecated methods. We
throw not implemented exceptions for embedded and right now in the
client, they are there but are broken (can cause protocol errors and
loss of connection). I guess if you wanted to spend a lot of time to
implement them for both embedded and client, I wouldn't object strongly
to having them, but in general my vote would be to throw a not
implemented exception like we do for embedded at least for now.
Thanks
Kathey
Re: [jira] Commented: (DERBY-253) Client should throw not implemented
exception for depricated setUnicodeStream/getUnicodeStream
Posted by "Lance J. Andersen" <La...@Sun.COM>.
There are still a fair amount of applications which utilize these
methods. I am not removing these methods in JDBC 4 and infact I
actually clarified the api docs for them.
Derby should implement these IMHO.
Regards
Lance
Daniel John Debrunner (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-253?page=comments#action_64262 ]
>
>Daniel John Debrunner commented on DERBY-253:
>---------------------------------------------
>
>What should the behaviour be? I think unimplemented is correct, implementing methods that are not intended to be used seems wrong.
>
>
>
>>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.0.0
>> Reporter: Kathey Marsden
>> Priority: Minor
>>
>>
>
>
>
>>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
>>
>>
>
>
>
[jira] Commented: (DERBY-253) Client should throw not implemented exception for depricated setUnicodeStream/getUnicodeStream
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-253?page=comments#action_64262 ]
Daniel John Debrunner commented on DERBY-253:
---------------------------------------------
What should the behaviour be? I think unimplemented is correct, implementing methods that are not intended to be used seems wrong.
> 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.0.0
> Reporter: Kathey Marsden
> Priority: Minor
>
> 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
--
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
[jira] Commented: (DERBY-253) Client should throw not implemented
exception for depricated setUnicodeStream/getUnicodeStream
Posted by "Olav Sandstaa (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-253?page=comments#action_12420833 ]
Olav Sandstaa commented on DERBY-253:
-------------------------------------
Thanks for reviewing and committing this patch, Knut Anders!
Since this patch removes functionality from the client driver (although probably broken functionality), is this something that needs a comment in the release notes?
> 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
--
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
[jira] Updated: (DERBY-253) Client should throw not implemented exception for depricated setUnicodeStream/getUnicodeStream
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-253?page=all ]
Kathey Marsden updated DERBY-253:
---------------------------------
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
was:
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
Removing out of date test information to clarify the Jira entry.
> 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.0.0
> Reporter: Kathey Marsden
> Assignee: Olav Sandstaa
> Priority: Minor
>
> 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
--
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
Re: [jira] Commented: (DERBY-253) Client should throw not implemented
exception for depricated setUnicodeStream/getUnicodeStream
Posted by Kathey Marsden <km...@sbcglobal.net>.
Olav Sandstaa (JIRA) wrote:
>The report refers to the a test named "conn/blobclob4BLOB.java", but I am unable to locate any test with name. There is a test named "jdbcapi/blobclob4BLOB.java" and initially I thought this was the right test to use, but I can not find that this test is doing any calls to setUnicodeStream/getUnicodeStream.
>
>There is a test called "jdbcapi/parameterMapping.java" that does a lot of calls to setUnicodeStream/getUnicodeStream which are disabled when running with the network client. I suspect this is the right test to use for reproducing this problem.
>
>
>
Hi Olav,
I updated the Jira entry so it is (hopefully) more clear. It had some
out of date test information.
I think parameterMapping is the right place to test these calls. They
should throw not implemented exceptions for both embedded and client. I
believe they already do for embedded. It would be good if the client
matches the embedded SQLState for this exception.
Kathey
[jira] Commented: (DERBY-253) Client should throw not implemented exception for depricated setUnicodeStream/getUnicodeStream
Posted by "Olav Sandstaa (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-253?page=comments#action_66736 ]
Olav Sandstaa commented on DERBY-253:
-------------------------------------
I have had some problems trying to reproduce this problem based on the description given in the Jira report.
The report refers to the a test named "conn/blobclob4BLOB.java", but I am unable to locate any test with name. There is a test named "jdbcapi/blobclob4BLOB.java" and initially I thought this was the right test to use, but I can not find that this test is doing any calls to setUnicodeStream/getUnicodeStream.
There is a test called "jdbcapi/parameterMapping.java" that does a lot of calls to setUnicodeStream/getUnicodeStream which are disabled when running with the network client. I suspect this is the right test to use for reproducing this problem.
Since I am new to the Derby code and test harness I would appreciate that someone told me if I am on the wrong track to reproduce this problem.
> 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.0.0
> Reporter: Kathey Marsden
> Assignee: Olav Sandstaa
> Priority: Minor
>
> 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
--
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
[jira] Updated: (DERBY-253) Client should throw not implemented
exception for depricated setUnicodeStream/getUnicodeStream
Posted by "Olav Sandstaa (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-253?page=all ]
Olav Sandstaa updated DERBY-253:
--------------------------------
Derby Info: (was: [Patch Available])
> 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
--
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
[jira] Assigned: (DERBY-253) Client should throw not implemented exception for depricated setUnicodeStream/getUnicodeStream
Posted by "Olav Sandstaa (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-253?page=all ]
Olav Sandstaa reassigned DERBY-253:
-----------------------------------
Assign To: Olav Sandstaa
> 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.0.0
> Reporter: Kathey Marsden
> Assignee: Olav Sandstaa
> Priority: Minor
>
> 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
--
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
[jira] Commented: (DERBY-253) Client should throw not implemented exception for depricated setUnicodeStream/getUnicodeStream
Posted by "Lance Andersen (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Updated: (DERBY-253) Client should throw not implemented
exception for depricated setUnicodeStream/getUnicodeStream
Posted by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org>.
[ 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:
PROBLEM
PreparedStatement.setUnicodeStream() and ResultSet.getUnicodeStream()
throw SQLException when invoked after upgrading to Apache Derby 10.2.
SYMPTOM
Calling either of these methods will result in an exception with
SQLSTATE 0A000 and message: "Feature not implemented: ..."
CAUSE
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.
SOLUTION
This was an intentional change. No Derby product solution is offered.
WORKAROUND
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: 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
--
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
[jira] Resolved: (DERBY-253) Client should throw not implemented
exception for depricated setUnicodeStream/getUnicodeStream
Posted by "Olav Sandstaa (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-253?page=all ]
Olav Sandstaa resolved DERBY-253:
---------------------------------
Resolution: Fixed
Verified that the patch is in. Thanks for commiting it, Knut Anders!
> 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
--
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
[jira] Updated: (DERBY-253) Client should throw not implemented
exception for depricated setUnicodeStream/getUnicodeStream
Posted by "Dyre Tjeldvoll (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-253?page=all ]
Dyre Tjeldvoll updated DERBY-253:
---------------------------------
Component: JDBC
Fix Version: 10.2.0.0
Priority: Major (was: Minor)
> 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
>
> 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
[jira] Updated: (DERBY-253) Client should throw not implemented
exception for depricated setUnicodeStream/getUnicodeStream
Posted by "Olav Sandstaa (JIRA)" <de...@db.apache.org>.
[ 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
--
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
[jira] Updated: (DERBY-253) Client should throw not implemented exception for depricated setUnicodeStream/getUnicodeStream
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-253?page=all ]
Kathey Marsden updated DERBY-253:
---------------------------------
Description:
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
was:
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
> 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.0.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
[jira] Commented: (DERBY-253) Client should throw not implemented
exception for depricated setUnicodeStream/getUnicodeStream
Posted by "Olav Sandstaa (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-253?page=comments#action_12420864 ]
Olav Sandstaa commented on DERBY-253:
-------------------------------------
Knut Anders, thanks for the proposal to release notes. This looks very good.
> 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
--
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
[jira] Updated: (DERBY-253) Client should throw not implemented exception for depricated setUnicodeStream/getUnicodeStream
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-253?page=all ]
Daniel John Debrunner updated DERBY-253:
----------------------------------------
Comment: was deleted
> 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.0.0
> Reporter: Kathey Marsden
> Priority: Minor
>
> 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
--
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
[jira] Commented: (DERBY-253) Client should throw not implemented
exception for depricated setUnicodeStream/getUnicodeStream
Posted by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-253?page=comments#action_12420831 ]
Knut Anders Hatlen commented on DERBY-253:
------------------------------------------
The tests ran cleanly. Committed revision 421570. Thanks Olav!
> 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
--
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
[jira] Commented: (DERBY-253) Client should throw not implemented
exception for depricated setUnicodeStream/getUnicodeStream
Posted by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-253?page=comments#action_12420797 ]
Knut Anders Hatlen commented on DERBY-253:
------------------------------------------
The patch looks good. I will run some tests and commit it.
> 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
--
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