db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3991) Clob.truncate(0) throws exception
Date Mon, 20 Apr 2009 08:25:47 GMT

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

Kristian Waagan commented on DERBY-3991:
----------------------------------------

Yun,
> However, I have some questions about the name of release notes. You have said 'The file
is now attached as 'releaseNote.html' to allow the release note generator to pick it up',
do you mean a release note must have the identical name of 'releaseNote.html'? If so, should
I post the two release notes in two times with the same name of 'releaseNote.html'?

I don't think we can attach two release notes to the same issue and have the release notes
generator pick them both up. If we end up with such a scenario, I think we have to split the
issue into two (or create a sub-issue).

The only feedback from the community so far has been to write a release note for the changed
SQLState only. If you agree, you can start rewriting the release note again.
You can attach the next version of the release note as 'releaseNote.html' as well. The release
notes generator will pick up the newest version.


Thanks,


> 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.


Mime
View raw message