I tried 0.8 with 0.6b1 but didn't work. Both 0.8 and 1.0.2 work with sqla 0.5.8 without problems.
I began trying using pyodbc in ubuntu yesterday but can't even make it run unixodbc with freetds to reach a sqlserver . If someone has configuration tips ot make this work .... please let me know. On Feb 6, 4:30 pm, Michael Bayer <[email protected]> wrote: > On Feb 5, 2010, at 10:34 PM, Domingo Aguilera wrote: > > > I've been using pymssql for years. There's no special reason. If > > this means the end of pymssql in sqlalchemy I have no problem, I'll > > change to pyodbc. Thanks for your help. > > have you tried using the old version of pymssql then ? > > > > > > > On Feb 5, 9:21 pm, Michael Bayer <[email protected]> wrote: > >> On Feb 5, 2010, at 10:18 PM, Domingo Aguilera wrote: > > >>> After r6731 > > >>> File "/home/smartics/myenv/src/sqlalchemy/lib/sqlalchemy/engine/ > >>> __init__.py", line 223, in create_engine > >>> return strategy.create(*args, **kwargs) > >>> File "/home/smartics/myenv/src/sqlalchemy/lib/sqlalchemy/engine/ > >>> strategies.py", line 65, in create > >>> dialect = dialect_cls(**dialect_args) > >>> File "/home/smartics/myenv/src/sqlalchemy/lib/sqlalchemy/dialects/ > >>> mssql/pymssql.py", line 25, in __init__ > >>> super(MSDialect_pymssql, self).__init__(**params) > >>> File "/home/smartics/myenv/src/sqlalchemy/lib/sqlalchemy/dialects/ > >>> mssql/base.py", line 1121, in __init__ > >>> super(MSDialect, self).__init__(**opts) > >>> File "/home/smartics/myenv/src/sqlalchemy/lib/sqlalchemy/engine/ > >>> default.py", line 89, in __init__ > >>> self.paramstyle = self.dbapi.paramstyle > >>> AttributeError: 'module' object has no attribute 'paramstyle' > > >> thats a pymssql bug. DBAPI requires this param to be present. > > >> Whats the reason you can't just use pyodbc ? > > >>> On Feb 5, 7:36 pm, Michael Bayer <[email protected]> wrote: > >>>> r 6731. > > >>>> sorry i dont have pymssql installed to test these extremely trivial > >>>> glitches > > >>>> On Feb 5, 2010, at 7:17 PM, Domingo Aguilera wrote: > > >>>>> Michael, > > >>>>> after testing r6730 this is what I gethttp://gist.github.com/296416 > > >>>>> stack trace .... > > >>>>> File "prueba.py", line 3, in <module> > >>>>> engine = sa.create_engine("mssql+pymssql://foo/b...@host/pruebas" ) > >>>>> File "/home/smartics/myenv/src/sqlalchemy/lib/sqlalchemy/engine/ > >>>>> __init__.py", line 223, in create_engine > >>>>> return strategy.create(*args, **kwargs) > >>>>> File "/home/smartics/myenv/src/sqlalchemy/lib/sqlalchemy/engine/ > >>>>> strategies.py", line 65, in create > >>>>> dialect = dialect_cls(**dialect_args) > >>>>> File "/home/smartics/myenv/src/sqlalchemy/lib/sqlalchemy/dialects/ > >>>>> mssql/pymssql.py", line 25, in __init__ > >>>>> super(MSSQLDialect_pymssql, self).__init__(**params) > >>>>> NameError: global name 'MSSQLDialect_pymssql' is not defined > > >>>>> On Feb 4, 7:12 am, Michael Bayer <[email protected]> wrote: > >>>>>> On Feb 4, 2010, at 1:13 AM, Domingo Aguilera wrote: > > >>>>>>> I am trying to use 0.6b1 with pymssql ( latest version 1.0.2 ). For > >>>>>>> it I use create_engine with an uri like mssql+pymssql://.... > > >>>>>>> It seems 0.6b1 looks for a dbapi attribute that is not present in > >>>>>>> pymssql. Is there a workaround for this? > > >>>>>> theres two things going on there. one is that pymssql has been > >>>>>> rewritten recently. well, thats actually pretty much it - we havent > >>>>>> done any testing with pymssql. If you can provide details we can > >>>>>> commit a patch. In 0.6 we can probably just shoot for supporting the > >>>>>> "new" pymssql since its supposed to be much better than the old. > > >>>>>>> Tks. > > >>>>>>> -- > >>>>>>> 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 > >>>>>>> athttp://groups.google.com/group/sqlalchemy?hl=en. > > >>>>> -- > >>>>> 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 > >>>>> athttp://groups.google.com/group/sqlalchemy?hl=en. > > >>> -- > >>> 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 > >>> athttp://groups.google.com/group/sqlalchemy?hl=en. > > > -- > > 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 > > athttp://groups.google.com/group/sqlalchemy?hl=en. -- 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.
