#31515: Django tries to reuse MySQL connections that have gone away with ASGI.
---------------------------------+------------------------------------
Reporter: Braunson | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 3.0
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by Braunson):
Replying to [comment:24 Andrew Godwin]:
> Oh, OK. Note that you can use those under WSGI Django as well and
they'll perform very similarly - Django 3.0 does not have a true-
asynchronous request path, so it's using one thread per request anyway.
Thanks, we'll just not use asgi for now then :)
--
Ticket URL: <https://code.djangoproject.com/ticket/31515#comment:25>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.183c968a198358081536e48b5ddf7068%40djangoproject.com.
