diff options
| author | Malcolm Tredinnick <malcolm.tredinnick@gmail.com> | 2011-08-22 01:07:19 +0000 |
|---|---|---|
| committer | Malcolm Tredinnick <malcolm.tredinnick@gmail.com> | 2011-08-22 01:07:19 +0000 |
| commit | 1f233b479ad1329c7137f033c366b8f4894a6cd7 (patch) | |
| tree | 79d64b5164152fe1b92aee960ac82173c190c468 /docs | |
| parent | c471d471bf9cb4f8da1fad78c5037660186ba6fd (diff) | |
Made documentation of ManyToManyField placement clearer (kind of).
Inspired by ticket #16661.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@16639 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/topics/db/models.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/topics/db/models.txt b/docs/topics/db/models.txt index 0e18205e5d..d52c3c6669 100644 --- a/docs/topics/db/models.txt +++ b/docs/topics/db/models.txt @@ -363,9 +363,9 @@ It's suggested, but not required, that the name of a :class:`~django.db.models.ManyToManyField` (``toppings`` in the example above) be a plural describing the set of related model objects. -It doesn't matter which model gets the -:class:`~django.db.models.ManyToManyField`, but you only need it in one of the -models -- not in both. +It doesn't matter which model has the +:class:`~django.db.models.ManyToManyField`, but you should only put it in one +of the models -- not both. Generally, :class:`~django.db.models.ManyToManyField` instances should go in the object that's going to be edited in the admin interface, if you're using |