On Apr 30, 11:04 pm, mtrier <[email protected]> wrote: > > Some additional info, and a possible fix: > > > =================================================================== > > --- lib/sqlalchemy/databases/mssql.py (revision 5930) > > +++ lib/sqlalchemy/databases/mssql.py (working copy) > > @@ -991,7 +991,7 @@ > > # We may have to skip over a number of result sets with > > no data (due to triggers, etc.) > > while True: > > try: > > - row = self.cursor.fetchone() > > + row = self.cursor.fetchall()[0] > > break > > except pyodbc.Error, e: > > self.cursor.nextset() > > > I.e., calling fetchall() instead of fetchone() seems to clean up the > > cursor state. >
Also, FWIW, the original test passes just fine on Windows and pyodbc. So it's definitely a FreeTDS issue. > > Michael --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
