-
Notifications
You must be signed in to change notification settings - Fork 45
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
[Feature]: Add Support for on_conflict_do_nothing in SQLAlchemy Integration #1173
Comments
I was able to get something similar to work in my code with:
I still think it would be a great thing to add to the library. |
Can you please provide an example of code that currently errors out? |
@Mause
There is also on_conflict_do_update
|
I see it now. I am importing the insert directly from sqlalchemy. I need to use the postgres insert or Insert method/class. thanks for the help. |
What happened?
Currently, when using the duckdb_engine with SQLAlchemy, the on_conflict_do_nothing method is not supported, resulting in an AttributeError. This feature is essential for handling insert conflicts gracefully without raising exceptions, which is particularly useful for upsert operations and maintaining data integrity.
Additional Context:
This feature is supported in other SQLAlchemy dialects like PostgreSQL and SQLite, and adding it to DuckDB would improve its integration and usability.
DuckDB Engine Version
0.13.6
DuckDB Version
1.1.3
SQLAlchemy Version
2.0.31
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: