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-2769) Implement error handling/parameter checking in Clob.setString
Date Sun, 26 Apr 2009 13:53:30 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Yun Lee updated DERBY-2769:

    Attachment: releaseNote.html

Kathey, thanks for your advice. I have added a  '22011.S.1' message into SQLState, and applied
it to two Clobs.

>>There is a comment 
>>//if offset + len == str.length(), it's accepted. 
>>I think this is incorrect and the test case below it useds str.length() -1

I think the comment is correct, it just shows a boundary condition, and the code below the
start of ' str.length() -1' and the len of '1' is accepted, as ( str.length() -1) + 1 =  str.length().
However I have replaced it with "//if (offset + len) == str.length(), it's accepted. " to
make it clear to understand.

Please also check the release not for this issue. Thanks!

> Implement error handling/parameter checking in Clob.setString
> -------------------------------------------------------------
>                 Key: DERBY-2769
>                 URL: https://issues.apache.org/jira/browse/DERBY-2769
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions:
>            Reporter: Kristian Waagan
>            Assignee: Yun Lee
>         Attachments: DERBY-2769-1.patch, DERBY-2769-1.stat, DERBY-2769-2.patch, DERBY-2769-2.stat,
DERBY-2769-3-a.diff, DERBY-2769-3-a.stat, DERBY-2769-3-b.diff, DERBY-2769-3-b.stat, DERBY-2769-4.diff,
DERBY-2769-4.stat, releaseNote.html
> The error handling, or parameter checking, in Clob.subString is not adequate.
> There are four parameters that can be invalid;
>  * pos
>  * str
>  * offset
>  * len
> The first one is already handled properly, the remaining three are not. They typically
result in some low-level exception like a NPE.
> I have not found anything in the JDBC specification nor JavaDoc that dictates the behavior,
except for that SQLException should use states defined in the SQL 2003 specification. A brief
search there resulted in the following possibilities:
>  22003 - numeric value out of range
>  22004 - null value not allowed
>  2200F - zero-length character string
>  22011 - substring error 
>  22023 - invalid parameter value
> Some of these are already defined by Derby, but with unsuitable or very specific error

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message