1,651
edits
Recent history: Difference between revisions
m
→Recent History - Introduction
| Line 25: | Line 25: | ||
The data are held in [[cumulusmx.db|RecentData table in cumulusmx.db]] (uses SQLite). There are many software tools available that can read/edit SQLite3, this is not the place to get too technical, but take a look at '''sqlitebrowser''' in a Windows and Linux environment, and '''phpLiteAdmin''' in Microsoft Windows. Also, you could use any application that can read ODBC files (e.g. Libre Office's Base functionality) can read the MX databases. | The data are held in [[cumulusmx.db|RecentData table in cumulusmx.db]] (uses SQLite). There are many software tools available that can read/edit SQLite3, this is not the place to get too technical, but take a look at '''sqlitebrowser''' in a Windows and Linux environment, and '''phpLiteAdmin''' in Microsoft Windows. Also, you could use any application that can read ODBC files (e.g. Libre Office's Base functionality) can read the MX databases. | ||
While Cumulus is left running, every minute: | |||
#The oldest set of records, in database table row number 0 | |||
#Cumulus then works through subsequent table rows (or array elements), as it reads each one, it moves it to the previous (now empty) row (or array element) | |||
#The number of table rows, or array elements, is actually variable, this is because of two reasons: | |||
#*Table rows, or array elements, will be less frequent (or even missing) for the period before Cumulus is started | |||
#*Cumulus uses current time, read from the computer, in its decision as to where to store each new recent history value set, so it can overwrite existing table rows, or array elements, if date-time matches one that already exists, such as in the hour after when clocks go back. | |||
= Using Recent History = | = Using Recent History = | ||