#35223: Fields with db_default raise ValidationErrors when full_clean() called
-------------------------------------+-------------------------------------
Reporter: Brian Ibbotson | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* stage: Unreviewed => Accepted
* type: Bug => Cleanup/optimization
Comment:
Replying to [comment:4 Simon Charette]:
> I believe that we should find a way to have `db_default` behave the same
way as generated fields when no value has been assigned to the instance
when `full_clean` is called (#35127). Requiring users to explicitly pass
it to `exclude` is simply bad ergonomics IMO.
Agreed, I think we should treat this as a cleanup not bug.
--
Ticket URL: <https://code.djangoproject.com/ticket/35223#comment:5>
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/0107018db8515e55-d755d226-4ccc-4873-b913-a4893179c607-000000%40eu-central-1.amazonses.com.
