Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <441D8A12.60503@amberpoint.com>
Date: Sun, 19 Mar 2006 08:42:58 -0800
From: Bryan Pendleton <bpendleton@amberpoint.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: [jira] Commented: (DERBY-1014) Make tests less sensitive to
 pre-fetching
References: <1086052325.1142516403327.JavaMail.jira@ajax>
 <441983EC.1000505@amberpoint.com> <441988BD.9050208@sun.com>
 <873bhe3d1c.fsf@sun.com>
In-Reply-To: <873bhe3d1c.fsf@sun.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

>> Bryan, as far as I have understood, this JIRA is not about the actual
>> pre-fetching, but about fixing the tests so that they are not broken
>> when prefetching is introduced.  Prefetching is covered by DERBY-822.

Thanks! I knew this once, but had forgotten.

I'm still quite interested in the whole pre-fetching topic, and I suspect
I may learn quite a bit by studying the tests, as it's interesting to me
to consider how the external behavior of the system, as reflected in the
tests, is changed via the pre-fetching. So seeing where the prefetching
changes interacted with tests which proved sensitive to prefetching, is
an interesting eye into this new behavior.

Plus I need to learn more about the tests in general, so taking the
opportunity to study patches to them is good exercise.

But I've been quite busy with some other issues recently, so please don't
hold up this issue on my behalf. I'll continue to follow it as you go.

thanks,

bryan