db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yun Lee (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3991) Clob.truncate(0) throws exception
Date Fri, 27 Mar 2009 17:32:50 GMT

     [ 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-2a.diff

Hi,  all. I'm a prospective student for GSOC, Yun Lee. I have posted a patch for this issue,
wish for your comments. 

At this moment, I'm in the user group, without the permission to assign this issue to myself.
How to apply for the developer group, please?

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.0.0
>            Reporter: Kristian Waagan
>            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.


Mime
View raw message