Thanks, Narayanan, I'll take a look at this.
The LobTest failure was a result of my checkin try and fix some jdk13
test regressions. In the process I broke LobTest for jdk14. I just
checked in a fix, let me know if that works for you.
Rather than spending the time to run a test in your own clean sandbox,
you can always check the test results from the regression test run or
the tinderbox test runs found at
http://www.multinet.no/~solberg/public/Apache/index.html
and
http://people.apache.org/~fuzzylogic/derby_test_results/
David
V.Narayanan (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-856?page=all ]
>
> V.Narayanan updated DERBY-856:
> ------------------------------
>
> Attachment: setCharacterStreamInternal_3.diff
>
> Hi,
> 1) I have made the changes and am reattaching the patch again.
> 2) I ran derbyall and noticed failures. I noticed a failure in jdbcapi/LobTest.java.
So I ran derbyall on a workspace on which I had'nt applied this patch and
> I observed the same failure. I then concluded that this failure was not due to me
applying my patch.
> 3) I am attaching the diff file setCharacterStreamInternal_3.diff as the new diff file.
> thanx
> Narayanan
>
>
>
>>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, setCharacterStreamInternal_3.diff
>>
>>A similar change to setBinaryStreamInternal is being handled as part of DERBY-599.
>
>
|