openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From garpinc <>
Subject Re: Duplicate entry issue with multithreaded application
Date Mon, 24 Sep 2012 15:01:14 GMT
This is my last major issue which I hope to resolve today.. Is there any
facility to control what happens in JPA when a unique key constraint is
violated? Rather than have the whole transaction rollback I'd just like it
to get the existing record instead and move on...

Rick any ideas here?

View this message in context:
Sent from the OpenJPA Users mailing list archive at

View raw message