> What I wanted to achieve was that I wanted to serialize "hourly rates" > as table-per-class-hierarcy strategy,
My mistake - on re-reading your first post, I now see you mentioned that explicitly. I must confess to a sort of "willful ignorance" about the actual tables that FNH maps for me. I usually take a quick look at the generated tables, and say "OK, I get it", but as long as the data in my object model is persisted properly, and there are no obvious performance problems, I'm happy with whatever it gives me. In your case, you are obviously going to extra effort to get a table- per-class-hierarchy. What are the advantages of this approach? -Tom -- You received this message because you are subscribed to the Google Groups "Fluent NHibernate" 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/fluent-nhibernate?hl=en.
