#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 |
---------------------------------------------------+------------------------
Comment (by norvegh):
Hi,
You are correct in that we are not using the HTTP layer. We have a back-
end application and it was very convenient to reuse Django's model API
that we use for the front-end Webapp. However there is clearly a bug in
Django, as the connections are not closed even when the threads using
those connections are terminated. Those DB connections are just hanging
there for a long time (or forever, don't really know that).
We know that this is not exactly the way Django is supposed to be used,
but Django has grown too powerful and useful to limit it only to the
front-end.
norvegh
--
Ticket URL: <http://code.djangoproject.com/ticket/9878#comment:2>
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
-~----------~----~----~----~------~----~------~--~---
