That makes sense, and as much as I would volunteer to try to maintain the dialect, I can't see justify using work resources (where I have access to Sybase) to maintain an open source component for a DB we are working to migrate away from.
Since the metadata is collecting ok, minus some type catches I have to do to write to other DB's, I can maybe just write raw SQL through sql alchemy or worst case through pyodbc to deal with collecting the records. Thank you for the help. Ken On Wednesday, November 28, 2018 at 6:12:41 PM UTC-5, Mike Bayer wrote: > > Hi there - > > Unfortuantely, the Sybase dialect is unmaintained and will likely be > removed from a future SQLAlchemy release. For this database to be > usable, a dedicated maintainer would need to volunteer and we can set > them up with a new sybase ASE dialect available as a third party > download. The demand for this database is extremely low, the Python > drivers are poorly maintained and the database itself is extremely > difficult to run for testing purposes. > > -- 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.
