> > Reading this thread, I keep wondering why you are trying to put > all that connection setup configuration into the connection string... > > Such setting are normally configured in the odbc.ini file and then > you just reference data source name in the connection string. > > That's the standard way of using ODBC and the reason why you > have ODBC managers with nice setup GUIs. A DSN-less setup > like the one created by SA bypasses the ODBC manager > configuration. >
Only via an option: DSN connections have been supported for some time via the 'dsn' keyword, the OP seems to either not want that or can't get it to work. > SA should really adapt to the ODBC standard of using data source > names, as it moves the connection configuration where it should be: > Into the scope of the ODBC manager you are using to configure your > ODBC drivers. SA already has a de-facto standard using a db-uri scheme that works with non-ODBC datasources as well. It makes sense for ODBC compliant SA database drivers to conform to that form, not to just displace it and force a config-file style of setup. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
