1) The API is incredibly error prone. To the extent that even today EF6 Core can do random things to your dates if you’re not careful. 2) It’s the wrong model

1) The API is incredibly error prone. To the extent that even today EF6 Core can do random things to your dates if you’re not careful. 2) It’s the wrong model for representing dates and times so you end up with stuff like the midnight convention (which would be fine if it wasn’t for point 1) In short: in 99 instances out of 100, you would be better off using DateTimeOffset, DateOnly or TimeOnly.