Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 2
    What is the "N+1 problem"? I'm not familiar... Commented Dec 15, 2010 at 20:06
  • I think it's this: stackoverflow.com/questions/97197/… Commented Dec 15, 2010 at 21:05
  • 2
    Not sure I agree. A good ORM should let you execute raw SQL when necessary, and N+1 issues are generally rookie mistakes (e.g. nested loops over lazy-loaded collections) that can be easily avoided. Commented Dec 15, 2010 at 23:52
  • @richeym: Those where the first things that popped into my mind. The other answer have my back though. The point being is an ORM is just a tool, there are cases where raw sql is preferred. Commented Dec 16, 2010 at 11:58