#31185: fields.E310-E311 should take into account UniqueConstraints without
conditions.
-------------------------------------+-------------------------------------
Reporter: Pavel Garkin | Owner: Ahmad
| Abdallah
Type: Bug | Status: closed
Component: Core (System | Version: master
checks) |
Severity: Normal | Resolution: fixed
Keywords: UniqueConstraint | Triage Stage: Ready for
unique_together E310 E311 | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"5bf28ac2ed17773214bd6c7796ef356067c9fa91" 5bf28ac2]:
{{{
#!CommitTicketReference repository=""
revision="5bf28ac2ed17773214bd6c7796ef356067c9fa91"
Fixed #31185 -- Fixed detecting of unique fields in
ForeignKey/ForeignObject checks when using Meta.constraints.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31185#comment:15>
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/064.1fe0bee4ebe5ee5bc56f5e6f9f6529a0%40djangoproject.com.
