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 includes SPF record at
 spf.trusted-forwarder.org)
Message-ID: <003601c546f2$1568d930$1401a8c0@RPWS002>
From: "RPost" <rp0428@pacbell.net>
To: "Derby Development" <derby-dev@db.apache.org>
References: <42679AC9.2040105@sun.com> <4267CD05.5020206@debrunners.com>
Subject: Re: DERBY-31: setQueryTimeout semantics
Date: Thu, 21 Apr 2005 21:16:39 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

> "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 believe that Derby already has too many tuning properties and would
> like to see it move towards a single tuning property, such "how much
> memory can this database use". Everything else would be self tuned.

Would you have the same concern if the existing tuning properties were
'self tuning'? Maybe the focus should be more on making the existing
properties tune themselves rather than eliminating them altogether.