simonfranken/timetracker
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Restore onDelete: Cascade on Project->Client and TimeEntry->Project

Browse Source 
Direct database deletes should still cascade to avoid orphaned records.
The migration now only adds the three deleted_at columns without touching
the existing FK constraints.
This commit is contained in:
simon.franken
2026-02-23 15:32:31 +01:00
parent 159022ef38
commit 1b0f5866a1
2 changed files with 2 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
backend/prisma/migrations/20260223200000_add_soft_delete/migration.sql
View File

@@ -6,15 +6,3 @@ ALTER TABLE "projects" ADD COLUMN "deleted_at" TIMESTAMP(3);
-- AlterTable: add deleted_at column to time_entries
ALTER TABLE "time_entries" ADD COLUMN "deleted_at" TIMESTAMP(3);
-- DropForeignKey: remove cascade from projects -> clients
ALTER TABLE "projects" DROP CONSTRAINT "projects_client_id_fkey";
-- DropForeignKey: remove cascade from time_entries -> projects
ALTER TABLE "time_entries" DROP CONSTRAINT "time_entries_project_id_fkey";
-- AddForeignKey: re-add without onDelete cascade
ALTER TABLE "projects" ADD CONSTRAINT "projects_client_id_fkey" FOREIGN KEY ("client_id") REFERENCES "clients"("id") ON DELETE RESTRICT ON UPDATE CASCADE;
-- AddForeignKey: re-add without onDelete cascade
ALTER TABLE "time_entries" ADD CONSTRAINT "time_entries_project_id_fkey" FOREIGN KEY ("project_id") REFERENCES "projects"("id") ON DELETE RESTRICT ON UPDATE CASCADE;