#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
-------------------------------------+-------------------------------------
Comment (by Sarah Boyce <42296566+sarahboyce@…>):
In [changeset:"2da007737cda936ef2ee87271bf9e69eb93cd3fe" 2da00773]:
{{{#!CommitTicketReference repository=""
revision="2da007737cda936ef2ee87271bf9e69eb93cd3fe"
[5.1.x] 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.
Backport of 1005c2abd1ef0c156f449641e38c33e473989d37 from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35560#comment:7>
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/010701907d24b798-03795cf3-dbbe-4778-b246-7cf066ac38c3-000000%40eu-central-1.amazonses.com.
