#25160: Move unsaved model instance assignment check to model.save()
-------------------------------------+-------------------------------------
Reporter: timgraham | Owner: timgraham
Type: | Status: assigned
Cleanup/optimization |
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by carljm):
Replying to [comment:4 timgraham]:
> I'll keep working on this. Carl, are you in favor of a backport to 1.8
as Anssi was in the linked ticket?
I think so. The original change was a backwards-incompatible regression,
which should have had a deprecation path at the very least, if we even
wanted to prohibit all in-memory use (which I don't think we should). So I
think that regression justifies a backported fix.
--
Ticket URL: <https://code.djangoproject.com/ticket/25160#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 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/067.67af833b0733ebd95a3c6d69879c5af7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
