Skip to content
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

feat(duckdb): allow all-null columns in memtables #8367

Merged
merged 1 commit into from
Feb 16, 2024

Conversation

cpcloud
Copy link
Member

@cpcloud cpcloud commented Feb 15, 2024

Turns out we are artificially restricting the input of all-null columns in memtables. This works out of the box by simply deleting the check that raises an exception.

@cpcloud cpcloud added this to the 9.0 milestone Feb 15, 2024
@cpcloud cpcloud added feature Features or general enhancements duckdb The DuckDB backend labels Feb 15, 2024
Copy link
Member

@kszucs kszucs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

@kszucs kszucs merged commit b2ae64a into ibis-project:main Feb 16, 2024
78 checks passed
@cpcloud cpcloud deleted the remove-all-null-column-limitation branch February 16, 2024 13:11
ncclementi pushed a commit to ncclementi/ibis that referenced this pull request Feb 21, 2024
Turns out we are artificially restricting the input of all-null columns
in memtables. This works out of the box by simply deleting the check
that raises an exception.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duckdb The DuckDB backend feature Features or general enhancements
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants