Recognises a soft delete the constraints do not understand
Rows marked deleted but still present, with keys and foreign keys unaware of the mark. The deleted row blocks a valid insert, or uniqueness is dropped and active duplicates load, and active rows reference deleted ones.
Can AI do this?
Not tested yet
No AI benchmark covers this knobit yet. New results are announced in the Can AI Do the Job? newsletter.
What it looks like in practice
Expected result: The keys and foreign keys unaware of the flag
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: party.is_deleted; the unique constraint on registry_code includes deleted rows, so the company cannot be registered again; payments keep pointing at a deleted party Acceptable: Uniqueness over active rows only (a filtered unique index where the dialect has one, otherwise a DQ rule); a rule on what may reference a deleted row; views that expose active rows; or deleted rows moved to a history table
Also known as: Soft delete the constraints do not understand (physical model)
Related knobits
Builds on
All 40 knobits of Design the physical data model.
Source: Review checklist 06-physical, row 25; S&W 15.5; this skill (conventions.soft_delete)