Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Fixed #4029 -- Fixed some broken links and made some links relative i…

…n docs/model-api.txt

git-svn-id: http://code.djangoproject.com/svn/django/trunk@5005 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit 73269ec8bc0db720e405f6366a9dd3f20d757128 1 parent e9e728c
Adrian Holovaty authored April 13, 2007

Showing 1 changed file with 12 additions and 12 deletions. Show diff stats Hide diff stats

  1. 24  docs/model-api.txt
24  docs/model-api.txt
@@ -21,7 +21,7 @@ A companion to this document is the `official repository of model examples`_.
21 21
 (In the Django source distribution, these examples are in the
22 22
 ``tests/modeltests`` directory.)
23 23
 
24  
-.. _Database API reference: http://www.djangoproject.com/documentation/db_api/
  24
+.. _Database API reference: ../db-api/
25 25
 .. _official repository of model examples: http://www.djangoproject.com/documentation/models/
26 26
 
27 27
 Quick example
@@ -57,7 +57,7 @@ Some technical notes:
57 57
       syntax, but it's worth noting Django uses SQL tailored to the database
58 58
       backend specified in your `settings file`_.
59 59
 
60  
-.. _settings file: http://www.djangoproject.com/documentation/settings/
  60
+.. _settings file: ../settings/
61 61
 
62 62
 Fields
63 63
 ======
@@ -501,7 +501,7 @@ For each model field that has ``choices`` set, Django will add a method to
501 501
 retrieve the human-readable name for the field's current value. See
502 502
 `get_FOO_display`_ in the database API documentation.
503 503
 
504  
-.. _get_FOO_display: ../db_api/#get-foo-display
  504
+.. _get_FOO_display: ../db-api/#get-foo-display
505 505
 
506 506
 Finally, note that choices can be any iterable object -- not necessarily a
507 507
 list or tuple. This lets you construct choices dynamically. But if you find
@@ -626,7 +626,7 @@ that takes the parameters ``field_data, all_data`` and raises
626 626
 
627 627
 Django comes with quite a few validators. They're in ``django.core.validators``.
628 628
 
629  
-.. _validator docs: http://www.djangoproject.com/documentation/forms/#validators
  629
+.. _validator docs: ../forms/#validators
630 630
 
631 631
 Verbose field names
632 632
 -------------------
@@ -792,8 +792,8 @@ relationship should work. All are optional:
792 792
                              the related object.
793 793
     =======================  ============================================================
794 794
 
795  
-.. _`Database API reference`: http://www.djangoproject.com/documentation/db_api/
796  
-.. _related objects documentation: http://www.djangoproject.com/documentation/db_api/#related-objects
  795
+.. _`Database API reference`: ../db-api/
  796
+.. _related objects documentation: ../db-api/#related-objects
797 797
 
798 798
 Many-to-many relationships
799 799
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -963,7 +963,7 @@ Example::
963 963
 
964 964
 See the `docs for latest()`_ for more.
965 965
 
966  
-.. _docs for latest(): http://www.djangoproject.com/documentation/db_api/#latest-field-name-none
  966
+.. _docs for latest(): ../db-api/#latest-field-name-none
967 967
 
968 968
 ``order_with_respect_to``
969 969
 -------------------------
@@ -1397,7 +1397,7 @@ if one of the ``list_display`` fields is a ``ForeignKey``.
1397 1397
 
1398 1398
 For more on ``select_related()``, see `the select_related() docs`_.
1399 1399
 
1400  
-.. _the select_related() docs: http://www.djangoproject.com/documentation/db_api/#select-related
  1400
+.. _the select_related() docs: ../db-api/#select-related
1401 1401
 
1402 1402
 ``ordering``
1403 1403
 ------------
@@ -1502,7 +1502,7 @@ The way ``Manager`` classes work is documented in the `Retrieving objects`_
1502 1502
 section of the database API docs, but this section specifically touches on
1503 1503
 model options that customize ``Manager`` behavior.
1504 1504
 
1505  
-.. _Retrieving objects: http://www.djangoproject.com/documentation/db_api/#retrieving-objects
  1505
+.. _Retrieving objects: ../db-api/#retrieving-objects
1506 1506
 
1507 1507
 Manager names
1508 1508
 -------------
@@ -1825,7 +1825,7 @@ just the ``where``, ``tables`` and ``params`` arguments to the standard lookup
1825 1825
 API. See `Other lookup options`_.
1826 1826
 
1827 1827
 .. _Python DB-API: http://www.python.org/peps/pep-0249.html
1828  
-.. _Other lookup options: http://www.djangoproject.com/documentation/db_api/#extra-params-select-where-tables
  1828
+.. _Other lookup options: ../db-api/#extra-params-select-where-tables
1829 1829
 
1830 1830
 Overriding default model methods
1831 1831
 --------------------------------
@@ -1858,7 +1858,7 @@ You can also prevent saving::
1858 1858
             else:
1859 1859
                 super(Blog, self).save() # Call the "real" save() method.
1860 1860
 
1861  
-.. _database API docs: http://www.djangoproject.com/documentation/db_api/
  1861
+.. _database API docs: ../db-api/
1862 1862
 
1863 1863
 Models across files
1864 1864
 ===================
@@ -1924,7 +1924,7 @@ order in which they're executed. The only thing you can assume is that, by the
1924 1924
 time your custom data files are executed, all the database tables already will
1925 1925
 have been created.
1926 1926
 
1927  
-.. _`manage.py documentation`: http://www.djangoproject.com/documentation/django_admin/#sqlcustom-appname-appname
  1927
+.. _`manage.py documentation`: ../django_admin/#sqlcustom-appname-appname
1928 1928
 
1929 1929
 Database-backend-specific SQL data
1930 1930
 ----------------------------------

0 notes on commit 73269ec

Please sign in to comment.
Something went wrong with that request. Please try again.