mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-10-23 21:59:11 +00:00
Code Issues 32 Releases Wiki Activity

Refs #36070 -- Referred to pk as an attribute when a composite primary key is defined.

Browse Source 
This is to avoid confusion that a field is often associated with having
a single associated database column.
This commit is contained in:
Jacob Walls
2025-01-14 16:43:49 +01:00
committed by Sarah Boyce
parent b721f12760
commit f054045973
4 changed files with 16 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/topics/composite-primary-key.txt
View File

@@ -11,8 +11,8 @@ In most cases, a single primary key should suffice. In database design,
however, defining a primary key consisting of multiple fields is sometimes
necessary.
To use a composite primary key, when creating a model set the ``pk`` field to
be a :class:`.CompositePrimaryKey`::
To use a composite primary key, when defining a model set the ``pk`` attribute
to be a :class:`.CompositePrimaryKey`::
class Product(models.Model):
name = models.CharField(max_length=100)
@@ -41,8 +41,8 @@ A composite primary key is represented by a ``tuple``:
>>> item.pk
(1, "A755H")
You can assign a ``tuple`` to a composite primary key. This sets the associated
field values.
You can assign a ``tuple`` to the :attr:`~django.db.models.Model.pk` attribute.
This sets the associated field values:
.. code-block:: pycon