-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] null values should be of type null and not of type string in manifest.json #74
Comments
This issue persists in the 1.4 RC release |
Python The issue you reported is only the case with database field because of how
The reason is some validation enforced by dbt. if you change database's default value to
If default value could be declared |
Ok - let me rais an issue then in dbt-core. |
I left a comment on the I haven't been able to look into it extensively, but following the precedent in |
Is there an existing issue for this?
Current Behavior
Null values are rendered as proprietary "None" string fields in manifest.json.
https://getdbt.slack.com/archives/C01PWH4TXLY/p1677050123391359
Expected Behavior
Null values are rendered as valid JSON nulls in manifest.json
Steps To Reproduce
dbt run
for version 1.3.2 of dbt-oracle
Relevant log output using
--debug
flag enabledNo response
Environment
What Oracle database version are you using dbt with?
11
Additional Context
No response
The text was updated successfully, but these errors were encountered: