DateTime strange UTC(?) offsetting between inserting and selecting

I have such data model:

public class MyObject
{
        [BsonId]
        public long Id { get; set; }

        [JsonConverter(typeof(Iso8601DateTimeConverter))]
        public DateTime? DueTo { get; set; }
}

This DateTimeConverter, is:

public class Iso8601DateTimeConverter : IsoDateTimeConverter
    {
        public override void WriteJson(JsonWriter writer, object value, JsonSerializer serializer)
        {
            var dateTime = (DateTime)value;
            serializer.Serialize(writer, dateTime.ToString("yyyy-MM-ddTHH:mm:ssZ"));
        }
    }

When data comes from API, it’s like in below example:

{
    "Id": 98,
    "DueTo": "2014-01-01T06:00:00Z"
}

From code perspective, DueTo field is 2014-01-01 at 06:00 AM.

But when I’m inserting/upserting data into LiteDB, it’s beeing converted into 2014-01-01 at 07:00 AM - data format is not the problem here, but the strange offset.

The question is why? When I’ve looked into my_db_file.db, inside it’s 2014-01-01 07:00:00.000 string.

What can I do, to ommit data inconsistency between inserting and selecting DateTime in LiteDB? Is there any special BSON attribute to be set?

[BennieCopeland]

Perhaps instead, store the Kind as well? I just got bitten by this myself. In my application the dates are all Kind=UTC. I was trying to compare Newtonsoft JSON deserialized event message data by value with what I was getting back from LiteDB, and they were not matching up like I expected.

[mbdavid]

Hi @Szymaniuk, yes. By default, BSON deserialization keeps DateTime as Kind=Local to be compatible. If you want work with UTC, you must define in connection string (or if you use LiteEngine you can specify in ctor).