Deletion, Referential Actions & Lifecycle Design what happens when related data disappears
Phase 10 - Relational Data Modeling Volume 03 - Database Engineering
↓
↓
Phase 10 decides what the durable data should mean before Phase 11 writes application behavior against it.
Delete is a business operation A foreign key answers whether related rows may exist. A referential action answers what the database should do when the referenced row is updated or deleted. This should follow ownership and retention requirements.
Cascade Delete children automatically Strong ownership, e.g. project-local tasks
Restrict / NoAction Block parent deletion Records must be handled deliberately
SetNull Keep child, clear optional reference Optional assignee/reference
Application-managed Service performs explicit archival/deletion workflow Audited enterprise processes
TaskFlow lifecycle choices Relationship Suggested behavior Reason
Workspace -> Project Cascade in learning model Projects have no meaning outside workspace
User -> Membership Cascade/explicit cleanup dependingMembership audit needs depends on user identity
workspace Workspace @relation(fields: [workspaceId], references: [id], onDelete: Cascade) assignee User? @relation(fields: [assigneeId], references: [id], onDelete: SetNull)
Soft deletion is not free Adding deletedAt looks simple but changes almost every query, uniqueness rule, reporting workflow, restore behavior and index strategy. Do not add soft deletion merely because enterprise systems often use it. Production retention requirements may require archival instead of cascading hard deletes. The course model teaches relational ownership, but a regulated HRIS or accounting system should derive lifecycle from explicit retention policy.
Exercise Choose and justify an on-delete behavior for comments, file attachments, activity log rows, and workspace invitations. There is no universally correct answer; the point is to connect lifecycle semantics to referential actions.
Deletion Referential Actions and Lifecycle matters because it changes a real boundary in TaskFlow. The goal is to understand the inputs, owner, observable output, and failure modes before adding more abstraction.
Restate the goal of “Deletion Referential Actions and Lifecycle” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: business noun → invariant → table/relation → constraint → query shape. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: A complete Prisma/ER model for TaskFlow core entities with keys, relation tables, uniqueness, and important indexes.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
Input -> owner -> transformation -> observable output -> failure evidenceDo not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Return to the nearest observable boundary: input, network, process log, database, or rendered UI. Compare actual evidence with the predicted path.
Change one variable at a time and reproduce the original failure after the fix; otherwise you have correlation, not diagnosis.
Without copying the final source, create a second small scenario that applies “Deletion Referential Actions and Lifecycle” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Add comments and timestamps with intentional delete behavior.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.JSON arrays replacing relational join tables without reason
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.