#35560: Model.full_clean() errors with GeneratedField and UniqueConstraint or
CheckConstraint
-------------------------------------+-------------------------------------
Reporter: Mark Gensler | Owner: Mark
| Gensler
Type: Bug | Status: closed
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: generatedfield | Triage Stage: Ready for
uniqueconstraint checkconstraint | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce <42296566+sarahboyce@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"1005c2abd1ef0c156f449641e38c33e473989d37" 1005c2a]:
{{{#!CommitTicketReference repository=""
revision="1005c2abd1ef0c156f449641e38c33e473989d37"
Fixed #35560 -- Made Model.full_clean() ignore GeneratedFields for
constraints.
Accessing generated field values on unsaved models caused a crash when
validating CheckConstraints and UniqueConstraints with expressions.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35560#comment:6>
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/010701907d22533c-ac54b50c-a451-4494-ad2d-23005d59c8f7-000000%40eu-central-1.amazonses.com.
