Ticket #1815: docs.diff
| File docs.diff, 4.4 KB (added by , 18 years ago) |
|---|
-
docs/tutorial01.txt
69 69 * ``urls.py``: The URL declarations for this Django project; a "table of 70 70 contents" of your Django-powered site. 71 71 72 .. _more onpackages: http://docs.python.org/tut/node8.html#packages72 .. _more about packages: http://docs.python.org/tut/node8.html#packages 73 73 74 74 The development server 75 75 ---------------------- -
docs/request_response.txt
102 102 ``AuthenticationMiddleware`` activated. For more, see 103 103 `Authentication in Web requests`_. 104 104 105 .. Authentication in Web requests: http://www.djangoproject.com/documentation/authentication/#authentication-in-web-requests105 .. _Authentication in Web requests: http://www.djangoproject.com/documentation/authentication/#authentication-in-web-requests 106 106 107 107 ``session`` 108 108 A readable-and-writable, dictionary-like object that represents the current -
docs/db-api.txt
1070 1070 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1071 1071 1072 1072 Django offers a powerful and intuitive way to "follow" relationships in 1073 lookups, taking care of the SQL ``JOIN`` s for you automatically, behind the1073 lookups, taking care of the SQL ``JOIN``\s for you automatically, behind the 1074 1074 scenes. To span a relationship, just use the field name of related fields 1075 1075 across models, separated by double underscores, until you get to the field you 1076 1076 want. -
docs/model-api.txt
52 52 * The name of the table, ``myapp_person``, is automatically derived from 53 53 some model metadata but can be overridden. See _`Table names` below. 54 54 * An ``id`` field is added automatically, but this behavior can be 55 overriden. See _`Automatic primary key fields`below.55 overriden. See `Automatic primary key fields`_ below. 56 56 * The ``CREATE TABLE`` SQL in this example is formatted using PostgreSQL 57 57 syntax, but it's worth noting Django uses SQL tailored to the database 58 58 backend specified in your `settings file`_. … … 124 124 An ``IntegerField`` that automatically increments according to available IDs. 125 125 You usually won't need to use this directly; a primary key field will 126 126 automatically be added to your model if you don't specify otherwise. See 127 _`Automatic primary key fields`.127 `Automatic primary key fields`_. 128 128 129 129 ``BooleanField`` 130 130 ~~~~~~~~~~~~~~~~ … … 1111 1111 isn't an ``AutoField`` and has ``editable=True``, in a single fieldset, in 1112 1112 the same order as the fields are defined in the model. 1113 1113 1114 The ``field_options`` dictionary can have the following keys: :1114 The ``field_options`` dictionary can have the following keys: 1115 1115 1116 1116 ``fields`` 1117 1117 ~~~~~~~~~~ … … 1312 1312 section of the database API docs, but this section specifically touches on 1313 1313 model options that customize ``Manager`` behavior. 1314 1314 1315 .. _Retrieving objects: http://www.djangoproject.com/documentation/db_api/#retrieving-objects 1316 1315 1317 Manager names 1316 1318 ------------- 1317 1319 … … 1401 1403 1402 1404 ...the statement ``Book.objects.all()`` will return all books in the database. 1403 1405 1404 You can override a ``Manager`` 's base ``QuerySet`` by overriding the1406 You can override a ``Manager``\'s base ``QuerySet`` by overriding the 1405 1407 ``Manager.get_query_set()`` method. ``get_query_set()`` should return a 1406 1408 ``QuerySet`` with the properties you require. 1407 1409 1408 For example, the following model has *two* ``Manager`` s -- one that returns1410 For example, the following model has *two* ``Manager``\s -- one that returns 1409 1411 all objects, and one that returns only the books by Roald Dahl:: 1410 1412 1411 1413 # First, define the Manager subclass. -
docs/generic_views.txt
62 62 instance; see the `database API docs`_ for more information about ``Queryset`` 63 63 objects. 64 64 65 .. _database API docs: http://www.djangoproject.com/documentation/db_api/ 66 65 67 "Simple" generic views 66 68 ====================== 67 69