Hi all,

I have the following problem:

· I have a table with a unique constraint on a pair of columns, let's call them (X, Y). I start a transaction with hibernate in which i first delete some rows and then i insert new ones. These new rows have the same values for (X, Y) than the old ones, but new values for other columns, also i use new Java Objects to be inserted on the table (with the PK attribute set to null), but despite of this i get an unique constraint error when the transaction ends and tries to commit. Suggestions? Any help would be appreciated.

Thanks in advance.

Hello
Do you commit (flush) the session between delete and insert?
http://www.hibernate.org/hib_docs/v3/re ... e-flushing

Hi man,

Thxs for your help, i don't commit between delete and insert,
the transaction should be committed only at the end, am i wrong?.
I don't do that, but i have a session.setFlushMode(FlushMode.AUTO)
at the beginning of the transaction, previous to the deletes and the inserts, don't know if this could be the problem.

Thxs in advance

In the doc the algorithm to executing flush (in this case the auto-flush) says that insertions come first. I'm not 100% shure but I think you'll have to call session.flush() between the operations. It only says that hibernate will have to make things reflected in the database before doing other operations and will not commit your transcation.

I can´t test that right now, but i will try it in a few hours, i´ll tell you if that is the solution of the problem

Thxs all of you

Hi Eugenio, I tested it: delete - flush - insert and it works, thxs for your help, i don't understand well why we have to be aware of using
the flush method, i think that should be hibernate business. Anyway thxs again.

See you.

I'm glad for you

I`ve just realized that you told me the same as Eugenio, thxs both of you

See you