Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

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
  • Loading branch information...
commit 1f233b479ad1329c7137f033c366b8f4894a6cd7 1 parent c471d47
Malcolm Tredinnick malcolmt authored
Showing with 3 additions and 3 deletions.
  1. +3 −3 docs/topics/db/models.txt
6 docs/topics/db/models.txt
View
@@ -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
Please sign in to comment.
Something went wrong with that request. Please try again.