#19519: Django fails to close db connections at end of request-response cycle
-------------------------------------+-------------------------------------
Reporter: amosonn@… | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Release blocker | Triage Stage: Accepted
Keywords: connection, | Needs documentation: 0
managment, closing, mysql, | Patch needs improvement: 0
innodb, signal, generator | UI/UX: 0
Has patch: 0 |
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by aaugustin):
Replying to [comment:6 akaariai]:
> Do we have a problem with transactions here? The transaction used for
the request could be closed before the request is actually generated.
This is less likely to bite people in real life. There are obvious uses
cases for reading from the database while generating a streaming response
(eg. huge CSV exports); I don't see writing to the database as being as
common.
It's tracked by #5241, and I don't think it is a release blocker.
--
Ticket URL: <https://code.djangoproject.com/ticket/19519#comment:10>
Django <https://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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
