rohit/probo
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Rename snapshot cleanup migration and use third_parties table

Browse Source 
Signed-off-by: Sacha Al Himdani <sacha@getprobo.com>
This commit is contained in:
Sacha Al Himdani
2026-05-20 12:46:54 +02:00
parent f41dd9566b
commit ec2bbccdbd
1 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
pkg/coredata/migrations/20260506T150405Z.sql → pkg/coredata/migrations/20260520T104358Z.sql
View File

@@ -17,14 +17,14 @@
-- table, controls_snapshots, snapshots_type enum, snapshot-scoped indexes) is
-- dropped in a follow-up migration.
-- processing_activity_vendors stores snapshot_id without an FK to snapshots, so
-- the cascade delete below would not reach it. Clean it up explicitly first.
DELETE FROM processing_activity_vendors WHERE snapshot_id IS NOT NULL;
-- processing_activity_third_parties stores snapshot_id without an FK to snapshots,
-- so the cascade delete below would not reach it. Clean it up explicitly first.
DELETE FROM processing_activity_third_parties WHERE snapshot_id IS NOT NULL;
-- Every other table with a snapshot_id has a FOREIGN KEY (snapshot_id) REFERENCES
-- snapshots(id) ON DELETE CASCADE, so deleting all snapshots removes every
-- snapshot-scoped row across data, vendors, assets, risks, findings, obligations,
-- processing_activities, statements_of_applicability, applicability_statements,
-- the vendor_* sub-tables, the processing_activity DPIA/TIA tables, and the
-- controls_snapshots junction.
-- snapshot-scoped row across data, third_parties, assets, risks, findings,
-- obligations, processing_activities, statements_of_applicability,
-- applicability_statements, the third_party_* sub-tables, the processing_activity
-- DPIA/TIA tables, and the controls_snapshots junction.
DELETE FROM snapshots;