-
Notifications
You must be signed in to change notification settings - Fork 77
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
Executing 2 statements within %%sql fails in DuckDB #674
Comments
hi @Alex-Monahan, I was able to reproduce the issue. I believe we introduce this when we added support for generic DB API drivers, we'll fix it! |
Thank you as always! Having this be a living, breathing, improving project is tremendous. Awesome stuff! |
hey @Alex-Monahan, update: while working on fixing this we realized that there's some deeper bug involved. so thanks a lot for bringing this up! It'll take a bit more time than expected to fix it but we'll take care of it |
hey @Alex-Monahan this has been fixed in 0.9.0, which we released just now! Sorry it took so long; we found out this and other issues were related so we decided to do a big refactoring to close them all at once instead of doing some quick patch. if you have any other problems, feel free to open another issue! |
Great! It's working again in my test case. Thanks for all the work you to do integrate with DuckDB! |
Hello! I believe this behavior used to work and that this is a regression. It may be related to the pandas output setting.
Here is a google collab that can reproduce the issue: https://colab.research.google.com/drive/1xKjvILJkydM5R095GOVo3hf8446-iZa9?usp=sharing
The text was updated successfully, but these errors were encountered: