-
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
MySQL backend #1224
Comments
|
This would also provide MemSQL support. I will see if anyone from over there would be interested in contributing |
|
Sounds great, thanks! |
|
@kszucs This should be based on the |
|
@cpcloud BTW what's the advantage of maintaining both sqlalchemy and custom compiler backends? |
|
Depends on how well sqlalchemy supports the underlying SQL backend. In the case of Impala and BigQuery there's a lot of stuff that is challenging to support in SQLAlchemy (or maybe it's that we don't know how to use it well enough) |
|
I get it, but also bothers me a bit. When I look at ibis' custom compiler it feels like another sqlalchemy. Couldn't we move away from either one? (I know there are pros&cons for both backend types) |
I guess mysql would be a nice to have backend.
Should it be based on the alchemy backend or the sql compiler (like impala, clickhouse and bigquery)?
The text was updated successfully, but these errors were encountered: