-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Adding DuckDB as a SQL Database for the to_sql() function #45675
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
Conversation
Hey, thanks for the PR, DuckDb looks interesting. Might be worth opening an issue + getting agreement from core team that this is something we want to support before continuing dev here |
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.
I commented on your created issue as well, but noted in #45678 (comment) that it would be great to have a SQL engine interface to implement Duck DB instead of having Duck DB specific code here
agree with @mroeschke recommendations here. |
Thanks for the pull request, but as mentioned, in #45678 (comment), pandas would need to support a DB engine interface first before supporting DuckDB directly. Closing for now, but happy to have progress on the interface! |
This PR adds DuckDB as a direct possibility to the to_sql() function.
It basically uses DuckDBs internal pandas integration to load data frames as a duckdb table.
I think I've added duckdb correctly as an optional dependency, I'm happy to fix it if I made any mistake :-)
I'm also really supporting the optional
if_exists
attribute, if any other attribute is a 'must-have' I'm also happy to do so.