From 1b4e1b021de69e5b2ceabb03d7e9f4185c5084a0 Mon Sep 17 00:00:00 2001 From: Curtis Date: Mon, 29 Jul 2013 20:59:53 +1000 Subject: [PATCH] Document the polymorphic_list property --- docs/admin.rst | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/admin.rst b/docs/admin.rst index 7d46842..db84b56 100644 --- a/docs/admin.rst +++ b/docs/admin.rst @@ -28,6 +28,13 @@ The exact implementation can depend on the way your module is structured. For simple inheritance situations, ``child_models`` is the best solution. For large applications, ``get_child_models()`` can be used to query a plugin registration system. +By default, the non_polymorphic() method will be called on the queryset, so +only the Parent model will be provided to the list template. This is to avoid +the performance hit of retrieving child models. + +This can be controlled by setting the ``polymorphic_list`` property on the +parent admin. Setting it to True will provide child models to the list template. + The child models ----------------