#35223: Fields with db_default raise ValidationErrors when full_clean() called -------------------------------------+------------------------------------- Reporter: Brian Ibbotson | Owner: bcail Type: | Status: closed Cleanup/optimization | Component: Database layer | Version: 5.0 (models, ORM) | Severity: Release blocker | Resolution: fixed Keywords: | Triage Stage: Ready for | checkin Has patch: 1 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+------------------------------------- Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* resolution: => fixed * status: assigned => closed Comment: In [changeset:"1570ef02f34037d32218d463342592debccf915c" 1570ef0]: {{{#!CommitTicketReference repository="" revision="1570ef02f34037d32218d463342592debccf915c" Fixed #35223 -- Made Model.full_clean() ignore fields with db_default when validating empty values. Thanks Brian Ibbotson for the report. Regression in 7414704e88d73dafbcfbb85f9bc54cb6111439d3. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/35223#comment:12> 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/0107018e1c97f097-cf3ddf8a-87d2-4f75-ba34-631c348f01dd-000000%40eu-central-1.amazonses.com.