summaryrefslogtreecommitdiff
path: root/docs/ref
diff options
context:
space:
mode:
authorRaúl Cumplido <raulcd@tid.es>2012-06-07 13:46:06 +0200
committerTim Graham <timograham@gmail.com>2012-06-30 17:24:26 -0400
commit342e8a6246d0c3893ecbe80584f30d6d0f05aa6f (patch)
treec3ec8852767be2d3dd2cacfb83ef0cacbeca50da /docs/ref
parenta89e76d15149c0758e6459d695ce60722cad7101 (diff)
[1.4.X] Fixed #18145 -- Improved documentation of unique_together type fields
Backport of 55ffcf8e7b from master
Diffstat (limited to 'docs/ref')
-rw-r--r--docs/ref/models/options.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/ref/models/options.txt b/docs/ref/models/options.txt
index 6ca3d3b2d0..9d076f6274 100644
--- a/docs/ref/models/options.txt
+++ b/docs/ref/models/options.txt
@@ -244,12 +244,12 @@ Django quotes column and table names behind the scenes.
unique_together = (("driver", "restaurant"),)
- This is a list of lists of fields that must be unique when considered together.
+ This is a tuple of tuples that must be unique when considered together.
It's used in the Django admin and is enforced at the database level (i.e., the
appropriate ``UNIQUE`` statements are included in the ``CREATE TABLE``
statement).
- For convenience, unique_together can be a single list when dealing with a single
+ For convenience, unique_together can be a single tuple when dealing with a single
set of fields::
unique_together = ("driver", "restaurant")