Home/ Questions/Q 3315866
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T22:24:05+00:00

I have a grails project that is throwing the following exception: org.springframework.dao.DataIntegrityViolationException: could not

  • 0

I have a grails project that is throwing the following exception:

org.springframework.dao.DataIntegrityViolationException: could not delete: [Role#4]; SQL [delete from role where id=? an
d version=?]; constraint [null]; nested exception is org.hibernate.exception.ConstraintViolationException: could not del
ete: [Role#4]

In my Role domain, all I did to create this error, was change the definition of one of the variables from

 List<RoleTool> roleTools = new ArrayList<RoleTool>()

to

ArrayList<RoleTool> roleTools = new ArrayList<RoleTool>()

Why is that?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It’s bad practice in general to specify a concrete class as the declaration type, both in variable declarations and in method signatures. Unless you really need it to be an ArrayList, leave it as List to allow more flexibility.

    I’m not entirely sure what’s happening here, but Hibernate has its own collections classes that it uses for mapped collections, the most commonly used being org.hibernate.collection.PersistentList and org.hibernate.collection.PersistentSet. These implement the List and Set interfaces respectively, but do not extend ArrayList or HashSet or any typical concrete collection. Instead they’re Hibernate internal classes that monitor changes to help with dirty detection when persisting, flushing, etc.

    It’s fine to declare the initial collection as an ArrayList since it’s only read from when saving (it’s Groovy though, so it’s a lot cleaner to just use List<RoleTool> roleTools = []). But Hibernate needs the flexibility of implementing the List/Set interface when loading persistent instances.

    • 0