Skip to content

Database schemas

WideQuick MOD uses several SQLite databases stored in the Data/ folder of the project. Each database is owned by a specific set of modules and should only be accessed through the scripts that manage it.

Note

WideQuick supports multiple types of databases. Moving from one to another is straightforward, but custom queries may need adjusting, since the engines use different SQL dialects. See Distinctive Features Of SQLite for more on this.

Contents

Config

  • Config — The central configuration database. Stores navigation structures, object registrations, scheduled jobs, report queues, logbook entries, document references, and saved user settings across most MOD modules.

History

  • History — Stores logged signal data. Tables are generated dynamically by loggers — each logger produces a data table and a meta table identified by a hash of the logger name.

Maintenance

  • Maintenance — Stores maintenance task configurations, the task log, change history, calendar events, and the registry of known remote systems.

SuffixConfig

  • SuffixConfig — Stores the suffix object configuration as JSON. Used by the suffix system to resolve tag structures at runtime.

BackUpAndRestore

  • BackUpAndRestore — Stores the variables staged for backup and the list of saved backups, along with the saved variable values for each one.

EventList

  • EventList — Stores the system event log and the list of variables tracked by the Audit Trail feature.

Larmlista

  • Larmlista — Stores logged alarm status changes. Tables are generated by the alarm logger, similar to the History database.