#25349: ModelForm regression when setting None into a ForeignKey
--------------------------+------------------------------------
Reporter: jpaulett | Owner:
Type: Bug | Status: new
Component: Forms | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------+------------------------------------
Changes (by timgraham):
* needs_better_patch: 0 => 1
Comment:
The consensus is to remove the check that prevents assigning `None` to a
foreign key field if `null=False` as proposed here. For clarity and
completeness (there's another similar check which the current PR doesn't
remove), let's do that removal as a separate ticket (#26179) and then
rebase the fix for this issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/25349#comment:8>
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/066.48e49305cd2e05ce9398ec99cb9e0a2e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
