[
https://issues.apache.org/jira/browse/DERBY-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Lee updated DERBY-3991:
---------------------------
Attachment: derby-3991-3.releaseNote.html
derby-3991-3.stat
derby-3991-3.diff
Thanks for your detailed advice, Kristian and Dag.
I have added Stream test for empty String.
Besides, I provide a release note for the change on truncate(). It addresses
two changes:
1.Accept zero length.
2.Give a more specific error message for nonpositive length.
I think accepting zero length is more important than giving a more specific
error message. As the type of this issue is 'Bug'.
Wish for your comments!
Yun
> 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, derby-3991-3.diff, derby-3991-3.releaseNote.html,
> derby-3991-3.stat
>
>
> 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.
