Agh, timezone in postgres, that’s another can of worm.
Maybe I just try leave it current way. Thanks.
The file archive’s behavior in v6 is new compared to v5, right? (It’s ok, I just should have realize I am looking at a v6, not v5 archive.)
I have another question. I have a python script to partially replicate what you did with ScadaData.dll
in v5 (only archive parsing, current/archive cnldata receiving and command send). With cython the performance is finally on par with the .net dll. But I am having checksum error with a small number of archives.
Polling the archive used to be easy – acquiring the .dat file and parse it, only grab the records of the time in range. The the archive disk file layout on v6 seems more fragmented and confusing.
I don’t think I saw any scadadata.dll
in v6, is there any equivalent code in v6 or a TCP interface document available?
Regards