#13776: is_valid() with null field value on ModelForms from models with non-
nullable ForeignKeys causes ValueError
-------------------------------------+-------------------------------------
Reporter: peterbe | Owner:
| anubhav9042
Type: Bug | Status: closed
Component: Forms | Version: master
Severity: Normal | Resolution: fixed
Keywords: ModelForm | Triage Stage: Accepted
ForeignKey |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Claude Paroz <claude@…>):
In [changeset:"65a1055a36318ff4e21ffeb7c3dd62fa81892269" 65a1055]:
{{{
#!CommitTicketReference repository=""
revision="65a1055a36318ff4e21ffeb7c3dd62fa81892269"
Fixed #25431 -- Readded inline foreign keys to modelformset instances
Too much field exclusions in form's construct_instance() in _post_clean()
could lead to some unexpected missing ForeignKey values.
Fixes a regression from 45e049937. Refs #13776.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/13776#comment:22>
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/065.6888de24cc3f7d1b25c0be153a8567f7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
