[
https://issues.apache.org/jira/browse/DERBY-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694129#action_12694129
]
Kristian Waagan commented on DERBY-3991:
----------------------------------------
Regarding the error message, I'm just wondering if the users should be notified
about the change through a release note [1]. We have a release note template
under "trunk/tools/release/templates/releaseNote.html", if you want to take a
look.
I agree the change is a good one, but I don't know if the change requires that
the community notifies the users about the changed error message.
Maybe someone else in the community has a stronger opinion about this?
[1] FYI, here are the release notes for 10.4:
http://db.apache.org/derby/releases/release-10.4.2.0.cgi#Release%20Notes%20for%20Derby%2010.4.2.0
Note especially under "Issues" and the "Note for DERBY-X" paragraphs.
> 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.
