Ticket #1012 (closed defect: wontfix)

Opened 1 year ago

Last modified 1 year ago

Honor foreign key constraints on delete for self.deleteChildLogic=k.REFINTEG_CASCADE

Reported by: uwe_grauer Assigned to: somebody
Priority: major Milestone: 1.0
Component: biz Version:
Keywords: Cc:

Description

If you have a form with master-detail relationships which has set self.deleteChildLogic=k.REFINTEG_CASCADE and you try to delete a master record dabo doesn't honor database foreign key constraints. It first deletes the master record and then the child records.

This leads to a database exception if there are foreign key constraints set up in the database.

Turn logic into first deleteing the child records and then the master record.

Change History

03/02/07 16:19:14 changed by ed leafe

  • status changed from new to closed.
  • resolution set to wontfix.

This is misguided. The bizobj referential integrity is there for backends that do not support it. This has been explained on the email list.

Use one or the other. Not both.

03/02/07 16:35:22 changed by uwe_grauer

  • status changed from closed to reopened.
  • resolution deleted.

Please explain why it is misguided. Would this produce errors? Why is turning the logic around a bad thing?

03/03/07 02:46:17 changed by uwe_grauer

  • status changed from reopened to closed.
  • resolution set to wontfix.

The decision was made to not fix the issue. Search the archive if you want to get more information on this. Subjects containing: "how to delete childrecords when deleteing parent?" "Honor foreign key constraints on delete for self.deleteChildLogic=k.REFINTEG_CASCADE"