Recognises an overwrite where history is required
A table updated in place although a data rule or requirement needs past states. Audit columns (updated_at, updated_by) record only the last change and are not history.
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 table and the history strategy it needs
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: account updated in place, updated_at taken as its history; last year's interest-rate report cannot be reproduced Acceptable: A history strategy chosen per table from the temporal rules (06-physical.md: effective dating, SCD type 2, history table, bi-temporal) and recorded in the table's comment
Also known as: Overwrite where history is required (physical model)
Related knobits
Builds on
All 40 knobits of Design the physical data model.
Source: Review checklist 06-physical, row 22; S&W 15.2–15.3; DDL 2014 ch. 17