Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Date: Fri, 22 Apr 2005 09:36:42 +0200
From: Oyvind.Bakksjo@Sun.COM
Subject: Re: DERBY-31: setQueryTimeout semantics
In-reply-to: <003601c546f2$1568d930$1401a8c0@RPWS002>
To: Derby Development <derby-dev@db.apache.org>
Message-id: <4268A98A.3080507@sun.com>
Organization: Sun Microsystems
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Mozilla/5.0 (X11; U; Linux i686; nb-NO; rv:1.7) Gecko/20040618
References: <42679AC9.2040105@sun.com> <4267CD05.5020206@debrunners.com>
 <003601c546f2$1568d930$1401a8c0@RPWS002>

RPost skrev:
>>"Daniel John Debrunner" wrote:
> 
> 
>>One of the ways to make an easy
>>to use database is to start with the mindset that no tuning properties
>>should be allowed and work from that.
> 
> 
> Or perhaps to start with the mindset that no tuning properties
> should be 'required'. As long as they are not required I have no problem
> with having properties that can be set by the user.

I agree with you here. Things should work fine out-of-the-box, but 
advanced users should be able to tune the system if they find that they 
need some different behaviour (e.g. more responsive cancellation, 
possibly at the expense of performance).

-- 
Oyvind Bakksjo
oyvind.bakksjo@sun.com
Office: +47 73842119
Mobile: +47 92283522