The best way to handle this would be issuing a PR which lists your dialect against this file:
https://github.com/sqlalchemy/sqlalchemy/blob/master/doc/build/dialects/index.rst That is used to build the online documentation for the .org; also Mike is more likely to approve a simple PR that does this, than he will be inclined to write it himself. On Tuesday, January 8, 2019 at 9:50:48 AM UTC-5, Charles Givre wrote: > > All, > John Omernik and I (mainly John) have been working on an SQLAlchemy > dialect for Apache Drill. Our main goal is to get Drill to work with > Apache Superset, but I'm sure it will have other uses. Anyway, I'd like to > ask if the dialect could be included in the SQLAlchemy Docs in the list of > available dialects? > > The link is here: https://github.com/JohnOmernik/sqlalchemy-drill > > Thanks! > -- C > -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
