#24880: Clarify docs about select_for_update() error if run outside of a
transaction
--------------------------------------+------------------------------------
Reporter: suligap | Owner: nobody
Type: Cleanup/optimization | Status: closed
Component: Documentation | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"d29ed3f355b0c57e7036807f1d54f33796d8d820" d29ed3f]:
{{{
#!CommitTicketReference repository=""
revision="d29ed3f355b0c57e7036807f1d54f33796d8d820"
Fixed #24880 -- Added more explicit docs on select_for_update() on SQLite.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24880#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.11ab9e1b799a43773bcb375e821468cc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.