#26179: Remove null assignment check for non-nullable foreign key fields
-------------------------------------+-------------------------------------
Reporter: timgraham | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database | Version: master
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
As raised in #25349 and [https://groups.google.com/d/topic/django-
developers/4UL_FkDXX-w/discussion discussed on django-developers], the
following behavior should be removed:
{{{
>>> obj.fk = None
ValueError('Cannot assign None: "Obj.fk" does not allow null values.)
}}}
(i.e. no more exception if you assign `None` to a non-nullable foreign
key). It applies to `ForwardManyToOneDescriptor` and
`ReverseOneToOneDescriptor`. The change should be documented in the
"backwards-incompatible changes" section of the release notes.
--
Ticket URL: <https://code.djangoproject.com/ticket/26179>
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/052.a026d1eeea3678e02200bd5e90f7346a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
