On 1/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I'm just getting data from the database in the following way. > > info.antiigm_set.values()
OK, that narrows it down. ;-) Also, are you running on trunk or some other version of Django? > The application is running on a linux server could that be the problem > ? No, most django deployments are on linux, I bet. You previously wrote: " My guess is that tha application keeps the database connection open for a amount of time and opens a new connection every time the database is aproached. " That's not true-- the intent is for Django to open the connection when it's needed and close it after response middleware has run. Is it possible that you have code running -after- response middleware which requires the DB (and thus re-opens the connection)? For example, does your response return an iterable that requires the DB when .next() is called? (If you're running an earlier version, my advice would be different...) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
