#30375: Use "NO KEY" when doing select_for_update for PostgreSQL
-------------------------------------+-------------------------------------
Reporter: Manuel Weitzman | Owner: Manuel
Type: | Weitzman
Cleanup/optimization | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: postgres, lock, | Triage Stage: Ready for
database, operation | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"a4e6030904df63b3f10aa0729b86dc6942b0458e" a4e6030]:
{{{
#!CommitTicketReference repository=""
revision="a4e6030904df63b3f10aa0729b86dc6942b0458e"
Fixed #30375 -- Added FOR NO KEY UPDATE support to
QuerySet.select_for_update() on PostgreSQL.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30375#comment:9>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.c5541f7c8bd0a9294fedf42deb9fe826%40djangoproject.com.
