badly-defined ForeignKey to self does not cause an exception

[Forest Bond <forest@…>]

I have a model something like this:

class MyModel(models.Model):
    my_model = ForeignKey('MyModel')

This mostly works, but I was confused when I found that instances didn't have a my_model_set attribute. I found that I should've defined my model like this:

class MyModel(models.Model):
    my_model = ForeignKey('self')

I can do that just fine, of course, but it was a bit non-obvious what the problem was. It'd be nice if defining that relationship improperly threw an exception.

[James Bennett]

Unfortunately it's kind of tricky to catch because that form is legal for getting around forward references to as-yet-undefined model classes, and for dealing with circular model dependencies. Probably still a good idea to see if we can do anything about it, though.

[Philippe Raoult]

i'd say we should force related_name to be set for foreignkeys to self.

[Ramiro Morales]

#3914 was about the same issue, marked as duplicate

[Jonas Obrist]

Can't reproduce this issue, works fine for me.