Usually this is due to bad mapping, but any of the new LINQ stuff only digs 3 levels deep in the object graph that I've seen (though this may be configurable). I wouldn't consider this to be a bug as much as a design decision but one of the devs could probably answer that better.
On Jun 12, 9:43 pm, "Yoann. B" <[email protected]> wrote: > Hi, > > Why QueryOver.Where only works on one objet level path ? > > Here is my query : > > var query = Session.QueryOver<Suggest>() > .Where(p => p.Profile.Customer.CustomerId == > customerId) > .Where(p => p.Job.Customer.CustomerId != customerId); > > var total = query.RowCount(); > > return total; > > I've got an exception : "could not resolve property : > Profile.Customer.CustomerId" and "could not resolve property : > Job.Customer.CustomerId" > > Using the LINQ Provider it works. > > Am i wrong with the QueryOver API ? > > Thanks. -- 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.
