-
Notifications
You must be signed in to change notification settings - Fork 608
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: unbound table
error even after setting default_backend
#8677
Comments
Thanks for the excellent reproducible example - this is indeed a bug. For now you should be able to change your code to get a bound table instead of an unbound table doing either: ...
t = con.create_table("test", pd.DataFrame(data))
# OR
t = con.table("test") # retrieve the table `test` later on
... |
I'm not sure this is a bug. An Do we really want to start trying to turn all unbound tables into bound tables simply because the default backend was set? |
Yeah, I realized that after commenting. I think the only thing to do here is update the error message to not provide incorrect advice (done in #8695). |
Previously this gave wrong advice to set the default backend. Fixes #8677.
What happened?
Executing a query with
ibis.<backend>.execute()
throws an error even ifdefault_backend
is setCode to replicate the issue:
What version of ibis are you using?
8.0.0
What backend(s) are you using, if any?
DuckDB
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: