Fix incorrect ordering of the events

[soujay]

• Resolves: Incorrect ordering of events in Dashboard and Events page #3921

Removes OrderingType.Double, with no value passed RavenDB 5.x defaults to lexicographic ordering:

When using RQL directly, if no ordering type is specified, then the server defaults to lexicographic ordering.

The document property on which is sorted is RaisedAt. This value is stored/interpreted as 2020-05-27T00:00:00.0000000Z. Using lexicographic ordering will work correctly with these values.

Symptoms

Incorrect order of events in ServicePulse events view.

Who's affected

ServiceControl 5 instances

Root cause

Incorrect OrderingType was passed to RavenDB query.

[ramonsmits]

I see that OrderingType.Double is removed. However, the RavenDB docs state:

When using RQL directly, if no ordering type is specified, then the server defaults to lexicographic ordering.

The document property on which is sorted is RaisedAt. If this is indeed lexicographic then it depends on the culture that RavenDB uses on how these timestamps are sorted.