Why are the classes a workaround? Are you designing a domain model or a database?
On Thu, Aug 19, 2010 at 8:29 PM, Miha V <miha.valen...@gmail.com> wrote: > Well, > > it "feels" weird to have many tables basically for the same type of > data. The derived classes are already a workaround if you ask me, and > when you do reporting (directly with SQL), it is easier to understand > what's going on and also easier to write reports against such model. > Because derived classes don't introduce new fields or anything into > the picture, you're basically just saving extra data for NHibernate to > figure out what goes into specific collection. > > rgds, > Miha. > > On Aug 19, 4:47 pm, tbushell <tbush...@bic.com> wrote: > > > > 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 fluent-nhibern...@googlegroups.com. > To unsubscribe from this group, send email to > fluent-nhibernate+unsubscr...@googlegroups.com<fluent-nhibernate%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/fluent-nhibernate?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To post to this group, send email to fluent-nhibern...@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.
