#22967: Model._do_update not always consistent with the precise meaning of
returned
value
-------------------------------------+-------------------------------------
Reporter: knaperek | Owner: knaperek
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) | Resolution: fixed
Severity: Normal | Triage Stage: Ready for
Keywords: select_on_save | checkin
concurrency race-condition | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by Anssi Kääriäinen <akaariai@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"c56c42b5c01ed774cfa8e044cd372a984608536c"]:
{{{
#!CommitTicketReference repository=""
revision="c56c42b5c01ed774cfa8e044cd372a984608536c"
Fixed #22967 -- Made Model._do_update consistent
Made _do_update behave more strictly according to its docs,
including a corner case when specific concurent updates are
executed and select_on_save is set.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/22967#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 [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.27ed25eae72a13417c418d817b68aa93%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
