Briq
/
django-polymorphic
6
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merge pull request #49 from funkybob/master 

Document the polymorphic_list property
fix_request_path_info
Diederik van der Boor 2013-07-29 04:04:49 -07:00
parent 9d00d214e1 1b4e1b021d
commit 496e2c2cf2
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/admin.rst
View File

@ -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 simple inheritance situations, ``child_models`` is the best solution.
For large applications, ``get_child_models()`` can be used to query a plugin registration system. 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 The child models
---------------- ----------------