#27193: ORDER BY clause not included in subqueries using select_for_update()
-------------------------------+--------------------------------------
Reporter: sqwishy | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 1.9
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by shaib):
* status: new => closed
* needs_better_patch: => 0
* resolution: => needsinfo
* needs_tests: => 0
* needs_docs: => 0
Comment:
Hi,
You said:
> My use case is to lock rows in a particular order with the goal of
preventing deadlocks.
Can you please point to some documentation, or example code with
execution, that shows this idea may work? As far as I know, the locking is
atomic -- it is done for all rows matching the criteria together, and thus
the order-by clause on the inner select is indeed meaningless and can be
dropped.
If and when you show this, please re-open the ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/27193#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 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.1cc0c765e6e3a1cc716e323d5bcc74cf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
