db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2769) Implement error handling/parameter checking in Clob.setString
Date Wed, 29 Apr 2009 17:26:30 GMT

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

Kathey Marsden commented on DERBY-2769:
---------------------------------------

Tests were clean but I had a conflict in messages.xml on commit. It seemed to merge cleanly
when I synched up, but when I rebuilt I got:
runmessagecheck:
[runMessageBundleTest] WARNING: Message id XRE04.U.1 in messages_en.properties is not referenced
in either SQLState.java
 or MessageId.java
[runMessageBundleTest] WARNING: Message id XRE04.U.2 in messages_en.properties is not referenced
in either SQLState.java
 or MessageId.java
[runMessageBundleTest] WARNING: Message id XRE05 in messages_en.properties is not referenced
in either SQLState.java or
MessageId.java
[runMessageBundleTest] WARNING: Message id XRE09 in messages_en.properties is not referenced
in either SQLState.java or
MessageId.java
[runMessageBundleTest] WARNING: Message id XRE11 in messages_en.properties is not referenced
in either SQLState.java or
MessageId.java
[runMessageBundleTest] WARNING: Message id XRE21 in messages_en.properties is not referenced
in either SQLState.java or
MessageId.java
[runMessageBundleTest] WARNING: Message id XRE22 in messages_en.properties is not referenced
in either SQLState.java or
MessageId.java
[runMessageBundleTest] WARNING: Message id XRE41 in messages_en.properties is not referenced
in either SQLState.java or
MessageId.java
[runMessageBundleTest] WARNING: Message id XRE42 in messages_en.properties is not referenced
in either SQLState.java or
MessageId.java

BUILD FAILED
C:\svn4\trunk\build.xml:514: Message check failed.
See error in build output or call ant runmessagecheck.

I will investigate.


> 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: 10.3.1.4
>            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
messages.

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