#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 --------------------------------------+------------------------------------
Comment (by Tim Graham <timograham@…>): In [changeset:"52b5890f5237ad8859108de1e0757be2b3f354c4" 52b5890]: {{{ #!CommitTicketReference repository="" revision="52b5890f5237ad8859108de1e0757be2b3f354c4" [1.8.x] Fixed #24880 -- Added more explicit docs on select_for_update() on SQLite. Backport of d29ed3f355b0c57e7036807f1d54f33796d8d820 from master }}} -- Ticket URL: <https://code.djangoproject.com/ticket/24880#comment:8> 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 django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/065.12bd666edac0781583f0e1ffd4b765b1%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.