Overview
The Historian module implements data storage based on classical table systems. Although an SQLite database is integrated into FrameworkX, the module is also compatible with various other types of databases.
To streamline the table creation process across different database types, it is possible to define generic characteristics. These characteristics will subsequently be utilized in generating the table in the chosen target database (TargetDB). While this procedure can also be independently performed directly within the Database Management System (DBMS) in use, introducing this abstraction layer enables users to customize settings such as table name, data type, data lifespan, and others. In the event of a potential architectural migration, these configurations are automatically applied to the new database without the need for manual adjustments.
On this page:
Historian Tables Configuration
A historian table delineates some characteristics regarding how data will be written to its target, standardizing requirements for different types of databases. In practice, the software incorporates distinct implementations for various databases, aiming to accomplish identical tasks. However, for the user, the interface remains consistent irrespective of the chosen target.
Properties
| Property | Description |
|---|---|
| Name | Chose a name for the table, the name is chosen by the user, respecting the naming rules. |
| ArchiveLocation | The Target DB's name. |
| AutoCreate | |
| SaveOnChange | |
| TimeDeadBand | |
| LifeTime | |
| SaveQuality | |
| ValueType | |
| Trigger | |
| Normalized | |
| Level | |
| Category | |
| LockState | |
| LockOwwner | |
| DateCreated | |
| DateModified | |
| Description |
Paragraph
In this section...