Self-referencing keys in the list_display kills development server with no error thrown

[adamfast@…]

If you use this model:

class Page(models.Model):
    title = models.CharField(maxlength=192)
    default = models.BooleanField()
    template = models.CharField(maxlength=256)
    parent = models.ForeignKey('Page')
    sequence = models.IntegerField()
    visible_on_menu = models.BooleanField()
    defined_header = models.CharField(maxlength=256)
    date_of_creation = models.DateTimeField()
    class Admin:
        list_display = ['title','parent','visible_on_menu']

And try to go to the model in the admin interface, the development server just dies. There is no error, it just goes back to a command prompt waiting.

This model is to be used for a newforms-like setup that can have parent/child pages for building heirarchical navigation menus - and it will be handy to see the parent in the display.

[Adrian Holovaty]

(Fixed formatting in description.)

[Simon G. <dev@…>]

Yep. Confirmed on r4921.

[Malcolm Tredinnick]

Whilst this is something we might be able to fix, the workaround -- and the way the documentation recommends to do this -- is to use "self" instead of "Page" in the ForeignKey.

[Simon G. <dev@…>]

This might be something that django.core.management.validate could check for and display a warning?

[anonymous]

Museum of modern art moma Child museum in new jersey

[Ramiro Morales]

Undo anonymous breakage

[Ramiro Morales]

Marking as duplicate of #4212 because a) this ticket has muted on being about the same issue and b) it has a couple of useful comments about things to consider before implementing validation of FK-to-self declarations.

[Ramiro Morales]

Oops, second try: Marking as duplicate of #4212 because a) it has a couple of useful comments about things to consider before implementing validation of FK-to-self declarations and b) this ticket has mutated to being about the same issue.