#33646: Adding async interface to QuerySet.
-------------------------------------+-------------------------------------
Reporter: Mariusz Felisiak | Owner: Andrew
| Godwin
Type: New feature | Status: closed
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: async | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by GitHub <noreply@…>):
In [changeset:"1109e669905d2011561e843f0ab7c2c02fb63c4d" 1109e669]:
{{{
#!CommitTicketReference repository=""
revision="1109e669905d2011561e843f0ab7c2c02fb63c4d"
Refs #33646 -- Reduced sync_to_async hops on async QuerySet iteration.
Until we add support for truly asynchronous database backends it's
actually detrimental to have complete set retrieval require multiple
hops between sync and async emulated contexts via asgiref.
By defaulting to sending the whole sync _fetch_all() to the current
context thread pool we reduce unncessary work when dealing with large
result sets since the queryset cannot be iterated anyway before all
results are retrieved and cached.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33646#comment:9>
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/010701808dc500fe-7290c690-f2f1-4aa7-8e71-bc16f8dc7fc9-000000%40eu-central-1.amazonses.com.
