From b5e12d490af3debca8c55ab3c1698189fdedbbdb Mon Sep 17 00:00:00 2001 From: Tom Forbes Date: Sun, 12 Jul 2020 13:59:57 +0100 Subject: Fixed #31007 -- Allowed specifying type of auto-created primary keys. This also changes the default type of auto-created primary keys for new apps and projects to BigAutoField. --- docs/ref/models/fields.txt | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) (limited to 'docs/ref/models') diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt index 93c011fe2c..759e004fcf 100644 --- a/docs/ref/models/fields.txt +++ b/docs/ref/models/fields.txt @@ -415,9 +415,12 @@ cross-site scripting attack. If ``True``, this field is the primary key for the model. If you don't specify ``primary_key=True`` for any field in your model, Django -will automatically add an :class:`AutoField` 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 +will automatically add a field 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. The type of auto-created primary key fields can +be specified per app in :attr:`AppConfig.default_auto_field +` or globally in the +:setting:`DEFAULT_AUTO_FIELD` setting. For more, see :ref:`automatic-primary-key-fields`. ``primary_key=True`` implies :attr:`null=False ` and @@ -428,6 +431,11 @@ The primary key field is read-only. If you change the value of the primary key on an existing object and then save it, a new object will be created alongside the old one. +.. versionchanged:: 3.2 + + In older versions, auto-created primary key fields were always + :class:`AutoField`\s. + ``unique`` ---------- -- cgit v1.3