On 1/13/07, Rob J Goedman <[EMAIL PROTECTED]> wrote:
Normally the delays are natural and are controlled via Twisted (TCP and callLater). Above program is stable if I comment out the cpl=list (...) statement, otherwise it grows forever.
Each time that code is called, it's fetching every row from the table and instantiating a full in-memory model object for each row retrieved; is there a reason why you need to have them all loaded and instantiated at that moment, rather than waiting and iterating over the QuerySet when you actually need to access the data? -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
