Eric Smith wrote: > > I'm writing a new database dialect for sqlalchemy 0.6 for Netezza. This > is on Windows. I have an ODBC driver for Netezza. A couple of questions: > > - Why isn't there a generic "talk to an ODBC source" dialect? I > thought that was the beauty of ODBC. Is this possible and just > hasn't been done, or is there some technical reason that (for > example) the SQL Server ODBC dialect won't just work?
there is. it is in sqlalchemy/connectors/pyodbc.py . There is also a placeholder for mxodbc if someone wants to take that up. > > - Is there some documentation on writing a dialect, specifically > for 0.6? I've looked around, but not found anything. Or is my > best bet just to look at an existing dialect? you should read the docstring in sqlalchemy/engine/base.py Dialect(), the "type_migration_guidelines.txt" document, as well as "TESTING NEW DIALECTS" in the README.unittests file. From there you'll be looking to emulate the existing dialects for file and object structure. You also should consider if you'd like your dialect to remain as a separate product or be part of inclusion to SQLA core. There's really no downside to maintaining as a separate product since you can release bugfixes on an independent schedule, and is how IBM's DB2 dialect works - your dialect is installed as a setuptools entrypoint "sqlalchemy.dialects.netazza+dbapiname". > > Thanks! > Eric. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
