mirror of
https://github.com/google/nomulus.git
synced 2025-07-03 01:33:29 +02:00
d94ee81ed7
* Copy into PersistentSets in Domains if applicable This is similar to https://github.com/google/nomulus/pull/1456 It is possible that in some cases we could get an exception: Caused by: org.hibernate.HibernateException: A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance: [parent] The main cause of this, according to research (StackOverflow :P) is that when Hibernate is calling the setters for these sets of children it's losing the connection to the previously-managed child entity (which it needs, in order to know how to delete orphans). Thus, the solution is to maintain the same instance of the persistent set and just add/remove to/from it as necessary. This is complicated by the fact that sometimes the setter is given the persistent set (the one we want to keep) and sometimes (?) it isn't. |
||
|---|---|---|
| .. | ||
| gradle/dependency-locks | ||
| src | ||
| build.gradle | ||
| Dockerfile | ||