Perhaps this is ridiculously obvious, but how does one eagerly load a child collection in NHibernate, while paging based on the parent (the distinct root)? NHibernate’s paging arguments (skip, take) seem to be passed through to the joined records, which makes perfect sense but doesn’t really provide an object level paging option. I’m not interested in projecting into a flattened object.
So for example, let’s say that I want to select 20 teachers at a time but want their classes eagerly loaded (which for the sake of argument may result in 57 generated db rows on page one and 63 generated db rows on page 2). -- 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.
