#22540: .save() called in multiple "creation" queryset functions
-------------------------------------+-------------------------------------
Reporter: craig.labenz@… | Owner: nobody
Type: | Status: closed
Cleanup/optimization | Version: master
Component: Database layer | Resolution: fixed
(models, ORM) | Triage Stage: Ready for
Severity: Normal | checkin
Keywords: creation | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by Claude Paroz <claude@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"0dce44e16be2d4850120cd333380ab9171c5964a"]:
{{{
#!CommitTicketReference repository=""
revision="0dce44e16be2d4850120cd333380ab9171c5964a"
Fixed #22540 -- Made _create_object_from_params() call create()
So as the save step is centralized in create(), especially useful
when customizing behavior in subclasses.
Thanks craig.lab...@gmail.com for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/22540#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 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/080.11070da27a8800195a6bb8ee00663019%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
