Anyway, this still doesn't solve the initial problem I am having. Is there any way to dynamically add a class mapping at runtime, post BuildSessionFactory()? I'm looking at removing as many mappings as possible for non-critical tables. The non-critical tables can be retrieved using an ISqlQuery and using Transformers.Transform.AliasToBean<T> to properly map the data to their domain object. That works great. The issue now is updating these rarely used tables. I'd like a way to be able to add a mapping so can call session.Save() or session.Update(). Is there any remote way to do this that doesn't incur a terrible performance hit? Thanks.
More testing in EF4 revealed that in the end it uses about the same memory, just allocates it in different ways at different times. On May 17, 11:56 am, Jason Meckley <[email protected]> wrote: > changing data access strategies is highly unlikely. it's a completely > technical problem so only devs care about it, not business persons. Not to > mention dumbing down data access to the lowest common denominator will hurt > the design and ability to performance tune the system; rather than improve > it. > > this type of encapsulation is foolish and doesn't provide any real value. -- 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.
