only if youre leaving dangling ResultProxys opened with pending results, which should be a fairly rare occurence in a normal application. if you simply call fetchall() on results instead of fetchone(), that alone would eliminate any hanging cursors.
On Apr 24, 2008, at 11:54 PM, BruceC wrote: > > Thank you to everybody for your comments on this problem... > > Michael, re: your suggestion about result.close(), is this something > that I could add to mssql.py, or do you think it's something that I > would need to add throughout my application everytime I access the db? > (It's a big application...) > > Cheers! > > On Apr 25, 4:15 am, Michael Bayer <[EMAIL PROTECTED]> wrote: >> So if you are using >> straight connection or engine result sets, and are not explicitly >> exhausting all rows, call result.close() to explicitly release the >> cursor. That will solve the problem. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
