Ben, I'm creating a new "Provider Role" object (in a new Provider Management module). This provider role has an associated set of provider roles representing the other provider roles it can supervise, as well as an associated set of relationship types that the provider role can support. Neither of these should be retired when the parent provider role is retired, but I discovered that they were when writing unit tests for the new provider management service.
Thanks, Mark From: [email protected] [mailto:[email protected]] On Behalf Of Ben Wolfe Sent: Wednesday, March 21, 2012 3:36 PM To: [email protected] Subject: Re: [OPENMRS-DEV] retiring/voided child collections when retiring/voiding an object 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]<mailto:[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<mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> from OpenMRS Developers' mailing list ________________________________ Click here to unsubscribe<mailto:[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]
