Re: Can not find/download release 10.8.3.0

2013-01-08 Thread Maison Mo


--- En date de : Lun 7.1.13, Rick Hillegas  a écrit :

> De: Rick Hillegas 
> Objet: Re: Can not find/download release 10.8.3.0
> À: derby-user@db.apache.org
> Date: Lundi 7 janvier 2013, 15h33
> On 1/7/13 2:12 AM, Maison Mo wrote:
> > Hello,
> >
> > I use currently Derby 10.8.2.2, and plan to use
> 10.8.3.0, mainly for the bug fix : 
> https://issues.apache.org/jira/browse/DERBY-5552
> >
> > However I could not find any 10.8.3.0 binary from
> download page :
> > http://db.apache.org/derby/derby_downloads.html link
> seems to be broken ?
> >

> Hi Mo,
> 
> I think this is corrected now. Please try again. Note that
> DERBY-5552 is 
> also marked as fixed in 10.9.1.0.

Hello, download page contains 10.8.3.0 binairies, but references 10.9.0.0 
release notes.
Thank you for the link.

  M. Maison




Re: Can not find/download release 10.8.3.0

2013-01-08 Thread Rick Hillegas

On 1/8/13 12:43 AM, Maison Mo wrote:


--- En date de : Lun 7.1.13, Rick Hillegas  a écrit :


De: Rick Hillegas
Objet: Re: Can not find/download release 10.8.3.0
À: derby-user@db.apache.org
Date: Lundi 7 janvier 2013, 15h33
On 1/7/13 2:12 AM, Maison Mo wrote:

Hello,

I use currently Derby 10.8.2.2, and plan to use

10.8.3.0, mainly for the bug fix : 
https://issues.apache.org/jira/browse/DERBY-5552

However I could not find any 10.8.3.0 binary from

download page :

http://db.apache.org/derby/derby_downloads.html link

seems to be broken ?
Hi Mo,

I think this is corrected now. Please try again. Note that
DERBY-5552 is
also marked as fixed in 10.9.1.0.

Hello, download page contains 10.8.3.0 binairies, but references 10.9.0.0 
release notes.
Thank you for the link.

   M. Maison




Thanks, Mo. Hopefully this problem is fixed now, too.

Thanks,
-Rick


RE: Force unique constraint to be enforced at statement execution?

2013-01-08 Thread Bergquist, Brett
Not exactly familiar with Spring Data JPA but I am with JPA with container 
managed transactions.   Assuming you have a handle on the EntityManager, invoke 
the 'flush' method on it which will cause the entity manager to perform the 
database operations before the commit.   You can then wrap your code with a 
try/catch block if needed to catch the exception that occurs.

-Original Message-
From: Matthew Adams [mailto:matt...@matthewadams.me] 
Sent: Tuesday, January 08, 2013 1:46 PM
To: derby-user@db.apache.org
Subject: Force unique constraint to be enforced at statement execution?

Hi all,

How do I force a unique constraint to be enforced upon statement execution 
instead of at transaction commit?

I'm using Spring Data JPA over DataNucleus & Derby (embedded), and Spring's 
persistence exception translation proxy is not translating the unique 
constraint exception because it's happening at transaction commit instead of 
when the statement is executed.

Thanks,
Matthew




--
View this message in context: 
http://apache-database.10148.n7.nabble.com/Force-unique-constraint-to-be-enforced-at-statement-execution-tp126304.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.




Re: Force unique constraint to be enforced at statement execution?

2013-01-08 Thread Rick Hillegas

On 1/8/13 10:46 AM, Matthew Adams wrote:

Hi all,

How do I force a unique constraint to be enforced upon statement execution
instead of at transaction commit?

Hi Matthew,

I am not familiar with how your application stack defers constraint 
enforcement until commit time. Derby constraints are always enforced at 
statement end and never deferred to commit time. There is an outstanding 
enhancement request for deferring enforcement: 
https://issues.apache.org/jira/browse/DERBY-532. If you run in 
autocommit mode, statement and transaction boundaries coincide. More 
information on Derby constraints can be found in the section titled 
"CONSTRAINT clause" in the Derby Reference Manual.


Sorry that this does not address your problem,
-Rick

I'm using Spring Data JPA over DataNucleus&  Derby (embedded), and Spring's
persistence exception translation proxy is not translating the unique
constraint exception because it's happening at transaction commit instead of
when the statement is executed.

Thanks,
Matthew




--
View this message in context: 
http://apache-database.10148.n7.nabble.com/Force-unique-constraint-to-be-enforced-at-statement-execution-tp126304.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.