#30376: Saving ModelForm with missing, non-optional fields does not trigger a
validation error
-------------------------------+--------------------------------------
Reporter: Will Gordon | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 2.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Will Gordon):
Ok, so maybe this is more of an issue with the `save()` as opposed to
validation. As I read that quote
if the model does not allow the missing fields to be empty, and does not
provide a default value for the missing fields, any attempt to save() a
ModelForm with missing fields will fail
If I have a field with `blank=False` in my Model, then doing a `save()` on
the ModelForm should fail...regardless of if I have specified that field
in the ModelForm or not. Am I just taking a narrow view on that comment,
or is it saying something other than what I'm reading?
--
Ticket URL: <https://code.djangoproject.com/ticket/30376#comment:2>
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/067.cbf9da18182cf528400804beef901ab0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
