Details
-
Bug
-
Resolution: Fixed
-
Critical
-
None
Description
Deleting a matchgrid object (and related objects) should first put up a warning and delete the physical (mg_foo) table before removing the matchgrid object itself.
Attachments
Issue Links
- is related to
-
CO-2579 Deleting Matchgrid that has History Records throws foreign key violation
- Resolved