On Wed, Apr 2, 2008 at 6:22 PM, Rick Morrison <[EMAIL PROTECTED]> wrote: > > also of concern is that, nobodys ever going to know they need to use this > parameter when this issue arises. > > Well the idea is that this is a workaround for what I suspect is a broken > Unix + pyodbc configuration, not a long-term solution. > > > > > its only because I narrowed the issue down to where I knew we needed those > names to be that it was identified.
So how would I find out if this is pyodbc or unixodbc? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
