Changeset 2869
- Timestamp:
- 05/09/06 10:21:28 (3 years ago)
- Files:
-
- django/trunk/docs/db-api.txt (modified) (1 diff)
- django/trunk/docs/generic_views.txt (modified) (1 diff)
- django/trunk/docs/model-api.txt (modified) (5 diffs)
- django/trunk/docs/request_response.txt (modified) (1 diff)
- django/trunk/docs/tutorial01.txt (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
django/trunk/docs/db-api.txt
r2862 r2869 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 django/trunk/docs/generic_views.txt
r2809 r2869 63 63 objects. 64 64 65 .. _database API docs: http://www.djangoproject.com/documentation/db_api/ 66 65 67 "Simple" generic views 66 68 ====================== django/trunk/docs/model-api.txt
r2863 r2869 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 … … 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`` … … 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`` … … 1312 1312 section of the database API docs, but this section specifically touches on 1313 1313 model options that customize ``Manager`` behavior. 1314 1315 .. _Retrieving objects: http://www.djangoproject.com/documentation/db_api/#retrieving-objects 1314 1316 1315 1317 Manager names … … 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 django/trunk/docs/request_response.txt
r2809 r2869 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`` django/trunk/docs/tutorial01.txt
r2853 r2869 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
