-
Notifications
You must be signed in to change notification settings - Fork 41
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]: MetaData.reflect() raises exception with sqlalchemy v2.0.36 #1128
Comments
Hello! I've taken a look at both this codebase and the sqlalchemy codebase and I think I have an idea for how to fix the problem. My group and I are students at the University of Toronto so we'd love to take a crack at this issue! |
Hello @Mause! We were able to make a fix for this but we'd like someone to review the code, is it possible that I could be made the assignee to create the PR? |
@Aarya2004 you should be able to create the PR without needing to be an assignee. You will need to make a fork of this repo, push your commits to a branch there, and then submit a PR from that branch to here. If you need help with that let me know |
Hey @NickCrews, thank you so much! We've created the PR but we'd appreciate a code review if possible. Thanks for the tip! |
SQLAlchemy 2.0.36 introduces a regression when creating a table in DuckDB. Relevant issues: - In SQLAlchemy repo (resolution is to update DuckDB): sqlalchemy/sqlalchemy#12011 - In DuckDB repo (PR is open): Mause/duckdb_engine#1128 Plan is to track these issues and remove cap when resolved.
What happened?
This commit in sqlalchemy v2.0.36 causes a regression when creating a table in DuckDB. A SQLAlchemy developer says that this package will need to override the new statement.
DuckDB Engine Version
0.13.2
DuckDB Version
1.1.2
SQLAlchemy Version
2.0.36
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: