db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Waagan <Kristian.Waa...@Sun.COM>
Subject Re: 10.5 backporting
Date Mon, 28 Jun 2010 06:35:26 GMT
On 27.06.10 02:16, Dag H. Wanvik wrote:
> Hi Kathey,
> Kathey Marsden<kmarsdenderby@sbcglobal.net>  writes:
>> I was looking at the fixes that have gone into trunk and 10.6 and
>> seeing what looked good to backport to 10.5.  I came up with the
>> following list.   I did not look all that closely, but just picked
>> ones that looked like they might be likely user hits.  Please speak up
>> if you see any that would not be appropriate for backport or any that
>> the query may have missed. Sometimes the affects versions and fix
>> versions in Jira are not quite right so the query will miss something
>> useful.
> I just added "fixed in" to DERBY-4679, which you may want to consider.
>> DERBY-4477  |[DERBY-4477] Selecting / projecting a column whose value
>> is represented by a stream more than once fails
>> |Dag H. Wanvik
> This one may, or may not depend on other LOB work Kristian have been
> doing, not sure.

That's correct, it depends on DERBY-4520.
Backporting that one is at least moderately risky, it involves 
significant changes and refactoring.
Too bad, as it created the basis for fixing a number of stream-related 


>> DERBY-4448  |[DERBY-4448] ArrayIndexOutOfBoundsException when trying
>> to override generated column
>> |Dag H. Wanvik
> Has probably already been backported, since the fix was attached to
> DERBY-4451 (solved both issues).
> Thanks,
> Dag

View raw message