fix(duckdb): workaround remaining null map issues #8985
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #8632.
Note that of the backends that support nullable maps, DuckDB is the only one whose
NULL
handling semantics differ.Other backends that support nullable maps and are implemented in Ibis and tested in CI:
hstore
extension)BREAKING CHANGE: Calling the
get
orcontains
method onNULL
map values now returnsNULL
. Usecoalesce(map.get(...), default)
orcoalesce(map.contains(), False)
to get the previous behavior.