Documentation mentions default primary key being regular IntegerField, not BigAutoField

[Ari Pollak]

BigAutoField is the default type of primary key now, and in Postgres, regular IntegerField only goes up to around 2 billion. However, a couple of pages still talk about the default primary key being an IntegerField.

Under ​https://docs.djangoproject.com/en/5.1/topics/db/models/#field-options:

If you don’t specify primary_key=True for any fields in your model, Django will automatically add an IntegerField to hold the primary key, so you don’t need to set primary_key=True on any of your fields unless you want to override the default primary-key behavior. For more, see Automatic primary key fields

Under ​https://docs.djangoproject.com/en/5.1/ref/contrib/contenttypes/#generic-relations:

2. Give your model a field that can store primary key values from the models you’ll be relating to. For most models, this means a PositiveIntegerField. The usual name for this field is “object_id”.

[Ari Pollak]

Pull request: ​https://github.com/django/django/pull/18970

[dimen61]

Hi, Ari. Since you are working with this issue, please update the tag "Owned by" to youself.

[Sarah Boyce <42296566+sarahboyce@…>]

In ad385ae:

Fixed #36037 -- Fixed default primary key type in docs.

BigAutoField is the default type for primary keys. In models.txt, the linked
anchor shows that the default primary key is a BigAutoField, so it now defers
to that section instead of duplicating an (incorrect) type.