Skip to main content

NHibernate: DateTime support

By default, if you load a datetime value from the database through NHibernate, the DateTimeKind will be set to ‘Unspecified’. For a specific requirement on a recent project, the DateTimeKind needed to be set to ‘Local’ instead.
So I dived into NHibernate to discover a rich set of Date/Time related functionality. Let’s create a simple object:
public class SampleEntity 
{    
 public DateTimeEntity() 
 {        
  CreatedOn = DateTime.Now;    
 }     

 public virtual Guid Id { get; private set; }    
 public virtual DateTime CreatedOn { get; set; }
}

If we save this entity to the database and load it again, we see there’s a difference:

Original entity:
Id: 9245fe4a-d402-451c-b9ed-9c1a04247482
CreatedOn: 2012-04-08 11:57:22 PM (Local)

Reloaded entity:
Id: 9245fe4a-d402-451c-b9ed-9c1a04247482
CreatedOn: 2012-04-08 11:57:22 PM (Unspecified)

When creating the entity, we initialized the CreatedOn property with DateTime.Now.(This is always the local time.) After saving and reloading the object to the database, the DateTimeKind is changed to ‘Unspecified’. This is because the database does not store whether the DateTime value is Local or UTC. NHibernate has no way of knowing which one it is, hence Unspecified.

To solve this NHibernate 3 includes two new DbTypes. In our mapping file, we can specify one of the following types:


<property name="CreatedOn" type="LocalDateTime"/>
<property name="CreatedOn" type="UtcDateTime"/>

By doing this we are explicitly telling NHibernate whether the database stores Local or UTC times.
For more information I recommend this blogpost by James Kovacs.
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