Add DateTimeOffset support
The DocumentDb engine should be able to recognize and properly order DateTimeOffset serialized fields.
Work on this feature is now started. Will update when this is released.
Christian Lykke commented
Any updates on this issue?
Any updates on the this feature? Quite surprise that we did not have `DateTimeOffset` support for so long.
Sander Saares commented
It took me a minute to understand what exactly was missing here - looks like Cosmos treats DateTimeOffset as just a string, which means that timezones are completely ignored in any ordering logic! So events from different timezones are in the wrong order.
This would be extremely helpful. We have to use DateTimeOffset for proper date handling and display throughout our application and SQL Server does it quite well. But I want to move part of our application over to Cosmos DB and can't do it until there is support for DTO.
`DateTime` is not a proper type to handle ISO8601 datetime. It must be a `DateTimeOffset` type.