#27403: Document that prefetch_related doesn't guarantee transactional
consistency
-------------------------------------+-------------------------------------
Reporter: Aymeric Augustin | Owner: Tim Bell
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: dev
Severity: Normal | Resolution: fixed
Keywords: | 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 Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"8b18e0bb3ba8bb1f51e15487a6d5402853e637ae" 8b18e0bb]:
{{{
#!CommitTicketReference repository=""
revision="8b18e0bb3ba8bb1f51e15487a6d5402853e637ae"
[5.0.x] Fixed #27403 -- Doc'd that QuerySet.prefetch_related() doesn't
guarantee transactional consistency.
Added a note about the potential race condition in prefetch_related()
that could produce an inconsistent result, one that does not correspond
to any point in the database history.
Backport of ee104251c403fbac83b8475163ff2ac01c567d25 from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27403#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/0107018b65ee2869-71d74808-3909-488c-ac7d-829c7ce63df4-000000%40eu-central-1.amazonses.com.
