Tim, I committed a patch from ticket #480 today from that adds some improved module-switching code to the MSSQL interface. See how that works for you.
On 3/16/07, Tim Golden <[EMAIL PROTECTED]> wrote: > > > Rick Morrison wrote: > > Sorry, Stephen, I replied too early; your second email arrived before > the > > first. A whole day before the first. > > > > So until we get a real cleanup, you're looking to try modules in this > order: > > > > ['pyodbc', 'adodbapi', 'pymssql'] > > > > Sounds OK to me -- any objections out there? > > Looks good to me. > > I got slightly confused somewhere through this thread. > When I was putting a test together for the passthrough > patch, I ended up using an Import hook to force a > particular dbapi module to be used programatically > (given that I have all three installed). > > Obviously there are variations on that (manually renaming > one etc) but have I missed anything more sophisticated > using SA itself? Didn't look like it to me from the code. > > TJG > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
