Insert / delete fails on unique constraint (order problem)

Question

Hi dear Kodo team,
within a transaction, we are deleting a certain jdo object. The deletion is
undone later (within the same tx), resulting in creating a new object with
the same contents as the deleted one (gets another oid, of course). In our
database, there is a unique constraint on two mapped fields of this object.
Unfortunately, kodo issues the INSERT statement before the DELETE
statement, thus producing a unique constraint violation.
Is there a way to influence the statement order? Is there any solution other
than disabling / deferring this constraint?
Thanks in advance,
Contus

Answer 1

Beside Oracle, we are using our db schema on db platforms that do not
support deferred constraints. That's why we would like to know if there is
a way to influence statement order without removing those constraints.
Thanks,
Contus
Alex Roytman wrote:
In general the best option is to use deferred constraints on all your FK
and unique constraints. You still get complete referential integrity but
do not need Kodo to order your statements for you. If you are already
doing it but still get this error message and you are using Oracle 9.2 it
seems to be a bug in oracle JDBC. I submitted it to oracle - they accepted
it and supposedly working on resolution
"contus" <[email protected]> wrote in message
news:bulku6$qad$[email protected]..
Hi dear Kodo team,
within a transaction, we are deleting a certain jdo object. The deletionis
undone later (within the same tx), resulting in creating a new object
with the same contents as the deleted one (gets another oid, of course).
In our database, there is a unique constraint on two mapped fields of
thisobject.
Unfortunately, kodo issues the INSERT statement before the DELETE
statement, thus producing a unique constraint violation.
Is there a way to influence the statement order? Is there any solutionother
than disabling / deferring this constraint?
Thanks in advance,
Contus