db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David W. Van Couvering" <David.Vancouver...@Sun.COM>
Subject Re: [jira] Commented: (DERBY-856) modify setCharacterStreamInternal to take a long for the length, and perform the > max int check in the method
Date Fri, 03 Feb 2006 18:45:05 GMT
I'm not sure I understand this logic.  Shouldn't we be providing useful 
error messages with enough detail as possible?  Standard error messages 
may be reusable, but they may not be helpful.  Are there space concerns?

David

Daniel John Debrunner (JIRA) wrote:
>     [ http://issues.apache.org/jira/browse/DERBY-856?page=comments#action_12365037 ]

> 
> Daniel John Debrunner commented on DERBY-856:
> ---------------------------------------------
> 
> Patch looks good,  I don't agree the error message has to change, it's the standard Derby
error message for the correct situation. We shouls not be adding special error messages for
one off situations.
> 
> 
>>modify setCharacterStreamInternal to take a long for the length, and perform the >
max int check in the method
>>--------------------------------------------------------------------------------------------------------------
>>
>>         Key: DERBY-856
>>         URL: http://issues.apache.org/jira/browse/DERBY-856
>>     Project: Derby
>>        Type: Improvement
>>  Components: JDBC
>>    Versions: 10.2.0.0
>> Environment: All Environments
>>    Reporter: V.Narayanan
>>    Assignee: V.Narayanan
>>    Priority: Minor
>> Attachments: setCharacterStreamInternal.diff, setCharacterStreamInternal.stat, setCharacterStreamInternal_1.diff,
setCharacterStreamInternal_2.diff, setCharacterStreamInternal_2.stat
>>
>>A similar change to setBinaryStreamInternal is being handled as part of DERBY-599.

> 
> 

Mime
View raw message