#22356: unique_together fails when referencing columns from base and child class
-------------------------------------+-------------------------------------
Reporter: claus | Owner: frog32
Type: Bug | Status: closed
Component: Core (System | Version:
checks) | 1.7-beta-1
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
Has patch: 1 | checkin
Needs tests: 1 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette <charette.s@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"0bcc92c6917738caa2f08ec16d26fad62974fb47"]:
{{{
#!CommitTicketReference repository=""
revision="0bcc92c6917738caa2f08ec16d26fad62974fb47"
Fixed #22356 -- Added a check to make sure unique_together fields are
local.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/22356#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.86fe8210fc8119d326b230a9301cefeb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
