Hi!

I have a table with a technical primary-key and a typically business-key (4 attributes in a unique-constraint).

I want now that the method saveOrUpdate throw a ConstraintViolationException or something else before the database is involved when the unique-constraint is violated!

Is this possible to manage in the mapping-file?
I have found something like properties or natural-key or unique-key, but nothing of them did that what i want!?

Is there a solution?

Thanx
Michael J.

I was facing the same problem . You can try adding the constraint to the database table.That works.

Still i am working on a solution using the mapping file

Regards,
Basent V

Thanx for the reply.
The constraint exists in the database.
I have found the Interceptor as solution but thats not really what i want. I want to do it with the mapping file like you! If you found a solution with the mapping file than please post it!

Regards,
Mikel

May be I don't understand what you are trying to do, but, how can you know if a unique constraint is violated before you try to save to the database? I don't think is possible to do with the mapping file, as hibernate does not have a list of the already stored values, unless you have a second level cache (and the data is in the cache)

Hibernate will throw a ConstraintViolationException, but it will be done after trying to save in the database (In fact, the exception, is the result of a database exception)

The only solution, would be to check the database before saving, to see if the key is already present in the database. I do this with foreign keys

By the way, the unique attribute of the property tag, is only useful when automatically generating the database from the mapping files.

I guess i didnt read the question properly. I dont think it is possible to know this; before it hits the database.

Post deleted because it was posted to wrong thread in error, please ignore.