#35223: Fields with db_default raise ValidationErrors when full_clean() called
-------------------------------------+-------------------------------------
Reporter: Brian Ibbotson | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 5.0
(models, ORM) |
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 Mariusz Felisiak):
> I would suggest having fields with db_default be excluded by default
from full_clean()
`db_default` is just a default value, we cannot always exclude it from
`full_clean()`. What about not valid values provided explicitly in
`create()`? What about `None` when field is non-nullable? etc.
--
Ticket URL: <https://code.djangoproject.com/ticket/35223#comment:3>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018db3cad4b7-8048c91f-722d-4ae9-8dfd-01bb422addd3-000000%40eu-central-1.amazonses.com.
