Changes between Version 3 and Version 4 of TracDev/CacheManager

Timestamp:

Apr 17, 2014, 4:16:11 PM (10 years ago)

Author:

Remy Blank

Comment:

Removed an obsolete bullet point.

TracDev/CacheManager

@@ -33 +33 @@
 }}}
 
- * If more control is needed, for example to invalidate an attribute within an existing transaction, the attribute should be decorated with the '''`@cached`''' decorator. Accessing the attribute then yields a proxy object with two methods, `get()` and `invalidate()`, taking an optional `db` argument. For example, this is used in the case of ticket fields to invalidate them in the same transaction as e.g. an enum modification.
-
  * The cache is '''consistent within a request'''. That is, a cached attribute will always have the same value during a given transaction. Obviously, cached values should be treated as immutable.