[b/330573524] Prevent IF from treating NULL as FALSE #49
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.
Tableau offers the
IIF
function with the signatureIIF(bool, val1, val2[, val3])
. Ifbool
isTRUE
, it returnsval1
, if it isFALSE
, it returnsval2
, and if it isNULL
, it returnsval3
if provided, otherwise it returnsNULL
.Previously, we translated this behavior by rewriting it as BigQuery's
IF
. The issue however, is that ifbool
isNULL
, BigQuery defaults toval2
instead ofNULL
orval3
.This commit corrects for that by wrapping the expression in another
IF
that checks ifbool
isNULL
. If it is, it returnsval3
if specified, otherwiseNULL
. Ifbool
is not null, it follows normalIF
behavior.