#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:"c76089be6f955d0493b3ab81c2beb64db4e203c4" c76089b]:
{{{#!CommitTicketReference repository=""
revision="c76089be6f955d0493b3ab81c2beb64db4e203c4"
[5.0.x] Refs #35560 -- Corrected CheckConstraint argument name in
model_fields tests.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35560#comment:9>
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/0107019091ec1dfd-0ad5f8c1-497b-46a3-94de-e7366b13e68c-000000%40eu-central-1.amazonses.com.
