The setting for bizobj.deleteChildLogic shows up as 3. Was this because I did a self.addChild in my primary bizobj def?
If the backend has referential integrity enforcement capability such as Postgresql, I am inclined to set the deleteChildLogic to 1. The issue was gone after I set the deleteChildLogic attribute to 1. Thanks Ed. On Mon, Jul 13, 2009 at 7:36 AM, Ed Leafe<[email protected]> wrote: > On Jul 12, 2009, at 4:57 PM, tim awa wrote: > >> My delete button on a form with a parent and child grids have the >> following code: >> >> self.Form.delete() >> >> It deletes the parent without issues if there are no child records. >> >> If I delete a parent in Postgresql directly, the ON DELETE CASCADE >> setting deletes the child records accordingly. >> >> The delete button in my Dabo application somehow deletes both parent >> and child records but the application freezes immediately after the >> click. > > Do you have referential integrity logic in both the database and in > the application? Perhaps that's what's hanging the app. Can you add > some debugging to your bizobj to determine what the setting for its > 'deleteChildLogic' attribute is? The possible values are: > > REFINTEG_IGNORE = 1 > REFINTEG_RESTRICT = 2 > REFINTEG_CASCADE = 3 > > So it bizobj.deleteChildLogic == 3, you could have the problem you > are seeing. > > > -- Ed Leafe > > > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
