#22356: unique_together fails when referencing columns from base and child class
-------------------------------------+-------------------------------------
Reporter: claus | Owner: nobody
Type: Bug | Status: new
Component: Core (System | Version:
checks) | 1.7-beta-1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by shai):
* cc: shai (added)
* needs_better_patch: => 0
* component: Migrations => Core (System checks)
* needs_tests: => 1
* needs_docs: => 0
* stage: Unreviewed => Accepted
Comment:
This cannot work when you are using multi-table inheritance -- the two
columns are in separate tables, and you cannot place a cross-table
constraint.
This probably belongs in "system checks".
It can work if the parent is abstract.
(accepting based on report, with no attempt to reproduce)
(I am hesitant to mark it, not being familiar enough with the checks code,
but this is probably an easy-pickings ticket)
--
Ticket URL: <https://code.djangoproject.com/ticket/22356#comment:1>
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.db101d7baaa8e1fe6f7807ea349e0b06%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
