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 20113,Documentation on _ptr and _ptr_id use in multi-table inheritance,anonymous,nobody,"The documentation on ""Multi-table inheritance"" does not mention the naming of the (generated) primary / foreign key field of the inheriting table (which becomes place_ptr_id in the Place / Restaurant example). If I use instance data from that model in a template, and want to render the fields myself, I need that name, as described in ""Using the formset in the template"": {{{
{{ formset.management_form }} {% for form in formset %} {{ form.place_ptr }} {% endfor %}
}}} Confusingly, the name which should be used here is ""place_ptr"", not ""place_ptr_id"", which it is in the database (using ""place_ptr_id"" in the template gives a MultiValueDictKeyError). Since this is not documented (or I haven't found it, though I did search!), I suggest adding something to the ""Multi-table inheritance"" documentation which explains how the auto-generated field can be used in templates as ""place_ptr"". ",Cleanup/optimization,closed,Documentation,1.5,Normal,duplicate,,,Unreviewed,0,0,0,0,0,0