#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:"2d3bb414cfb2778cc64f22e7203102d7389f81e6" 2d3bb414]:
{{{#!CommitTicketReference repository=""
revision="2d3bb414cfb2778cc64f22e7203102d7389f81e6"
Refs #35560 -- Corrected required feature flags in
GeneratedModelUniqueConstraint.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35560#comment:10>
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/01070190b57a5e7a-d7c3479c-7aa1-4767-a748-94e07cbbf4a4-000000%40eu-central-1.amazonses.com.
