On Apr 29, 10:08 am, Tom Wood <thomas.a.w...@gmail.com> 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. >
This change does not affect any of the tests on Windows. So that's good. I'd like to confirm a couple of other things before we commit. Thanks a lot. Michael --~--~---------~--~----~------------~-------~--~----~ 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 sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
