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 _________________________________________ 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]
