/ doc / DocFrag / ARCCore.StreamProcessorP.TimestampResolution / Attribute

Attribute

Edit keys at this level only

Edit keys at all sub levels.
NOTE: Edits are always additive. Use 'Invalid' in order to delete keys.

Description = The time interval between each timestamp update in the -PropertyStream-.0x000D0x000A0x000D0x000A(See also -TimestampResolution- concept in -ARCEvent-.-UtilEvent-.)0x000D0x000A0x000D0x000AUsed by -AddTimestampAsRequired-.0x000D0x000A0x000D0x000AOnly relevant for -CoreDB- (there should only be one source of timestamps in the system).0x000D0x000A(If this value is present, then -StreamProcessor- will insert timestamps at the specified interval).0x000D0x000A0x000D0x000ABackground: The -PropertyStream- principle lends itself well to keeping historical track of changes in your database. A method for timestamping the updates is therefore also natural to include.0x000D0x000A0x000D0x000ABut, by default, timestamps are not stored with each -PropertyStream--line. (you might have expected each property stream line to start with a timestamp like '2020-04-26 11:02:37' but that is not the case.)0x000D0x000A0x000D0x000AInstead, timestamps are inserted at regular intervals in the stream as Timestamp = 0x005Byyyy-MM-dd HH:mm ...0x005D. This is a practical approach reflecting the fact that consecutive timestamps will often be identical anyway and therefore just taking up space.0x000D0x000A0x000D0x000ANote that if this value is not set at all, then neither will timestamps be inserted into the -PropertyStream-.0x000D0x000A0x000D0x000AThe higher value chosen, the less space timestamps will take up in storage and transfer.0x000D0x000A0x000D0x000ASet to the highest value acceptable according to your time-resolution needs. If you have a need for a one-minute accuracy for timestamps, set this value to 1 minute.0x000D0x000A0x000D0x000AIf you want the highest possible resolution for when properties are created (down to the millisecond), set a resolution of one millisecond (ticks are not supported).0x000D0x000A
LongDescription = Properties for which we want to store in-memory a -Created-, / -Invalid- field or similar are given the latest timestamp value found.
PKTypeAttribute/BoilerplateCodeProperties = // Autogenerated boilerplate code. Paste into your class as needed.0x000D0x000Apublic TimeSpan TimestampResolution0x007B0x000D0x000A  get =0x003E IP.GetPV0x003CTimeSpan0x003E(StreamProcessorP.TimestampResolution)0x003B0x000D0x000A  set =0x003E IP.SetPV(StreamProcessorP.TimestampResolution, value)0x003B0x000D0x000A0x007D0x000D0x000Apublic AddTimestampResolution(TimeSpan timestampResolution) =0x003E IP.AddPV(StreamProcessorP.TimestampResolution, timestampResolution)0x003B0x000D0x000Apublic TimeSpan? GetTimestampResolution() =0x003E TryGetTimestampResolution(out var retval) ? retval : null0x003B0x000D0x000Apublic TimeSpan GetTimestampResolution(TimeSpan defaultValue) =0x003E TryGetTimestampResolution(out var retval) ? retval : defaultValue0x003B0x000D0x000Apublic bool TryGetTimestampResolution(out TimeSpan timestampResolution) =0x003E IP.TryGetPV(StreamProcessorP.TimestampResolution, out timestampResolution)0x003B0x000D0x000A0x000D0x000A0x000D0x000A
PKTypeAttribute/Cardinality = HistoryOnly
PKTypeAttribute/Description = The time interval between each timestamp update in the -PropertyStream-.0x000D0x000A0x000D0x000A(See also -TimestampResolution- concept in -ARCEvent-.-UtilEvent-.)0x000D0x000A0x000D0x000AUsed by -AddTimestampAsRequired-.0x000D0x000A0x000D0x000AOnly relevant for -CoreDB- (there should only be one source of timestamps in the system).0x000D0x000A(If this value is present, then -StreamProcessor- will insert timestamps at the specified interval).0x000D0x000A0x000D0x000ABackground: The -PropertyStream- principle lends itself well to keeping historical track of changes in your database. A method for timestamping the updates is therefore also natural to include.0x000D0x000A0x000D0x000ABut, by default, timestamps are not stored with each -PropertyStream--line. (you might have expected each property stream line to start with a timestamp like '2020-04-26 11:02:37' but that is not the case.)0x000D0x000A0x000D0x000AInstead, timestamps are inserted at regular intervals in the stream as Timestamp = 0x005Byyyy-MM-dd HH:mm ...0x005D. This is a practical approach reflecting the fact that consecutive timestamps will often be identical anyway and therefore just taking up space.0x000D0x000A0x000D0x000ANote that if this value is not set at all, then neither will timestamps be inserted into the -PropertyStream-.0x000D0x000A0x000D0x000AThe higher value chosen, the less space timestamps will take up in storage and transfer.0x000D0x000A0x000D0x000ASet to the highest value acceptable according to your time-resolution needs. If you have a need for a one-minute accuracy for timestamps, set this value to 1 minute.0x000D0x000A0x000D0x000AIf you want the highest possible resolution for when properties are created (down to the millisecond), set a resolution of one millisecond (ticks are not supported).0x000D0x000A
PKTypeAttribute/EnumMember = TimestampResolution
PKTypeAttribute/EnumType = StreamProcessorP
PKTypeAttribute/IsObligatory = False
PKTypeAttribute/LongDescription = Properties for which we want to store in-memory a -Created-, / -Invalid- field or similar are given the latest timestamp value found.
PKTypeAttribute/Type = TimeSpan

Edit single sub keys only: Description / LongDescription / PKTypeAttribute

Generated 2025-09-15 13:18:06.208 UTC