[Bug] Null values

[dinoDayo]

Is this a new bug in dbt-core?

• I believe this is a new bug in dbt-core
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

I have not been able to find anything in the documentation or the code base that explains how DBT recommends managing null values. A solution to this problem would be extremely helpful.

For example, consider I have model A which is dependent on model B. When I define a null value in model B, that value is converted to None when I reference that value in model A. This makes data management and analysis extremely difficult. I believe the built-in method for identifying whether or not a value is equal to null in dbt core would address this problem for me. If such a function exists, an example of how to use it would be much appreciated.

Thank you for your time.

Expected Behavior

I would expect that a null value is consistently null as it is passed between different models and macros.
At this point I am converting them to adapter.quote('NULL'), which results in "'NULL'", which I can then convert to null values at the end of the model definition. This is not ideal though.

Steps To Reproduce

Define a table with null values and then reference those null values in another model. In the downstream model the null values will be versed to None.

Relevant log output

Environment

- OS:
- Python:
- dbt:

Which database adapter are you using with dbt?

No response

Additional Context

No response