Write, Bureaucrats, Administrators
135
edits
Difference between revisions of "Archive Types"
no edit summary
| Line 2: | Line 2: | ||
OdataLink Models have archive types | OdataLink Models have archive types | ||
These exist to improve the refresh rate in scenarios where | These exist to improve the refresh rate in scenarios where its 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 | # '''Live''' optimises the model for end user use. At all times the latest data is returned | ||
# '''Developer''' optimises the model for development. If the last refresh occured more than 8 hours ago then retrieve the latest data and cache it, else return the data stored in the cache. The benefit of this Archive type is that it makes refreshes faster but the downside is your not always seeting the latest data | # '''Developer''' optimises the model for development. If the last refresh occured more than 8 hours ago then retrieve the latest data and cache it, else return the data stored in the cache. The benefit of this Archive type is that it makes refreshes faster but the downside is your not always seeting the latest data | ||
# '''Static''' optimises 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. | # '''Static''' optimises 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]] | |||