-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Critical
-
Affects Version/s: None
-
Component/s: Match
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.
- is related to
-
CO-2579 Deleting Matchgrid that has History Records throws foreign key violation
-
- Resolved
-