#24880: Error on all db backends if `select_for_update` is run outside of a
transaction
-------------------------------+--------------------------------------
Reporter: suligap | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by timgraham):
I'm having trouble seeing backwards compatibility as a major concern. This
would affect SQLite users who are using `select_for_update()` (where it
has no effect) outside of a transaction. Am I missing a case you are
thinking about?
--
Ticket URL: <https://code.djangoproject.com/ticket/24880#comment:3>
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.772de6ec07f1c656fc9ed50dcc6e8f8b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
