summaryrefslogtreecommitdiff
path: root/docs/ref
diff options
context:
space:
mode:
authorHelen Sherwood-Taylor <helenst@gmail.com>2014-12-24 19:15:48 +0000
committerTim Graham <timograham@gmail.com>2014-12-24 15:06:09 -0500
commit4ccdf6e57f49d7e981dcd88c1db65229b8b92487 (patch)
treeb1e5896da4d3fe43eaef629420a662d8c83eb15e /docs/ref
parent3daa9d60be6672841ceed5bb812b6fb25950dc16 (diff)
Fixed #24041 -- Documented effect of changing a model instance's primary key.
Diffstat (limited to 'docs/ref')
-rw-r--r--docs/ref/models/fields.txt9
1 files changed, 7 insertions, 2 deletions
diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt
index 5eabf84cad..35997801fb 100644
--- a/docs/ref/models/fields.txt
+++ b/docs/ref/models/fields.txt
@@ -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``
----------