|
|
| (12 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | The '''Enable Caching''' options on the [[:Category:Reports|Report]] settings page can be used to help improve loading time and reduce the processing load on the server.
| + | #REDIRECT [[Reports#Report and Field Caching]] |
| − | | |
| − | | |
| − | Complex report and reports that are accessed regularly will benefit the most from the '''Enable Caching''' option.
| |
| − | :[[Image:Repcache.png]]
| |
| − | | |
| − | * Reports can also be '''Cached By User''' when appropriate (Note that you must select both '''Enable Caching''' and '''Cache by User''' and enter an appropriate '''Cache Life Span'''
| |
| − | | |
| − | | |
| − | Rather than creating the report each time it is run, caching stores the results for the duration specified in the '''Cache Life Span''' field.:
| |
| − | * The first time a report is viewed it will create it by querying the database and show live data.
| |
| − | * Anyone viewing the report after this, within the life span specified will see a snapshot of the report from the cache. Changed to underlying data will '''not''' be reflected in the report during the '''Cache Life Span'''
| |
| − | * The report will be updated once the life span has expired, and any changes to the underlying data will then be reflected.
| |
| − | | |
| − | | |
| − | ==IMPORTANT==
| |
| − | * '''Reports that prompt for criteria should NOT be cached in any way.'''
| |
| − | * Reports that include criteria based on the current user (i.e. '''@userid@''') must be cached by user.
| |
| − | | |
| − | ==See Also==
| |
| − | * [[Straight Join]]
| |
| − | | |
| − | | |
| − | [[Category:Reports]]
| |
