This repository has been archived by the owner on Mar 11, 2021. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PLEASE: DO NOT MERGE WHEN THERE'S ONLY ONE APPROVAL.
See https://github.com/fabric8-services/fabric8-wit/blob/12f42bbe747f33bf0e3fe485d35ff66ac021d613/docs/cascading-soft-delete.md#cascading-soft-deletes for a description of what this PR does and why.
In addition to adding the cascading soft-delete mechanism for our complete database, I had to make a few adjustments to some tables:
Delete no longer needed
work_item_link_categories
categories that is no longer used since migration 106.Add missing foreign key constraint from
comments
towork_items
item and delete all comments that don't reference a work item.Change foreign key from
tracker_items
andtracker_queries
totrackers
fromON UPDATE RESTRICT ON DELETE RESTRICT
toON DELETE CASCADE
.Change foreign key from
identites
tousers
toON DELETE CASCADE
.Implements [4] When a workitem is deleted, all links associated with it are deleted of Delete workitem #2304
Addresses Work items are not deleted when space is removed openshiftio/openshift.io#4382