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 19824,Technically ambiguous reference docs for Field.primary_key,Keryn Knight ,nobody,"In the [https://docs.djangoproject.com/en/dev/ref/models/fields/ Model Field Reference], the description for [https://docs.djangoproject.com/en/dev/ref/models/fields/#primary-key Field.primary_key] says that ''Django will automatically add an IntegerField to hold the primary key'' - this is semi-correct, because Django actually provides an AutoField, itself internally represented as an IntegerField. I've provided a proposed fix in [https://github.com/kezabelle/django/tree/docs/fields_pk this branch] on GH. The only commit is [https://github.com/kezabelle/django/commit/f79a71d792552c5f7f28e5b99042fa52f912419e this one], which boils down to two changes: * Changed IntegerField to AutoField. This should be OK, as the AutoField documentation describes it being an IntegerField. * Removed pluralisation in ""for any fields in …"", changing to ""for any field in …"" as there can be only one on a model.",Uncategorized,closed,Documentation,dev,Normal,fixed,,,Unreviewed,1,0,0,0,0,0