From 28e78f64e4fa15e7a7540e930e49dfc0e469ffc1 Mon Sep 17 00:00:00 2001
From: Derek Willis <dwillis@gmail.com>
Date: Sat, 19 Feb 2011 16:36:12 -0500
Subject: [PATCH] model Relationship backreference
---
docs/topics/db/models.txt | 15 ++++++++++-----
1 files changed, 10 insertions(+), 5 deletions(-)
diff --git a/docs/topics/db/models.txt b/docs/topics/db/models.txt
index 7bc2e09..48ef5d7 100644
a
|
b
|
whatever you want. For example::
|
320 | 320 | |
321 | 321 | See the `Many-to-one relationship model example`_ for a full example. |
322 | 322 | |
323 | | .. _Many-to-one relationship model example: http://code.djangoproject.com/browser/django/trunk/tests/modeltests/many_to_one/models.py |
| 323 | .. _Many-to-one relationship model example: http://code.djangoproject.com/browser/django/trunk/tests/modeltests/many_to_one/models.py |
324 | 324 | |
325 | | :class:`~django.db.models.ForeignKey` fields also accept a number of extra |
326 | | arguments which are explained in :ref:`the model field reference |
327 | | <foreign-key-arguments>`. These options help define how the relationship should |
328 | | work; all are optional. |
| 325 | :class:`~django.db.models.ForeignKey` fields also accept a number of extra |
| 326 | arguments which are explained in :ref:`the model field reference |
| 327 | <foreign-key-arguments>`. These options help define how the relationship should |
| 328 | work; all are optional. |
| 329 | |
| 330 | See the `Following relationships backward example`_ for more details on accessing backwards |
| 331 | related objects. |
| 332 | |
| 333 | .. _Following relationships backward example: http://docs.djangoproject.com/en/dev/topics/db/queries/#backwards-related-objects |
329 | 334 | |
330 | 335 | Many-to-many relationships |
331 | 336 | ~~~~~~~~~~~~~~~~~~~~~~~~~~ |