id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
31269	Generic Relations on multi table inheritance does not behave as other fields	Eduardo Klein	nobody	"Suppose we have the following models:

{{{
#!python
class Tag(models.Model):
    content_type = models.ForeignKey('contenttypes.ContentType', on_delete=models.CASCADE)
    object_id = models.PositiveIntegerField()
    obj = GenericForeignKey()


class Point(models.Model):
    name = models.CharField(max_length=256)
    tags = GenericRelation(""tag"")


class SpecificPoint(Point):
    pass
}}}

We create a specific_point instance as follow:
{{{
#!python
specific_point = SpecificPoint.objects.create(name=""test"")
}}}

Now we add a tag to the corresponding point instance :
{{{
#!python
point = Point.objects.get(pk=specific_point.id)
tag = point.tags.create()
}}}

When we do `specific_point.tags.all()` it returns en empty queryset, instead of a queryset containing the tag instance that we have created and that we would obtain doing `point.tags.all()`

I understand that the issue here is that the content_type associated with the `tag` instance is the ""point"" one and not the ""specificpoint"", but it's problematic since if we do `specific_point.pk` or `specific_point.name` or any other field that is not a generic relation, we would obtain exactly the same as `point.pk` or `point.name`, but the ""logic"" is broken for generic relations.

I'm not sure that this is a bug, but at least I think it deserves some consideration in the docs. If this is considered a bug, one possible solution would be to concatenate the tags from both models' content_types.
"	Bug	closed	contrib.contenttypes	3.0	Normal	needsinfo			Unreviewed	0	0	0	0	0	0