On Nov 8, 2007 11:15 AM, David Geller <[EMAIL PROTECTED]> wrote: > I finally did get the errors while logging was enabled, but not sure > what sort of light has been shed on this:
You'll probably have to ask on the sqlalchemy list. I don't know about the innards of SA or why .__del__ would be called at that particular time. It could mean the connection is being forcibly destroyed before all the data has been read from it, or something like that. You also need to turn on connection pool logging, however. The only queries that matter are the two or three previous ones on the same connection. If the last result was large or occurred immediately before the .__del__, that would lead more credence to the theory that the .__del__ is being called too quickly. -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
