amotl commented on PR #29243: URL: https://github.com/apache/superset/pull/29243#issuecomment-2168741417
Hi @john-bodley. Thanks for asking. > What was the main reason for splitting this work out, i.e., why isn't it viable to simply update the SQLAlchemy dialect for the former? The Python DBAPI HTTP driver is stable, and does not receive many changes any longer, actually mostly none. This is by far not the case with the SQLAlchemy dialect. To get an idea about the relevant traffic, let us enumerate the whole stack of requests and improvements already queuing up. - https://github.com/crate/crate-python/issues?q=is%3Aissue+is%3Aopen+sqlalchemy - https://github.com/crate/sqlalchemy-cratedb/pulls In particular, that patch demonstrates that the HTTP driver is not necessarily tied to the SQLAlchemy dialect, and vice versa. - https://github.com/crate/sqlalchemy-cratedb/pull/11 In this spirit, we decided to split concerns between those two artefacts, by separating them into two different repositories. Currently, the SQLAlchemy dialect still exclusively uses the HTTP driver, but it will give users a choice after the aforementioned patch has been integrated. Let us know about any further questions you may have on this topic. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
