github/rails
1
1
Fork 0
mirror of https://github.com/github/rails.git synced 2026-04-26 03:00:59 -04:00
Code Issues Packages Projects Releases Wiki Activity

Update with globally keyed fragments

Browse Source
This commit is contained in:
Aditya
2008-11-23 15:17:03 -05:00
parent f3ac3fafbc
commit d67adf1e33
1 changed files with 19 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
railties/doc/guides/source/caching_with_rails.txt
View File

@@ -176,7 +176,25 @@ and you can expire it using the `expire_fragment` method, like so:
[source, ruby]
-----------------------------------------------------
expire_fragment(:controller => 'producst', :action => 'recent', :action_suffix => 'all_products)
expire_fragment(:controller => 'products', :action => 'recent', :action_suffix => 'all_products)
-----------------------------------------------------
If you don't want the cache block to bind to the action that called it, You can
also use globally keyed fragments by calling the cache method with a key, like
so:
[source, ruby]
-----------------------------------------------------
<% cache(:key => ['all_available_products', @latest_product.created_at].join(':')) do %>
All available products:
-----------------------------------------------------
This fragment is then available to all actions in the ProductsController using
the key and can be expired the same way:
[source, ruby]
-----------------------------------------------------
expire_fragment(:key => ['all_available_products', @latest_product.created_at].join(':'))
-----------------------------------------------------
[More: more examples? description of fragment keys and expiration, etc? pagination?]