Recognises a changeable value list fixed in the DDL
A value set implemented as CHECK (... IN (...)) or an enum type although the business changes it. Adding a value needs a migration, a retired value cannot be forbidden for new rows while kept for old ones, and the labels live nowhere. A specific form of row 17: the domain is held in the schema rather than as data.
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 list and the reference table to hold it
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: CHECK (account_status_code IN ('OPN','DOR','CLS')); the bank adds BLK for blocked accounts and rows are rejected until a release Acceptable: ref_account_status with code, label and validity dates, and a foreign key to it; CHECK lists only for value sets fixed by definition (an alethic rule, such as Y/N)
Also known as: Value list fixed in the DDL (physical model)
Related knobits
Builds on
All 40 knobits of Design the physical data model.
Source: Review checklist 06-physical, row 16; Karwin, 31 Flavors; Fagin 1981