org.hibernate.exception.ConstraintViolationException: could not execute statement
The database rejected an insert/update because of a constraint (unique, foreign key, not null).
could not execute statement Meaning
Hibernate wraps the JDBC error; the root cause at the bottom of the stack names the constraint (e.g. Duplicate entry, violates foreign key constraint).
Common causes
- Duplicate unique value
- Missing referenced row (FK)
- NULL in a NOT NULL column
- Bean Validation (jakarta.validation) annotations not checked before save
⚡ Quick fix
- Scroll to the root cause for the DB message
- Validate before saving
- Translate to a 409/422 response in your API
Detailed fix by platform
Java
- Spring: catch DataIntegrityViolationException at the service/controller boundary
How to diagnose
- Root cause — Which constraint?
- Data — Which value violates it?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Java
Other ways to find it
Where this error sits
Origin: Application & API. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 12 Oct 2026