#9878: Database backend leaves idling connections when used in multiple threads
---------------------------------------------------+------------------------
Reporter: Fredde | Owner: nobody
Status: closed | Milestone:
Component: Database layer (models, ORM) | Version: 1.0
Resolution: invalid | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by ubernostrum):
* status: reopened => closed
* resolution: => invalid
Comment:
What Malcolm means is that the database connection ''Django itself created
automatically'' for the ORM in the current request/thread will be closed.
Additional connections that you yourself cause to be opened are your
responsibility to clean up (just as files you open are your responsibility
to close, mail-server connections you open are your responsibility to
close, etc., etc.).
--
Ticket URL: <http://code.djangoproject.com/ticket/9878#comment:4>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---