You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <de...@db.apache.org> on 2006/01/25 16:54:10 UTC
[jira] Commented: (DERBY-856) modify setCharacterStreamInternal to
take a long for the length, and perform the > max int check in the method
[ http://issues.apache.org/jira/browse/DERBY-856?page=comments#action_12363970 ]
Rick Hillegas commented on DERBY-856:
-------------------------------------
This seems straightforward and the derbyall tests pass. NSinSameVM has the same errors we see in the mainline. There is some instability in readlocks.sql but that test passed when I re-ran it.
> 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
>
> A similar change to setBinaryStreamInternal is being handled as part of DERBY-599.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Commented: (DERBY-856) modify setCharacterStreamInternal to
take a long for the length, and perform the > max int check in the method
Posted by Rick Hillegas <Ri...@Sun.COM>.
Thanks, Mike. I have clipped this info to DERBY-861.
Regards,
-Rick
Mike Matrigali wrote:
> I going to try and take a look at the readlocks issue, but it never
> reproduces for me. Could you post the kind of environment (#
> processors, jvm, OS) you were
> running when you saw the problem and the diff to the JIRA entry
> DERBY-861, i would like to know if all intermittent failures are in
> the same place in the test.:
>
>
>
> Rick Hillegas (JIRA) wrote:
>
>> [
>> http://issues.apache.org/jira/browse/DERBY-856?page=comments#action_12363970
>> ]
>> Rick Hillegas commented on DERBY-856:
>> -------------------------------------
>>
>> This seems straightforward and the derbyall tests pass. NSinSameVM
>> has the same errors we see in the mainline. There is some instability
>> in readlocks.sql but that test passed when I re-ran it.
>>
>>
>>> 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
>>>
>>> A similar change to setBinaryStreamInternal is being handled as part
>>> of DERBY-599.
>>
>>
>>
>
Re: [jira] Commented: (DERBY-856) modify setCharacterStreamInternal
to take a long for the length, and perform the > max int check in the method
Posted by Mike Matrigali <mi...@sbcglobal.net>.
I going to try and take a look at the readlocks issue, but it never
reproduces for me. Could you post the kind of environment (#
processors, jvm, OS) you were
running when you saw the problem and the diff to the JIRA entry
DERBY-861, i would like to know if all intermittent failures are in
the same place in the test.:
Rick Hillegas (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-856?page=comments#action_12363970 ]
>
> Rick Hillegas commented on DERBY-856:
> -------------------------------------
>
> This seems straightforward and the derbyall tests pass. NSinSameVM has the same errors we see in the mainline. There is some instability in readlocks.sql but that test passed when I re-ran it.
>
>
>>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
>>
>>A similar change to setBinaryStreamInternal is being handled as part of DERBY-599.
>
>