Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Date: Mon, 07 Jul 2008 17:40:57 +0200
From: Dag.Wanvik@Sun.COM (Dag H. Wanvik)
Subject: Re: simpler api to the Derby store
In-reply-to: <wjo8bq1du4cb.fsf@khepri41.norway.sun.com>
Sender: Dag.Wanvik@Sun.COM
To: derby-dev@db.apache.org
Message-id: <x1ox7ibxhfcm.fsf@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
References: <4863BD11.5050402@sun.com> <4863C0CD.6070303@amberpoint.com>
 <486A6E52.8000800@sbcglobal.net> <486A8B09.7010106@sun.com>
 <7921d3e40807022339q5ae0a3f6ja63867114f8e9f44@mail.gmail.com>
 <wjo8bq1du4cb.fsf@khepri41.norway.sun.com>
User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/22.1 (usg-unix-v)

Knut Anders Hatlen <Knut.Hatlen@Sun.COM> writes:

> although the API could need to be cleaned up and made easier. If someone
> wants to do such a cleanup, I think it would be good because
>
>   a) it may make Derby code that accesses the store simpler (easier to
>   understand, more maintainable)
>
>   b) it is easier for other projects to use Derby's store directly
>   without needing to fork Derby's code base (which potentially
>   increases Derby's user base and the chance of getting contributions
>   back from those projects)

If the API were cleaner/easier, it would also make it more palatable
to produce other backends for Derby. We have had attempts to make main
memory backends; I am not sure why these never made it into
"production", though, could a backend API complexity be one reason?