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.
In order to streamline the table creation process across different database types, it is feasible to define generic characteristics. These characteristics will subsequently be employed for table creation in the selected database, designated as TargetDB. This procedure can also be independently conducted directly within the Database Management System (DBMS) in use. The introduction of this abstraction layer enables users to customize settings such as table name, data type, data lifespan, and so forth. This not only facilitates the automatic creation of the table but also provides numerous advantages from the perspective of potential database architectural migrations.
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 | If true, when run a project with a HistorianTable properly configured, the table will be created automatically into de TargetDB. |
| SaveOnChange | |
| TimeDeadBand | |
| LifeTime | |
| SaveQuality | |
| ValueType | |
| Trigger | |
| Normalized | |
| Level | |
| Category | |
| LockState | |
| LockOwwner | |
| DateCreated | |
| DateModified | |
| Description |
Paragraph
In this section...