#34827: select_for_update example raises TransactionManagementError
-------------------------------+--------------------------------------
Reporter: SydneyUni-Jim | Owner: nobody
Type: Bug | Status: closed
Component: Documentation | Version: 4.2
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Simon Charette):
* status: new => closed
* resolution: => invalid
Comment:
Querysets are lazily evaluated, and thus only the evaluating part needs to
be run within a transaction
> When the queryset is evaluated (**for entry in entries in this case**),
all matched entries will be locked until the end of the transaction block
--
Ticket URL: <https://code.djangoproject.com/ticket/34827#comment:2>
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/0107018a8239eef2-317435de-96ec-453e-bf7e-44368cafac22-000000%40eu-central-1.amazonses.com.
