So, when I use custom SQL and I join to an entity say "Address"... if no Address is found NHibernate is going and making a second sql call for the Address, and hence I'm ending up with an N+1 SELECT problem.
An example of this problem is here; http://bit.ly/4boQqN But I can summarize: It really sucks to break into custom sql for performance only to have an N+1 SELECT problem :( --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
