#9878: Database backend leaves idling connections when used in multiple threads
---------------------------------------------------+------------------------
Reporter: Fredde | Owner: nobody
Status: reopened | Milestone:
Component: Database layer (models, ORM) | Version: 1.0
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by anonymous):
* status: closed => reopened
* resolution: invalid =>
Comment:
Replying to [comment:1 mtredinnick]:
> However, Django closes its connection to the database at the end of each
request/response cycle
This is not true even when using the HTTP layer (only tested with the
development server). After all the threads have joined, there is still
idling connections left behind. Try the code I posted erlier and you will
see.
--
Ticket URL: <http://code.djangoproject.com/ticket/9878#comment:3>
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
-~----------~----~----~----~------~----~------~--~---
