-
Notifications
You must be signed in to change notification settings - Fork 590
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
refactor(sql): remove sqlalchemy from the codebase #8074
Conversation
0eff8fb
to
591d38a
Compare
3f7d544
to
a89cea5
Compare
edda7ea
to
dc2fa81
Compare
|
As part of this I discovered that pydruid has an inadvertent hard dependency on sqlalchemy: druid-io/pydruid#313 I've also submitted a PR there to address the issue. If this doesn't get merged before the 9.0 release then it's probably time to consider removing the druid backend. |
Wouldn't that only affect those that installed |
|
It's not a blocker technically speaking, except that we still have to list sqlalchemy somewhere. Perhaps it is enough to pass the |
|
Ok, that seems to work and not cause a huge number of headaches AFAICT but I am still a bit 😒 🤣 |
dc2fa81
to
e028780
Compare
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.
Nice
|
Ok, I've had enough of it with quoting. I'm going |
|
The remaining duckdb failures are due to quoting, which should be fixed after #8172 is merged into |
432d151
to
e4df99b
Compare
3514106
to
e1e10d6
Compare
5dd75af
to
78ab2dc
Compare
78ab2dc
to
256cbd8
Compare
|
Clouds are passing: |
|
The DuckDB windows failure is a transient network issue during installation, I'll restart the job once the others finish, and then merge this PR. |
|
Nice! Thanks @cpcloud! |
This PR removes sqlalchemy from the codebase.