Skip to main content

EF Core - The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value

Athough EF Core is a developer friendly Object-Relational Mapper (ORM), working with it isn't without its challenges. One error that we encountered during a pair programming session was:

The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value

In this blog post, we will delve into the causes of this error and explore ways to resolve it.

"Constructing a database in the 18th century" - Generated by AI

Understanding the error

This error typically occurs when there is an attempt to convert a datetime2 value in SQL Server to a datetime value, and the value falls outside the valid range for the datetime data type.

  • datetime: This data type in SQL Server has a range from January 1, 1753, to December 31, 9999, with an accuracy of 3.33 milliseconds.
  • datetime2: This newer data type, introduced in SQL Server 2008, has a much broader range from January 1, 0001, to December 31, 9999, with an accuracy of 100 nanoseconds.

When EF Core tries to map a .NET DateTime to SQL Server’s datetime, any value outside the range of January 1, 1753, to December 31, 9999, will cause this conversion error.

Remark: Wondering why January 1, 1753? Read about the Gregorian calendar here.

Let’s fix it!

One reason that this error can occur is when your DateTime is set to DateTime.MinValue which is January 1, 0001. This value is valid for datetime2 but not for datetime, leading to the out-of-range error.

Initialize your DateTime properties with a value that is within the range of the SQL Server datetime type.(e.g. 1/1/1753).

Another solution is to use the datetime2 type explicitly in your EF Core model configurations to avoid range issues:

There is a third solution in case this error happens because you try to map a nullable database column to a non-nullable property. In that case you could change the property to make it nullable:

Remark: Instead of using a DateTime type consider using the DateOnly type when you only care about the Date part.

More information

What's New in EF Core 8 | Microsoft Learn

Entity Framework Core–DateOnly and TimeOnly (bartwullems.blogspot.com)

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more