Changes to the AbtTimestamp class
Reason for change
AbtTimestamp, our perennial problem-child, has undergone yet another class shape change to alleviate a serious performance problem.
Change
The 2 instance methods timestampValue and timestampValue:, which were categorized as AbtBase-Internal, were none the less used in some customer code. These methods have now been categorized as AbtBase-Deprecated. timestampValue is replaced by asMicroseconds; timestampValue: is replaced by the class method fromMicroseconds:. These 2 new methods are categorized as AbtBase-API and so should remain stable in the future.
The instance method milliseconds: is also now categorized as AbtBase-Deprecated without a direct replacement.
The behavior of the class method date:time:microseconds: has been changed to better align with the internal representation of AbtTimestamp. Previously the value of the microseconds: argument could range from 0 – 999999 and overrode the milliseconds portion of the time: argument. Now the valid range is 0 – 999 and it does not affect the milliseconds portion of the time: argument.
Action required
If you want to set the milliseconds portion of a timestamp, use code similar to the following:
anAbtTimestamp time milliseconds: anInteger
Since the methods categorized as AbtBase-Deprecated may be removed from the product in some future release, you should consider changing your code so that these methods are not used.
Last modified date: 07/02/2019