You're probably think of the change in 1.8.4 that moved the unsaved model instance assignment data loss check (added in Django 1.8) to Model.save() to allow easier usage of in-memory models (#25160 <https://code.djangoproject.com/ticket/25160>).
The checks in question have been in Django since 1.0: https://github.com/django/django/commit/1452d46240609ff39dacf9ea2f759ed600c2f09f On Wednesday, February 3, 2016 at 11:37:31 AM UTC-5, Florian Apolloner wrote: > > On Wednesday, February 3, 2016 at 12:26:26 AM UTC+1, Tim Graham wrote: >> >> There's a proposal to remove this behavior: >> >> >> >>> obj.fk = None >> ValueError('Cannot assign None: "Obj.fk" does not allow null values.) >> > > Yes please, if you do IntegerField(null=False) you can still do > instance.xxx = None -- only ForeignKeys are weird and check during > assignment… > That said I thought we already removed that in 1.9 or 1.10? > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/d668ad00-9eae-41b6-9b3e-6846cc67141d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
