Hi Fabio, On Fri, Apr 22, 2011 at 3:31 PM, Fabio Maulo <[email protected]> wrote: > Now try to say me that this, and your reported issue, is a bug in NH and not > a completely confusion in your system.
I understand your points, but disagree that it's not a bug. Quoting: http://www.nhforge.org/doc/nh/en/index.html#mapping-declaration-version """ Version numbers may be of type Int64, Int32, Int16, Ticks, Timestamp, or TimeSpan (or their nullable counterparts in .NET 2.0). """ This statement is incorrect, because a nullable version property doesn't work at all, as my test case demonstrates. There is really no miracle needed. It's a pretty easy fix. The only problem that I see is that the <version/> XML should be updated so that it supports not-null="false". If you don't want to call it a bug, fine. It's at least an enhancement to support nullable version columns. Mike
