Write, Bureaucrats, Administrators
135
edits
Difference between revisions of "Archive Types"
Jump to navigation
Jump to search
→Overview
| Line 2: | Line 2: | ||
OdataLink Models have archive types | OdataLink Models have archive types | ||
These include Live, Developer and Static | |||
Those in addition to Live exist to improve the refresh rate in scenarios where speed is more important than retrieving latest live data from the source | Those in addition to Live exist to improve the refresh rate in scenarios where speed is more important than retrieving latest live data from the source | ||
=== Live === | |||
Optimises the model for end user use. | |||
At all times the latest data is returned. | |||
Its the slowest for returning data | |||
To be used once development is completed | |||
=== Developer === | |||
Optimises the model for development. | |||
Cached data is returned where the last retrieval was less than 8 hours ago | |||
The benefit of this Archive type is that it makes refreshes faster but the downside is your not always retrieving the latest data. | |||
This is the default when creating a model. | |||
Once development is completed switch it back to '''Live''' | |||
=== Static | |||
Optimises the model for historica data that never changes. | |||
that data to pull blocks of records that will never change. | |||
The model only returns the latest data once for the defined parameters and then caches it and only ever returns that cached data going forward. | |||
Use this option if you wish to report on historical data from previous financial years and append with live data for the current year. | |||
To change an archive type see [[Editing a model's details]] | To change an archive type see [[Editing a model's details]] | ||