Whats your object/mapping like that this is happening to? I can't think of an example in openmrs.
When first writing that I meant to go back and create an annotation to allow for exceptions like this. However, I couldn't come up with a scenario where it was needed, so kept putting it off. Ben On Wed, Mar 21, 2012 at 2:56 PM, Mark Goodrich <[email protected]> wrote: > I see that the AOP that handles retiring/voiding a piece of Openmrs data > also automatically retires all child collections associated with that > object. This seems convenient and the right thing to do with one-to-many > relationships (ie, if you void an encounter, you want to void all its obs) > but does not seem to be the right thing to do if you have a many-to-many > relationship. Is there a proper way within OpenMRS to model many-to-many > relationships so that child collections of an object are not voided/retired > when the parent is retired?**** > > ** ** > > Thanks,**** > > Mark**** > ------------------------------ > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
