You can use formulas as discriminators as opposed to a column. You obviously have some sort of logic that determines the object type?
On Oct 22, 9:02 am, Brian Chavez <[email protected]> wrote: > Hello. > > Problem: > > I have 1 very large table of columns. > > I have a class hierarchy that represents different projections of the > columns of this table. > > For example: > > class A{ > AProperty{get;set;} //Mapped to ColumnA in Table 1 > > } > > class B : A { > BProperty{get;set;} //Mapped to ColumnB in Table 1 > > } > > class C : B { > CProperty{get;set;} > > } > > When I ask NHibernate to pull C, I expect to see C.AProperty, > C.BProperty, and C.CProperty. > > Essentially, this class hierarchy represents different scoped > projected views of the *same* table. > > How do I do this in hbm.xml mapping files without adding discriminator > values? > > I've tried to use multiple <union-subclass> attributes and map to the > same table, but NH throws an exception: > > --> NHibernate.DuplicateMappingException : Duplicate table mapping > Table 1 > > Any ideas? > > Thanks, > Brian -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
