5,838
edits
Cumulusmx.db (preserving history): Difference between revisions
From Cumulus Wiki
Jump to navigationJump to search
Cumulusmx.db (preserving history) (view source)
Revision as of 05:19, 5 September 2022
, 5 September 2022Further minor layout change
m (layout) |
m (Further minor layout change) |
||
|
==Location of this database file==
* This database file/files is/are specific to Cumulus MX (as the file name suggests), not used by legacy Cumulus 1
*
*# One database table with this name was held in Random Access Memory for MX Releases 3.0.0 to 3.11.4 inclusive
*#
* The two database tables were merged from release 3.12.0 (beta build 3134) and stored as '''/CumulusMX/data/cumulusmx.db''' (get case of each character correct unless Microsoft Windows Operating System)
==Database type==
This file/files holds a SQLite3 database. Databases of this type are based on sequential file design, i.e. each row in the database table is sequenced by when created (new rows are only appended on end), and given a sequential number to act as primary key (numbers are not automatically revised when a row is deleted).
The MX [[Weather Diary]] also uses a SQLite3 database stored in [[diary.db|CumulusMX/data/diary.db]].
== Reading/editing database table outside MX ==
| RecentData
| Updated once a minute when MX is running
* Database of this name with this table originally in RAM
▲* MX beta 3.0.0 in RAM
* In 3.12.0 (beta build 3134)
| The update.txt for CumulusMX at release 3.12.0 (beta build 3134) states "Change: Cumulus MX now uses a persistent database to store the recent 1 minute data
- This means that charts, recent web tags, and internal calculations for trends and periodic values will be more accurate after a restart
| Updated when certain conditions are met and SQL is queued
| MX 3.21.0
| The update.txt for CumulusMX at release 3.21.0 states "New - Failed MySQL commands can now be individually edited/deleted
Changed - Failed MySQL commands are now stored in the SQLite database to persist across Cumulus runs"▼
▲- Failed MySQL commands are now stored in the SQLite database to persist across Cumulus runs"
| Edit or purge the failed MySQL command queue using '''Utils menu''' -->> ''PurgeMySQL''
| At time of writing, the current MX release does not use this table
| MX beta 3.0.0
(always in file)
| In [https://cumulus.hosiene.co.uk/viewtopic.php?p=123594#p123594 this forum post] Steve Loft describes this table as being for a possible future enhancement. It is believed this is the table that Steve had developed in Cumulus 2, as a replacement for the [[Monthly_log_files]].
| At time of writing, the current MX release does not use this table
| |||
