ISO / ANSI compliant join option

[SeanAdams]

Most databases treat null as "unknown" and as a result, null fails all comparisons in SQL.    For example, null does not match to null in a join, null will fail any > or < tests etc.    This is an ANSI and ISO standard behaviour.

Alteryx treats null differently - if you have 2 data sets going into a join, then a row with value null will match to a row with value null.

We've seen this creating confusion with our users who are becoming more fluent with SQL and who are using inDB tools - where the query layer treats null differently than the Alteryx layer.

Could we add a setting flag to Alteryx so that users can turn on ISO / ANSI standard processing of Null so that data works the same at all levels of the query stack?

Many thanks

Sean

[cgoodman3]

The expectation would be to follow the industry standards (iso) where they exist. Where they don’t I would like to see Alteryx being in step with other languages such as SQL for how you do things.

[MarqueeCrew]

I'll drink to that!!!

[simonaubert_bd]

Hello,

My 2 cents : I'm all in favor of following ISO/ANSI norms when it can apply. However, I'm not sure it should apply as a default for in-memory on Alteryx because of legacy compatibility. I would rather have two options :
-System settings
-Join tool settings

Best regards,

Simon