Reject unknown imported cities from queries #2675
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
This commit fixes a bug where the city report returned
N/A
entries. The functions that build imported data queries were using SQLCOALESCE
, assuming city data isNULL
when unknown, when actually its unknown value is0
.This commit addresses the problem using SQL
NULLIF
combined with the previousCOALESCE
call. With this change both0
andNULL
are treated as unknown.Since 1cb07ef cities can be
NULL
, but previously we saved0
as unknown.Closes #1960
Tests
Changelog
Documentation
Dark mode