From 580389c588ade9709f54c1494c5af6747011f043 Mon Sep 17 00:00:00 2001 From: Timo Graham Date: Sat, 31 Dec 2011 00:43:31 +0000 Subject: [PATCH] [1.3.X] Fixed #702 - Documented that ManyToMany fields can't be in unique_together; thanks poirier for the patch. Backport of r17314 from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.3.X@17315 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/ref/models/options.txt | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/ref/models/options.txt b/docs/ref/models/options.txt index 45304392b4..aae90d0b6a 100644 --- a/docs/ref/models/options.txt +++ b/docs/ref/models/options.txt @@ -238,6 +238,12 @@ Django quotes column and table names behind the scenes. unique_together = ("driver", "restaurant") + A :class:`~django.db.models.ManyToManyField` cannot be included in + unique_together (it's not even clear what that would mean). If you + need to validate uniqueness related to a + :class:`~django.db.models.ManyToManyField`, look at signals or + using an explicit :attr:`through ` model. + ``verbose_name`` ----------------