diff options
| author | Gary Wilson Jr <gary.wilson@gmail.com> | 2007-08-05 04:42:26 +0000 |
|---|---|---|
| committer | Gary Wilson Jr <gary.wilson@gmail.com> | 2007-08-05 04:42:26 +0000 |
| commit | 973f44aa4c953baf6bf56b8e5c474f5306452809 (patch) | |
| tree | 5dccfc0f08921a76e876e38ddc3112974b25ba8a /docs | |
| parent | eba5703fee221bc2ace9fcd2b6873d7e1cdf6753 (diff) | |
Changed some more links to be relative in the documentation. I had a couple unsaved files that didn't get in with [5798].
git-svn-id: http://code.djangoproject.com/svn/django/trunk@5802 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/db-api.txt | 2 | ||||
| -rw-r--r-- | docs/model-api.txt | 10 |
2 files changed, 6 insertions, 6 deletions
diff --git a/docs/db-api.txt b/docs/db-api.txt index 33b4194742..080ab0de16 100644 --- a/docs/db-api.txt +++ b/docs/db-api.txt @@ -1834,7 +1834,7 @@ Note that in the case of identical date values, these methods will use the ID as a fallback check. This guarantees that no records are skipped or duplicated. For a full example, see the `lookup API sample model`_. -.. _lookup API sample model: http://www.djangoproject.com/documentation/models/lookup/ +.. _lookup API sample model: ../models/lookup/ get_FOO_filename() ------------------ diff --git a/docs/model-api.txt b/docs/model-api.txt index 3509fa4ba0..f2806bbe31 100644 --- a/docs/model-api.txt +++ b/docs/model-api.txt @@ -22,7 +22,7 @@ A companion to this document is the `official repository of model examples`_. ``tests/modeltests`` directory.) .. _Database API reference: ../db-api/ -.. _official repository of model examples: http://www.djangoproject.com/documentation/models/ +.. _official repository of model examples: ../models/ Quick example ============= @@ -775,7 +775,7 @@ You can, of course, call the field whatever you want. For example:: See the `Many-to-one relationship model example`_ for a full example. -.. _Many-to-one relationship model example: http://www.djangoproject.com/documentation/models/many_to_one/ +.. _Many-to-one relationship model example: ../models/many_to_one/ ``ForeignKey`` fields take a number of extra arguments for defining how the relationship should work. All are optional: @@ -902,7 +902,7 @@ set up above, the ``Pizza`` admin form would let users select the toppings. See the `Many-to-many relationship model example`_ for a full example. -.. _Many-to-many relationship model example: http://www.djangoproject.com/documentation/models/many_to_many/ +.. _Many-to-many relationship model example: ../models/many_to_many/ ``ManyToManyField`` objects take a number of extra arguments for defining how the relationship should work. All are optional: @@ -979,7 +979,7 @@ as a read-only field when you edit an object in the admin interface: See the `One-to-one relationship model example`_ for a full example. -.. _One-to-one relationship model example: http://www.djangoproject.com/documentation/models/one_to_one/ +.. _One-to-one relationship model example: ../models/one_to_one/ Custom field types ------------------ @@ -1186,7 +1186,7 @@ See `Specifying ordering`_ for more examples. Note that, regardless of how many fields are in ``ordering``, the admin site uses only the first field. -.. _Specifying ordering: http://www.djangoproject.com/documentation/models/ordering/ +.. _Specifying ordering: ../models/ordering/ ``permissions`` --------------- |