mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-10-23 21:59:11 +00:00
Code Issues 32 Releases Wiki Activity

[1.7.x] Fixed display of lists after website redesign

Browse Source 
Thanks Brian Jacobel for the report. refs django/djangoproject.com#197

Backport of c7786550c4 from master
This commit is contained in:
Markus Holtermann
2014-12-17 14:01:19 +01:00
committed by Tim Graham
parent ebfb1dab26
commit a38951948a
4 changed files with 38 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/topics/cache.txt
View File

@@ -168,11 +168,12 @@ got a fast, well-indexed database server.
To use a database table as your cache backend:
* Set :setting:`BACKEND <CACHES-BACKEND>` to
``django.core.cache.backends.db.DatabaseCache``
* Set :setting:`LOCATION <CACHES-LOCATION>` to ``tablename``, the name of
the database table. This name can be whatever you want, as long as it's
a valid table name that's not already being used in your database.
* Set :setting:`BACKEND <CACHES-BACKEND>` to
``django.core.cache.backends.db.DatabaseCache``
* Set :setting:`LOCATION <CACHES-LOCATION>` to ``tablename``, the name of the
database table. This name can be whatever you want, as long as it's a valid
table name that's not already being used in your database.
In this example, the cache table's name is ``my_cache_table``::

6
docs/topics/forms/index.txt
View File

@@ -148,9 +148,9 @@ Instantiating, processing, and rendering forms
When rendering an object in Django, we generally:
1. get hold of it in the view (fetch it from the database, for example)
2. pass it to the template context
3. expand it to HTML markup using template variables
1. get hold of it in the view (fetch it from the database, for example)
2. pass it to the template context
3. expand it to HTML markup using template variables
Rendering a form in a template involves nearly the same work as rendering any
other kind of object, but there are some key differences.