If an invidual profile test results in a NULL, that was being ignored.
This commit:
Fixes two cases of a string value not being checked for NULL before a comparison.
Converts all profile jinja templates to use COALESCE(..., FALSE) for field values - so that an individual NULL check won't survive to any result tables.
For q_valid_us_core_v4 also confirm that "valid" isn't NULL (which should never be true because of the above, but... defense in depth)
Hopefully this will let us notice such invalid NULL checks earlier, by having the rows be flagged as failing the metric.
If an invidual profile test results in a NULL, that was being ignored.
This commit:
Hopefully this will let us notice such invalid NULL checks earlier, by having the rows be flagged as failing the metric.
NULLs and SQL are really annoying.