So are you using auto mapping? Make your special property virtual (remember you can make it protected internal virtual if that's better), then make an automapping override class. In the override class, specify map.Ignore(x => x.s2).
Or write an explicit class map, and just don't tell nh about that property. On Jun 4, 2014 2:12 AM, "Marco Giacinti" <marco.giaci...@gmail.com> wrote: > Well, I was just posting an example of what I'd want to achieve. >> > My goal is to have classes having both properties that must be persisted >> on db (so, they contains model) and other ones used in the app without the >> need of complex derived classes that make the code hard to maintain... >> > -- > You received this message because you are subscribed to the Google Groups > "Fluent NHibernate" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to fluent-nhibernate+unsubscr...@googlegroups.com. > To post to this group, send email to fluent-nhibernate@googlegroups.com. > Visit this group at http://groups.google.com/group/fluent-nhibernate. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To unsubscribe from this group and stop receiving emails from it, send an email to fluent-nhibernate+unsubscr...@googlegroups.com. To post to this group, send email to fluent-nhibernate@googlegroups.com. Visit this group at http://groups.google.com/group/fluent-nhibernate. For more options, visit https://groups.google.com/d/optout.
