Well, after 5 years of using Dabo, I finally found myself setting the deleteChildLogic to "IGNORE" in one of my bizobjs. I'm really glad it was there!
This was in a M:M situation : case 1 -> styles : style_effect : style_effects case 2 -> orders : openings : opening_styles : style_effect In case 1, any number of styles can be entered, and any number of style_effects can be entered (in separate forms). The Styles bizobj has as a child the StyleEffect bizobj. The StyleEffects bizobj has as a child the StyleEffect bizobj. You use either of those forms to add/remove links. For this case, I want the normal deleteChildLogic of "CASCADE", because if I delete a style, I want all style_effect records of that style to be deleted, too. In case 2, I have the StyleEffect bizobj as a child of the OpeningStyles bizobj as convenience, but when I delete a record in OpeningStyles I don't want to delete any of the children in StyleEffect, as that is "master" information. So it was easy to get what I wanted with a one-liner from my OpeningStyles biz: self.deleteChildLogic = dabo.dConstants.REFINTEG_IGNORE But Ed, what do you think of: 1) Making the child logic atts into properties, for the usual reasons of better documentation and being able to pass the prop to the constructor. 2) Ditching the dConstants thing, and just defining the possible values as "CASCADE", "IGNORE", or "RESTRICT"? Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
