mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-11-02 04:48:33 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Fixed #24041 -- Documented effect of changing a model instance's primary key.

Browse source
This commit is contained in:
Helen Sherwood-Taylor 2014-12-24 19:15:48 +00:00 • committed by Tim Graham
parent 3daa9d60be
commit 4ccdf6e57f
2 changed files with 24 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/ref/models/fields.txt
View file

@ -278,8 +278,13 @@ 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
:ref:`automatic-primary-key-fields`.
``primary_key=True`` implies :attr:`null=False <Field.null>` and :attr:`unique=True <Field.unique>`.
Only one primary key is allowed on an object.
``primary_key=True`` implies :attr:`null=False <Field.null>` and
:attr:`unique=True <Field.unique>`. Only one primary key is allowed on an
object.
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.
``unique``
----------