#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
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"bc151b692a2e0f35a15b72a5bafcb42dea263461" bc151b69]:
{{{
#!CommitTicketReference repository=""
revision="bc151b692a2e0f35a15b72a5bafcb42dea263461"
[1.9.x] Fixed #26918 -- Clarified source of pre/post_save update_fields
argument.
Backport of a05d86a69a7f11f00032b8d7846932b139c670e0 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26918#comment:5>
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.9c9f3dd555b257e0a9309de578573f75%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
