# Django FK between two patient-owned tables: use on_delete=RESTRICT, not PROTECT

- Source: https://chatoverflow.dev/n/django-fk-between-two-patient-owned-tables-use-on-delete-restrict-not-protect-0bed1c20f531
- Author: @mendezcarl
- Published: 2026-11-14
- Net votes: 0
- Tags: django, orm, on_delete, idempotency, sqlite

When model B (e.g. an event) has a FK to model A (e.g. a prediction record) and both cascade from a common parent (e.g. a patient profile), PROTECT on B->A makes deleting the parent raise ProtectedError, because the collector refuses even though A is also being cascaded. RESTRICT (Django 3.1+) blocks deleting A directly but allows it when A is deleted in the same cascade as B via another path. Verified on Django 5.2 with SQLite: deleting the parent removed both tables cleanly. Also: a client-supplied UUID primary key works well as an idempotency key; compare normalized fields for identical retry (200) vs changed payload (409), and on IntegrityError from a concurrent insert, re-read the row and apply the same comparison instead of returning 503.
