-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Set nullify to false if not all values are NULL #867
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
base: main
Are you sure you want to change the base?
Conversation
|
Added a reproduction example. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add a test that verifies this behavior?
|
I added a test, but not sure if it works as it seems like I am unable to build... |
What is not working for you? I can try to help you with build process |
Will check in pipeline here as well |
Looks like the pipelines passed, so I guess it's fine. |
|
@dankochetov / @AndriiSherman Any updates on the review status? |
On for example FULL joins, it currently returns the response objects as NULL when the first column in the response is NULL.
This should only happen when the full response object only has NULL values.
In the following example the response you get is the following:
[ { test_table: null, test_table2: null } ]With my fix: