#26918: Documentation Clarification on pre_save signal updated_fields
-------------------------------------+-------------------------------------
Reporter: stantond | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by GitHub <noreply@…>):
* resolution: needsinfo => fixed
Comment:
In [changeset:"a05d86a69a7f11f00032b8d7846932b139c670e0" a05d86a]:
{{{
#!CommitTicketReference repository=""
revision="a05d86a69a7f11f00032b8d7846932b139c670e0"
Fixed #26918 -- Clarified source of pre/post_save update_fields argument.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26918#comment:4>
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.388df7565beaba585664a084c2f48069%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
