-
1. Re: Envers Set merge / ManyToOne Cascade Update Problem
adamw Aug 21, 2012 3:51 AM (in response to freakmaster)1. No, there is currently no way like that to link back to historical entities. You will have to keep the revision number I guess and read it on-demand.
2. That's correct, as the Patient entity isn't changed (whether Patient is changed when you add/remove an Untersuchung is discussable and configurable. No way to automatically change the Patient, as there's no way to know which entities are in the same graph.
Adam
-
2. Re: Envers Set merge / ManyToOne Cascade Update Problem
freakmaster Aug 21, 2012 8:08 AM (in response to adamw)Ok, thank you for securing my assumption.
@1: due to the incomparability of revisionEntity and currentEntity (entityManager.contains(revisionEntity and vice versa) always returns false, even it's the same entity)
so I put both on Hashtables (with objectId as id) to compare it and create a delete- and a mergePersistList, which I have to
remove/merge manually.
@2: So, I will create a "dirty" solution and add or delete a blank of a text-column in the (One) Patient during the update of (Many) Untersuchung
to keep it current.
Thank you Adam for doing such great work here!