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
