dc/docs.datacontroller.io
6
1
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

docs(validations): document how each rule treats a special missing value #8

Open
hermes wants to merge 4 commits from docs/special-missing-rule-behaviour into main
pull from: docs/special-missing-rule-behaviour
merge into: :main
Conversation 0 Commits 4 Files Changed 1
+4 -2
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit e7fdb3ab52 - Show all commits
docs/dcc-validations.md
+4 -2
View File
@@ -60,10 +60,12 @@ The rules treat a special missing as a value for some checks and as a missing va
|ROUND|Ignored - ROUND only rounds values that are numbers, so a special missing is left as typed.| |ROUND|Ignored - ROUND only rounds values that are numbers, so a special missing is left as typed.|
|HARDREGEX / SOFTREGEX|Checked against the pattern like any other value. Unlike blanks and the plain `.`, special missings are **not** exempt. See [Regex Rules](#regex-rules).| |HARDREGEX / SOFTREGEX|Checked against the pattern like any other value. Unlike blanks and the plain `.`, special missings are **not** exempt. See [Regex Rules](#regex-rules).|
|SOFTSELECT|Passes - a soft dropdown never blocks a value.| |SOFTSELECT|Passes - a soft dropdown never blocks a value.|
|HARDSELECT|Fails - the strict membership test cannot match it (the dropdown list for a numeric column holds numbers).| |HARDSELECT|Checked against the dropdown list like any other value - it passes only if the list contains it.|
|HARDFORMULA / SOFTFORMULA|The formula returns `#VALUE!` for that row instead of a number, and that is what gets submitted.| |HARDFORMULA / SOFTFORMULA|The formula returns `#VALUE!` for that row instead of a number, and that is what gets submitted.|
In short, a special missing is **not supported** in a column that carries NOTNULL, MINVAL, MAXVAL, HARDSELECT or a formula. It is fine alongside the regex rules, a soft dropdown, and ROUND. In short, a special missing is **not supported** in a column that carries NOTNULL, MINVAL, MAXVAL or a formula. It is fine alongside the regex rules, a soft dropdown, and ROUND.
A primary key column is treated as NOT NULL whether or not the target table carries a physical constraint, and whether or not MPE_VALIDATIONS has a NOTNULL rule for it - a key identifies the row, so a blank and a special missing are both rejected there.
One related gotcha: a range rule's own value must be a number. Put a special missing in `MINVAL` and every cell in the column fails; put one in `MAXVAL` and every real number fails. One related gotcha: a range rule's own value must be a number. Put a special missing in `MINVAL` and every cell in the column fails; put one in `MAXVAL` and every real number fails.