Hi guys,

Hibernate seem to systematically "detect" my nullable int columns as dirty and updates them to "0".... [not-null="false"] in mapping doesn't seem to change this behaviour.
For ex:
I have a SQL server column [Rating] [int] NULL.
I have a class with:

My mapping file goes like: <property name="rating" column= "rating" not-null="false" />
And yet, for all cases WHERE [Rating] is NULL - I get: NHibernate.Persister.AbstractEntityPersister - d001.Blahblah.Class1.rating is dirty...
Am I missing something here?
Many thanks

Currently NHibernate requires using a nullable type for nullable integers (from Nullables library of NHibernateContrib package). Or you can write your own UserType that will save 0 as NULL. Search the Wiki for Nullables, there was a usage example there somewhere.

Here is the example using Nullables:
http://wiki.nhibernate.org/display/NHC/Nullables

Thanks guys!