Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openjpa.apache.org
Received-SPF: pass (athena.apache.org: domain of christian.defoy@gmail.com
 designates 66.249.82.236 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=hMQ5kOYK/qQMq15KfkoDvoF376I64Lrw8M2WQu+sV/ghgfOUDEREGO/sFMK6rozY9U3FV+aDYULZYzHac6OJwYHc4P7oKVmp7Js0nrjnu8wiRbq6XCcotZzkl4I/Xji5vvWwX4rrdsZ14Y3D+smYyey3Q42FBatphTzeKp2BhZQ=
Message-ID: <967946b0708211258y74e88d20p973a231915da78f0@mail.gmail.com>
Date: Tue, 21 Aug 2007 15:58:06 -0400
From: "Christian Defoy" <christian.defoy@gmail.com>
To: users@openjpa.apache.org
Subject: Re: Detection of constraint violations
In-Reply-To: <7262f25e0708211126w6cce0772h8f1a5c17c27e35eb@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <967946b0708211119i77f17d56tece25f04be84933b@mail.gmail.com>
	 <7262f25e0708211126w6cce0772h8f1a5c17c27e35eb@mail.gmail.com>

Patrick,

When I step into the code, I do see ReferentialIntegrityException
being created but they get converted to PersistenceException at some
point in PersistenceExceptions.translateStoreException().  My guess is
that no equivalent exception exists in the JPA spec...

I also only look for SQLState 23000.  I have nothing special to add to
that list...

Thanks!

Christian

On 8/21/07, Patrick Linskey <plinskey@gmail.com> wrote:
> When we can, we try to wrap such exceptions in a
> ReferentialIntegrityException. I think that we just look for SQLState
> of 23000 currently, though.
>
> Can you post stacks that correspond to codes that we should also be catching?
>
> -Patrick
>
> On 8/21/07, Christian Defoy <christian.defoy@gmail.com> wrote:
> > Hello,
> >
> > I am looking for a way of programatically detecting whether an
> > exception was caused by a constraint violation.  What is the best way
> > to do that?
> >
> > The only way I have found so far is to navigate up the cause chain of
> > the exception and see if one happens to be an SQLException and if so,
> > get the SQLState and see if it is 23xxx.
> >
> > Is there a simpler way?
> >
> > Oh, by the way, example 12.2 of the manual states that we can put
> > @Unique annotations in the @Table one but it turns out that type must
> > be @UniqueConstraint.
> >
> > Thanks in advance!
> >
> > Christian
> >
>
>
> --
> Patrick Linskey
> 202 669 5907
>