Changeset 6775
- Timestamp:
- 11/29/07 23:34:04 (1 year ago)
- Files:
-
- django/trunk/docs/cache.txt (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
django/trunk/docs/cache.txt
r6774 r6775 304 304 ========================= 305 305 306 **New in development version** .306 **New in development version** 307 307 308 308 If you're after even more control, you can also cache template fragments using … … 320 320 321 321 Sometimes you might want to cache multiple copies of a fragment depending on 322 some dynamic data that appears inside the fragment. For example you maywant a322 some dynamic data that appears inside the fragment. For example, you might want a 323 323 separate cached copy of the sidebar used in the previous example for every user 324 of your site. This can be easily achieved by passing additional arguments to325 t he ``{% cache %}`` template tag to uniquely identify the cache fragment::324 of your site. Do this by passing additional arguments to the ``{% cache %}`` 325 template tag to uniquely identify the cache fragment:: 326 326 327 327 {% load cache %} … … 330 330 {% endcache %} 331 331 332 I f you need more than one argument to identify the fragment that's fine, simply333 pass as many arguments to ``{% cache %}`` as you need! 332 It's perfectly fine to specify more than one argument to identify the fragment. 333 Simply pass as many arguments to ``{% cache %}`` as you need. 334 334 335 335 The low-level cache API
