Right. A good ORM should deal with all your common cases (if not, your schema probably needs improving), and it saves you writing a lot of boilerplate code. Fo

Right. A good ORM should deal with all your common cases (if not, your schema probably needs improving), and it saves you writing a lot of boilerplate code. For the edge cases where you need complex joins and/or extra performance, don't try and bother with the ORM, just drop to SQL.