I add an int Version Column / Property to a class. The version number of objects was incremented when object updated and also where selected by a query. I think this is in contradiction with Optimistic-Locking method. So when an object was read, an other previously readed operation must can update the object.
How can i resolve this?

This often happens when you have a field that is NULL and it is mapped to a property that can't be null (such as int, DateTime, etc.). When such a field is loaded the property is initalized to its default value (which is not null) and this default value is then saved, that's why the version is incremented.

The solution is usually to use Nullables from the NHibernateContrib package for such properties.

Of course the problem may be somewhere else entirely, so please provide more details (your mappings, your classes, your code) if I guessed wrong.

hi,

I' ve a similar problem.

I've got a class Customer with a lazy collection of Addresses. The Address class has a many-to-one relation with Country class.

If I load a Customer object, without initialize the Addresses collection and then I load all Country objects, the Customer version changes. When I load the countries list first It doesn't hapen. Any suggestion?

I found that xml property types must completely match to class property types. for example Int32 matches int.