Hibernate - how to catch "integrity constraint violation: unique constraint or index violation"

Question

In my table I have a unique constraint. In hibernate, when I add an item that violates that constraint, I want to catch it, so It will update instead of create an item.

When I set no try-catch block around

    updated = query.executeUpdate();

it gets following error

    Caused by: org.hsqldb.HsqlException: integrity constraint violation: unique constraint or index violation: WEEKROOSTERITEMUNI

When I set the following try-catch block

    try {
        updated = query.executeUpdate();

     }    
   catch(PersistenceException e){                                                         
        LOG.debug("this is PersistenceException exception throw");      
    }

it gets the following error

    Caused by: javax.persistence.RollbackException: Transaction marked as rollbackOnly

When I catch "ConstraintViolationException" I just keep getting the constraint exception, it doesn't catch anything.

    Caused by: org.hsqldb.HsqlException: integrity constraint violation: unique constraint or index violation: WEEKROOSTERITEMUNI

How can I catch this?

Suggest to go through this link in SO [SO Link][1] [1]: http://stackoverflow.com/questions/2167730/checks-for-constraint-violation-before-persisting-an-entity — aksappy, Nov 14 '13 at 08:58

score 0 · Answer 1 · answered Nov 14 '13 at 08:57

0

To catch unique constraint you should catch this exception ConstraintViolationException

answered Nov 14 '13 at 08:57

mvb13

1,514
3
18
33

When I do this, it doesn't catch anything, I just keep getting "Caused by: org.hsqldb.HsqlException: integrity constraint violation: unique constraint or index violation: WEEKROOSTERITEMUNI" – Ken Vernaillen Nov 14 '13 at 08:59
Did you try to catch HibernateException? – mvb13 Nov 14 '13 at 09:04
I catch it with a DataIntegrityViolationException exception – toquart Jul 20 '17 at 19:57

score -1 · Accepted Answer · edited Aug 28 '17 at 12:07

-1

The RollbackException is thrown at a higher level because @Transactional is set in that higher lever, so you can't catch it on that level. You need to catch it in the layer of your transaction.

A better way is to do a check if the object already exists on the database layer. A check-function. That check function is a get by the unique constraints. This is better because you don't need to catch exceptions.

You already need that get-function of the object, because you later want to merge that object. You don't want to merge a detached instance.

edited Aug 28 '17 at 12:07

Mohammad Faisal

5,783
15
70
117

answered Nov 14 '13 at 09:22

Ken Vernaillen

859
1
7
37

6

This doesn't work in the face of concurrent access to the database. Between the time you check and the time yo do something else, another session may have changed the database state. – WW. May 24 '18 at 00:51

Hibernate - how to catch "integrity constraint violation: unique constraint or index violation"

2 Answers2