On Nov 10, 2007, at 12:20 PM, david wrote:
> > Hi Mike - > > That did the trick! > > But, the strange thing is, if you note the illustration above, for > both situations I was selecting on a key, and there was only a single > row for each. Why would one require the result.close(), and the other > not? > > Yes, I wasn't sure the error is that all important - BUT, is it > indicative some of problem in the lower reaches somewhere? > > Also, when doing these queries is it recommended to always do a > "result.close()"? Perhaps there would be a way for this to be > "automatically" handled.. > david - it is automatically handled as much as it possibly can be. however when you say fetchone(), theres still results pending - its exactly the one case where we cannot automatically (and explicitly) close the cursor for you. So, if you leave it hanging, then the garbage collection of the cursor will eventually take over. as garbage collection can be a little "messy" (i.e., maybe its collecting the connection which points to the cursor first), well, theres the warning youre getting....things arent being garbage collected in the expected order. I didnt notice what version of MySQLdb youre running but maybe upgrading that to the latest version might help. - mike --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
