Log In
Home
06/27/2023
Offline
Is the following correct?
Suppose I have a historian with the following timestamp-values:
5:00 - 10
5:01 - 20
5:02 - 30
If I update the value for timestamp 5:01 (value = 25) using my client app then it becomes modified (5:01 - 20 and 5:01 - 25).
If I read the raw values (isReadModified is set to FALSE) then the server should return the following:
5:00 - 10
5:01 - 25
5:02 - 30
(including timestamp 5:01 with latest modified value(?)).
If I read modified values (isReadModified is set to TRUE) then I should only get two values for timestamp 5:01 (5:01 - 20 and 5:01 - 25), (but 5:00 and 5:02 will not be included because they are not modified)
Moderators-Specifications
Moderators-Companion
Moderators-Implementation
Moderators-Certification
Moderators-COM
02/24/2014
Offline
Some clarifications: A Historian is not required to support modification of historical data and if it does it is not required to store old values (modified records). With that said most historian do support this functionality. The read raw (isReadModified is set to FALSE) behaviour you are describing is correct. But the isReadModified is set to True is not - you would get a structure back that has more information
From the specification: "it reads the ModifiedValues, StatusCodes, timestamps, modification type, the user identifier, and the timestamp of the modification from the history database for the specified time domain for one or more HistoricalDataNodes. If there are multiple replaced values the Server shall return all of them. The updateType specifies what value is returned in the modification record. If the updateType is INSERT the value is the new value that was inserted. If the updateType is anything else the value is the old value that was changed."
Assuming you replaced the value when changing it, you would see just the 20.
Paul
Paul Hunkar - DSInteroperability
1 Guest(s)
Usage Policy