On Nov 13, 5:04 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> On 11/13/07, John Penix <[EMAIL PROTECTED]> wrote:
>
> > We've stuck a bit of ORM-using code from our "pure" django server into
> > another server that was only using django templates. We have been seeing
> > connections left open occasionally. I browsed the mailing list archives and
> > it sounds like django should be closing the connection. I'm wondering if we
> > aren't always tripping the code that closes the database connection since
> > this server is not using django to generate responses.
>
> Because it's oriented around web serving, Django closes the connection
> on the "request_finished" signal; if that signal is never fired,
> Django will not close the connection. Additionally, if something else
> requires database access after the signal is fired, a new connection
> will be opened and will not be closed.
Cool. So I'm guessing that if we send that signal as described here:
http://code.djangoproject.com/wiki/Signals
The connection should get closed.
I'll report back if it doesn't work.
Thanks!
John
>
> --
> "Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
