db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3991) Clob.truncate(0) throws exception
Date Tue, 31 Mar 2009 17:22:50 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694187#action_12694187
] 

Dag H. Wanvik commented on DERBY-3991:
--------------------------------------

I think if the error message is documented for the usage case (often they are not..), then
it is a API change and we should have 
a release note. If the actual error message is not documented in the user docs, it is less
clear to me that a release note is needed..
It may still be prudent do add one, though. I would not object to it.

> 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.1.0, 10.6.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.


Mime
View raw message