diff --git a/content/feed/sas-special-missings/index.md b/content/feed/sas-special-missings/index.md index 428f066..282576f 100644 --- a/content/feed/sas-special-missings/index.md +++ b/content/feed/sas-special-missings/index.md @@ -48,7 +48,7 @@ These are Data Controller's own rules, configured per column in the `MPE_VALIDAT - `NOTNULL` - works the same as SAS: cannot use special missings. A special missing is NULL to a NOT NULL (or primary key) constraint, so the rule rejects it, and so does a physical constraint on the target table - `HARDREGEX` - checked against the pattern like any other value; unlike blanks and the plain `.`, special missings are **not** exempt, so a numeric column that carries them needs a pattern which allows for a single letter - `SOFTREGEX` - the same check, but a failure is only a warning rather than a block, and it is ignored entirely if the column also has a `HARDREGEX` rule -- `SOFTSELECT` - never blocks, so a special missing passes; `HARDSELECT` is a strict membership test, so it passes only when the dropdown list contains it +- `SOFTSELECT` / `HARDSELECT` - both support special missings; a soft dropdown never blocks a value, and a hard one lists them alongside the ordinary values - `ROUND` - harmless. It only rounds values that are numbers, so a special missing is left exactly as it was typed Special missings are **not supported** in a column that carries a range rule or a formula: @@ -96,7 +96,7 @@ How they behave in Data Controller's validation rules: - NOTNULL works the same as SAS - no special missings: one is null to a NOT NULL (or primary key) constraint - HARDREGEX checks it against the pattern, unlike blanks and plain . - SOFTREGEX warns instead of blocking (and is ignored if the column also has a HARDREGEX) -- SOFTSELECT lets it through; HARDSELECT only when the dropdown list contains it +- SOFTSELECT and HARDSELECT both support them - ROUND leaves it alone, because it only rounds numbers Special missings are not supported where a range rule or a formula is configured: