Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of duncangroenewald@xtra.co.nz
 designates 210.54.141.242 as permitted sender)
Message-ID: <44F4952E.8000605@xtra.co.nz>
Date: Wed, 30 Aug 2006 07:27:42 +1200
From: Duncan Groenewald <duncangroenewald@xtra.co.nz>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: Derby vs. Hypersonic SQL
References: <44F403C6.2000800@intland.com>
In-Reply-To: <44F403C6.2000800@intland.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I have used both and now rely on McKoiDB for the majority of work.  
While it lacks one or two features it has proven to be very stable and 
reliable.  Derby lacks a couple of key features I needed, especially no 
user access control (GRANT, REVOKE).

I found Hypersonic's persistent to be unreliable and gave up after 
experiencing corruption on a number of databases.

I started a simple evaluation document to compare key features I needed 
which might help.  Send me your email address and I'll forward you a 
copy if you would like.

Regards
Duncan

Robert Enyedi wrote:
> Hi,
>
> We have a MySQL database with around 50 tables and we are thinking 
> about supporting other database engines too. After studying the 
> options on the Java DB engine implementations, it seems that there are 
> two important contenders: Apache Derby and Hypersonic SQL. While our 
> feeling is that Hypersonic SQL is a more mature product, Derby seems 
> to be hyped about a lot these days and it also has quite some history 
> since the days of Informix and Cloudscape.
>
> Could you please help in our decision by pointing out some advantages 
> and shortcomings of Apache Derby versus Hypersonic SQL?
>
> Thanks,
> Robert
>