#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
-------------------------------+--------------------------------------
Changes (by shaib):
* needs_better_patch: 0 => 1
* needs_docs: 0 => 1
Comment:
This makes perfect sense for the common use-case, "use sqlite as
scaffolding for development, use a more capable database backend for
production". On the other hand, this breaks backwards-compatibility on
Sqlite.
The idea of changing Sqlite's behavior to match other backends was
discussed when we changed select-for-update to error out (when supported)
if executed out of transaction; see https://groups.google.com/forum/#!msg
/django-developers/8woZjCPcFmA/GqQLDxFZbc8J for the details. Back then,
nobody seems to have thought it was worth breaking backwards
compatibility; if you want to convince people otherwise, I think it would
be best to do so on the DevelopersMailingList.
Even if you can convince people that a break is warranted, we will
probably want the change to go through a deprecation cycle; thus, the
patch as is would need to be fixed. Otherwise, a patch to improve the
documentation is welcome.
(I am not marking this "wontfix" yet, mostly because of the possibility of
resolving via documentation).
--
Ticket URL: <https://code.djangoproject.com/ticket/24880#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 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.f0a65c48351fbeb0886cceec6626ff63%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
