#33497: Database persistent connections do not work with ASGI in 4.0
-------------------------------------+-------------------------------------
Reporter: Stenkar | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: ASGI; Database | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* type: Bug => New feature
* stage: Unreviewed => Accepted
Comment:
OK, thanks Stenkar.
I'm going to accept this as a New Feature. It's a change in behaviour from
3.2, but it's precisely in allowing multiple executors for
`sync_to_async()` that it comes up. (In 3.2 it's essentially single-
threaded, with only a single connection actually being used.) We need to
improve the story here, but it's not a bug in #32889 that we don't have
async compatible persistent DB connections yet. (I hope that makes sense.)
A note to the docs about this limitation may be worthwhile.
--
Ticket URL: <https://code.djangoproject.com/ticket/33497#comment:7>
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/064.5dbd61ff005ebceab37763126d0e26b7%40djangoproject.com.
