Feature #1104
Periodic EPG Save
| Status: | Accepted | Start date: | 08/12/2012 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: |  Adam Sutton | % Done: | 0% | |
| Category: | EPG | |||
| Target version: | - |
Description
Moving this from my github:
Some people have asked for periodic EPG DB save to disk, mainly to retain info should system crash (not that that should happen). But it can also be useful for test purposes.
One variation on this could be to always store the DB (if modified) after a significant update. Exactly what a significant update means I'm not sure:
cumulative number of changes
non EIT now/next update (since they tend to be large batch updates).