Changeset 2331
- Timestamp:
- 02/18/06 10:22:31 (3 years ago)
- Files:
-
- django/trunk/docs/cache.txt (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
django/trunk/docs/cache.txt
r1898 r2331 6 6 7 7 Django's cache framework gives you three methods of caching dynamic pages in 8 memory or in a database. You can cache the output of entire pages, you can8 memory or in a database. You can cache the output of specific views, you can 9 9 cache only the pieces that are difficult to produce, or you can cache your 10 10 entire site. … … 123 123 .. _`middleware documentation`: http://www.djangoproject.com/documentation/middleware/ 124 124 125 The per- pagecache125 The per-view cache 126 126 ================== 127 127 … … 153 153 Sometimes, however, caching an entire rendered page doesn't gain you very much. 154 154 For example, you may find it's only necessary to cache the result of an 155 intensive database . In cases like this, you can use the low-level cache API to156 store objects in the cache with any level of granularity you like.155 intensive database query. In cases like this, you can use the low-level cache 156 API to store objects in the cache with any level of granularity you like. 157 157 158 158 The cache API is simple::
