You need to make this behavior opt-in, otherwise people will upgrade and 
possibly lose data because something may not be referenced in the model 
anymore (or perhaps multiple types mapped to same table returning different 
things). Entity framework is a two-step process and you can customize the 
migration, which mitigates this issue, but schema migration is not 
customizable and thus should not have this behavior enabled by default.

On Friday, July 11, 2014 8:33:01 AM UTC-6, Jeffrey Becker wrote:
>
> Ok, pull request is submitted.

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"nhibernate-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to