Ok i will try it. If both SchemaVerify and this are work, i think the following workflow could prevent the ghosting.
* I create a Test which runs SchemaVerify. * SchemaVerify tells me that i could run into ghosting with the current mapping. * I change the mapping with the property * SchemaVerify passes Fabio Maulo schrieb: > 2008/11/13 Steve Wagner <[EMAIL PROTECTED]> > >> Wouldn't it here a good suggestion to add an per property option which >> forces nhibernate to eval DBNull.Value==default(T) if it dose a dirty >> check? >> > > I think we have it working. In meta-data we having DefaultValue exactly for > that.mmm wait ... sometimes you are talking about a new feature for existing > data where you don't want to change the existing record even if you have a > value in the entity and a null in the DB. > Do you can create a failing test for the new feature ? >
