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 "Yun Lee (JIRA)" <ji...@apache.org> on 2009/03/28 04:28:50 UTC
[jira] Assigned: (DERBY-3991) Clob.truncate(0) throws exception
[ https://issues.apache.org/jira/browse/DERBY-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yun Lee reassigned DERBY-3991:
------------------------------
Assignee: Yun Lee
> Clob.truncate(0) throws exception
> ---------------------------------
>
> Key: DERBY-3991
> URL: https://issues.apache.org/jira/browse/DERBY-3991
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.3.1, 10.4.2.1, 10.5.0.0
> Reporter: Kristian Waagan
> Assignee: Yun Lee
> Priority: Minor
> Attachments: derby-3991-1a-ClobTruncateZeroTest.diff, derby-3991-2a.diff
>
>
> Truncating a Clob to zero length is allowed according to the JDBC specification, which says the following about the len argument (in the @throws tag):
> "SQLException - if there is an error accessing the CLOB value or if len is less than 0 "
> Derby throws an exception if zero is passed to truncate.
> A quick inspection of the code suggests that truncating a Clob to the empty string is easy to support.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.