Module selection in MSSQL is a bit ugly right now. Mike has proposed a clean-up of the way that DB-API modules are loaded and used, so this will get better soon, I hope.
I'll have a look at the patch. Rick On 3/9/07, polaar <[EMAIL PROTECTED]> wrote: > > > Yes, but I'm starting to think I'm doing something wrong ;-) I suppose > I should call create_engine with the module=pyodbc? > I was just using the creator argument (as I was doing already because > I needed to change the connectionstring to use integrated security > anyway), and just switched that from adodbapi to pyodbc. So maybe it's > still using the default adodbapi settngs... > Hmm, seems to make sense... oops... (well, it's not really clear from > the docs that this is used for anything else than determining which > module to use to create the connection, which seems unnecessary if you > create it yourself) > > I'll try it on monday... > > On 9 mrt, 22:08, "Rick Morrison" < [EMAIL PROTECTED]> wrote: > > This is still with pyodbc? The MSSQL module should already set > > sane_rowcount to False for that dialect, as per the pyodbc site, they > don't > > implement rowcount. > > > > Rick > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
