#26352: models.E003 check incorrectly prevents duplicate ManyToMany through-self
that differ by through_fields
-------------------------------------+-------------------------------------
Reporter: simonw | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by charettes):
The only use-case I can think of right now is working around limitations
of reverse relationships (#897 seems to mention this exact workaround).
If we ever unify the reverse relationships API by exposing them as normal
fields I think an explicit way of defining them would be necessary (to
define options such as `verbose_name`).
In the meantime I'm not sure about what should be done here as I vaguely
remember relying on a similar field definition in the past and it
definitely worked in Django 1.2. On the other hand I wouldn't be surprised
if it breaks Django in subtle ways as it seems untested (migrations come
to mind here).
--
Ticket URL: <https://code.djangoproject.com/ticket/26352#comment:3>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.502e556c2ae3b4da43b562daf75f3bb9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
