In FNH, it would be a .JoinedSubClass("columnName",x=>
x.YourSubClassMappingHere);
Although as a point of contention, one of the reasons why the table per
class hierarchy is default, is because it's the easiest to use in the
database, and it's also the best performing option. Having done a fairly
complex system using both ways, the table per class hierarchy is far better
performing.2009/6/16 Łukasz Podolak <lukasz.podo...@gmail.com> > > By default, the inheritance mapping is "table per class hierarchy". I > have a "DictionaryBase" class and couple of derived classes from it. > How can I tell fnh to map all my derived classes as single tables and > not to map DictionaryBase at all ? Can be fluent or automapping, > whichever gets job done. For now I can only accomplish such mapppings > when my concrete dictionary classes .. do not inherit from base, but I > wouldn't like it to live this way. > > I'm using SharpArch's defaults if this is any prompt. > thanks for any help > > Łukasz > > > -- - Hudson http://www.bestguesstheory.com http://twitter.com/HudsonAkridge --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To post to this group, send email to fluent-nhibernate@googlegroups.com To unsubscribe from this group, send email to fluent-nhibernate+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/fluent-nhibernate?hl=en -~----------~----~----~----~------~----~------~--~---
