Oops!!! - I overlooked your addition "Not.Nullable()". It might force Criteria to optimize the join to an inner, whereas Linq (at this time) definitely does not do this. But if the pointer is not nullable anyway, there should not be any difference between an inner and an outer join - would you agree? So then there is no bug. Or is your database highly performance sensitive to outer joins? Or do you use "dangling pointers" - i.e., the column itself is not- null, but the target values in the Broker table need not exist? ... then, I fear, you are at a boundary case of the Linq provider - and adding that p.Broker != null still might not help (but p.Broker.BrokerId != null should).
Regards Harald -- 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.
