[
https://issues.apache.org/jira/browse/DERBY-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3991:
-----------------------------------
Attachment: releaseNote.html
As a start, I tried to rewrite the release note, but I'm not sure if it is
acceptable. Please review.
The file is now attached as 'releaseNote.html' to allow the release note
generator to pick it up.
> 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
> Fix For: 10.6.0.0
>
> Attachments: derby-3991-1a-ClobTruncateZeroTest.diff,
> derby-3991-2a.diff, derby-3991-3.diff, derby-3991-3.releaseNote.html,
> derby-3991-3.stat, releaseNote.html
>
>
> 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.
