#25160: Move unsaved model instance assignment check to model.save()
-------------------------------------+-------------------------------------
Reporter: timgraham | Owner: timgraham
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"e4b813c0e723e774c5c7386a29f10bc807a47e47" e4b813c]:
{{{
#!CommitTicketReference repository=""
revision="e4b813c0e723e774c5c7386a29f10bc807a47e47"
[1.8.x] Fixed #25160 -- Moved unsaved model instance data loss check to
Model.save()
This mostly reverts 5643a3b51be338196d0b292d5626ad43648448d3 and
81e1a35c364e5353d2bf99368ad30a4184fbb653.
Thanks Carl Meyer for review.
Backport of 5980b05c1fad69eef907e0076aa2dc837edab529 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25160#comment:10>
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/067.8a8f3f535a0799a1050b02d50cb15f15%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
