Re: [fluent-nhib] Re: Discriminating sub classes with null values?

2010-01-10 Thread Paul Batum
c TypeBClassMap() { > >     HasMany(x=>x.Children); > >     } > > } > > > > > > From: fluent-nhibernate@googlegroups.com > [mailto:fluent-nhibern...@googlegroups.com] On Behalf Of Hudson Akridge > Sent: 04 January 2010 16:43 > To: fluent-nhibernate@go

RE: [fluent-nhib] Re: Discriminating sub classes with null values?

2010-01-04 Thread Martin Hornagold
HasMany(x=>x.Children); } } From: fluent-nhibernate@googlegroups.com [mailto:fluent-nhibern...@googlegroups.com] On Behalf Of Hudson Akridge Sent: 04 January 2010 16:43 To: fluent-nhibernate@googlegroups.com Subject: Re: [fluent-nhib] Re: Discriminating sub classes with null values

Re: [fluent-nhib] Re: Discriminating sub classes with null values?

2010-01-04 Thread Hudson Akridge
While you can *technically* do what you're looking for with a formula discriminator, that is, in my book, a horrid hack and like any "good" hack, will cause you unforseen problems down the road. What Paul is recommending is more of a state based function, and would be a better solution imo. Inheri

[fluent-nhib] Re: Discriminating sub classes with null values?

2010-01-04 Thread Boz
Thanks for responding Paul. I'm not sure I fully understand your response or whether I've phrased my question wrong. I see what you mean about not wanting to have objects in an invalid state at runtime, however wouldn't that always be the case for when you use DiscriminateSubClassesOnColumn? i.e