On Feb 4, 2010, at 5:49 PM, Yannick Gingras wrote: > On February 4, 2010, Michael Bayer wrote: >> In 0.6 we can probably just shoot for supporting the "new" pymssql >> since its supposed to be much better than the old. > > I've seen pymssql 1.0.2 segfault the interpreter when under medium > load. And yes, I had a core to prove that pymssql was as fault. I > would probably consider pyodbc is I was stuck with MSSQL.
did you contact the pymssql maintainer about that ? Also, even if pymssql was "at fault" I've observed that sometimes native libs segfault due to specific usages, which the dialect can be made to ensure never occur. > > -- > Yannick Gingras > http://ygingras.net > http://confoo.ca -- track coordinator > http://montrealpython.org -- lead organizer -- 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.
