Added 'Does Django support multiple-column primary keys?' to FAQ
git-svn-id: http://code.djangoproject.com/svn/django/trunk@2204 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
233708fb68
commit
41fac5f9ef
12
docs/faq.txt
12
docs/faq.txt
|
@ -363,6 +363,18 @@ avoid automating. That said, there's some work being done to add a
|
||||||
``django-admin.py updatedb`` command, which would output the necessary
|
``django-admin.py updatedb`` command, which would output the necessary
|
||||||
``ALTER TABLE`` statements, if any.
|
``ALTER TABLE`` statements, if any.
|
||||||
|
|
||||||
|
Do Django models support multiple-column primary keys?
|
||||||
|
------------------------------------------------------
|
||||||
|
|
||||||
|
No. Only single-column primary keys are supported.
|
||||||
|
|
||||||
|
But this isn't an issue in practice, because there's nothing stopping you from
|
||||||
|
adding other constraints (using the ``unique_together`` model option or
|
||||||
|
creating the constraint directly in your database), and enforcing the
|
||||||
|
uniqueness at that level. Single-column primary keys are needed for things such
|
||||||
|
as the admin interface to work; e.g., you need a simple way of being able to
|
||||||
|
specify an object to edit or delete.
|
||||||
|
|
||||||
The database API
|
The database API
|
||||||
================
|
================
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue