#31269: Generic Relations on multi table inheritance does not behave as other
fields
-------------------------------+--------------------------------------
Reporter: Eduardo Klein | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 3.0
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => needsinfo
Comment:
Hi Eduardo.
Thanks for the report.
I can see why you might want this. I can also see why it's unlikely to
work, and I guess not trivial to fix.
(Or let me put it another way, it's quite a niche use-case, and I'm not at
all sure it'd be worth the code to fix.)
The work-around is to resolve to the parent model, `Point` in your case,
and then access the generic relation.
This is easy enough to do.
I could see a note being added to the `GenericRelation` docs, but looking
it seems it would be quite clumsy wherever we put it.
Since someone searching will now find this, I'm a bit 😬 about adding such
a note.
I'll say `needsinfo`: happy to look at a code or docs patch for this
ticket, but pending that...
I hope that makes sense.
--
Ticket URL: <https://code.djangoproject.com/ticket/31269#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.f772ba4d744cc7eb5d238c9c577fa3cf%40djangoproject.com.
