On 27 Jan, 15:04, Tim <[email protected]> wrote: > Hello: I've seen a sporadic problem recently where a child collection > mapped as a <set> is not fully populated. > > This is an order-details scenario where I'm doing a big select to > return an order header and all of its order items. When NHibernate > packages up the order and details, the details collection will be > missing a contiguous sequence of items at the "end" of the collection, > i.e., if there are 14 order items in the database, only the first 10 > may be present in the collection. This seems random. I can't see a > pattern. But we'll process hundreds of orders over a 2-3 week period, > then this will happen once! Does this sound totally crazy? I can > post more details (mappings, etc.) but was hoping this description > would strike a chord with someone out there. Thanks for reading.
I am a newbie, so I don't know that much. But I'm just wondering if this could be a concurrency problem. Are you sure you're correctly dealing with concurrency? Is there some interesting information from NHibernate log? Daniel -- 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.
