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 mcintyre.a@gmail.com designates
 66.249.92.170 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=LtoT2Y+i35/2M/vmNFQamm7l9M0ITizMvVddvLV6UDIcPrm5jwEPCgDklkiE3zYlF5VyErwFCIVwiuKkYczptMrM+5ljiUx60lgjCqTLisaK3VAcXPaWKJwTxpM+iiSd/Z+nHSAUs3Bzlho7q9Pt4DgCIuouHF5ECAvBXECGE5g=
Message-ID: <54ac72d70607102155p19ba7bf8jad9bd7b70cd0df88@mail.gmail.com>
Date: Mon, 10 Jul 2006 21:55:31 -0700
From: "Andrew McIntyre" <mcintyre.a@gmail.com>
To: "Derby Discussion" <derby-user@db.apache.org>
Subject: Re: Apache Derby with Hibernate3 (more specificly GRAILS)
In-Reply-To: <BAY102-F16B53CFCE23A90B1D18FB6A0680@phx.gbl>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <BAY102-F16B53CFCE23A90B1D18FB6A0680@phx.gbl>

On 7/10/06, Lance Shaw <lanceshaw25@hotmail.com> wrote:
> Hello,
>
> I'm tring to use Derby with GRAILS which uses Hibernate3.  When I try to
> start the application using 'grails run-app' I get the following error:
>
> org.codehaus.groovy.grails.orm.hibernate.exceptions.CouldNotDetermineHibernateDialectException:
> Could not determine Hibernate dialect for database name [Apache Derby]!]
>
> Anyone know if there are dialect classes available for Derby to work with
> Hibernate3?

Hi Lance,

There is a Hibernate dialect class attached to this Hibernate JIRA issue:

http://opensource.atlassian.com/projects/hibernate/browse/HB-1224

>From the comments there, it appears that the class should be in
Hibernate 3.0. There is also a GRAILS JIRA issue that seems to
correspond to the error you are receiving:

http://jira.codehaus.org/browse/GRAILS-129

which, from the comments there, appears to have been fixed for Grail
.02 on May 31, 2006. So, if you are using GRAILS .01, this is probably
the issue you are hitting. You may want to check with the GRAILS
project to see if this is in fact the issue you are encountering.

cheers,
andrew