innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

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
This commit is contained in:
Malcolm Tredinnick 2011-08-22 01:07:19 +00:00
parent c471d471bf
commit 1f233b479a
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/topics/db/models.txt
View File

@ -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) :class:`~django.db.models.ManyToManyField` (``toppings`` in the example above)
be a plural describing the set of related model objects. be a plural describing the set of related model objects.
It doesn't matter which model gets the It doesn't matter which model has the
:class:`~django.db.models.ManyToManyField`, but you only need it in one of the :class:`~django.db.models.ManyToManyField`, but you should only put it in one
models -- not in both. of the models -- not both.
Generally, :class:`~django.db.models.ManyToManyField` instances should go in the 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 object that's going to be edited in the admin interface, if you're using