#28010: select_for_update() is too eager in presence of joins
-------------------------------------+-------------------------------------
Reporter: Ran Benita | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* version: 1.10 => master
* stage: Unreviewed => Accepted
Comment:
Allowing the usage of `FOR UPDATE OF` is definitely something we want to
add.
Now for the proposed options the one that makes the most sense to me is
`1.`. `2.` would be backward incompatible given we actually lock all rows
by default and some backends don't allow locking only a specific table
which would make `select_for_update()` behave quite a bit differently on
different backends.
--
Ticket URL: <https://code.djangoproject.com/ticket/28010#comment:1>
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/066.fc96048128f3a90d87c35e2b6f309fc5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
