Hi,
Can you post the error?
If business logic ensured that {P_TYPE_ID, P_VALUE_STRING} of Parameter are
unique combination then what exactly was the state of the Parameter instance
P that violated the unique constrain?
One possibility is during merge() operation, OpenJPA has wrongly judged the
persistent life-cycle state of a detached Parameter instance P, and tried to
re-insert P. But more data points are needed to diagnose what is going
wrong.
-----
Pinaki
--
View this message in context:
http://openjpa.208410.n2.nabble.com/ManyToMany-relations-violating-unique-constraints-tp5002254p5014509.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
