#36037: Documentation mentions default primary key being regular IntegerField,
not
BigAutoField
-------------------------------------+-------------------------------------
Reporter: Ari Pollak | Owner: Ari
Type: | Pollak
Cleanup/optimization | Status: closed
Component: Documentation | Version: 5.1
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce <42296566+sarahboyce@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"ad385ae163da2b1c558f62c0415db5aa03227587" ad385ae]:
{{{#!CommitTicketReference repository=""
revision="ad385ae163da2b1c558f62c0415db5aa03227587"
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.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36037#comment:7>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701942768bdef-096a4be3-da63-4de7-b86e-3c071fb90621-000000%40eu-central-1.amazonses.com.
