Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <988596289.1240147007544.JavaMail.jira@brutus>
Date: Sun, 19 Apr 2009 06:16:47 -0700 (PDT)
From: "Yun Lee (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-3991) Clob.truncate(0) throws exception
In-Reply-To: <19293666.1229345384746.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Yun Lee commented on DERBY-3991:
--------------------------------

>I think the release note needs some more work. For instance, do we want to describe two issues in one release note (zero length allowed, and the change of error message), or would it be better with a release note for each issue?

Kristian, thanks for your committing, it's a good message. And  I would love to provide two release notes for the two change points. 

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'?

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.