Yeah, but you have to go out of your way to do that. If you're in touch with the SQL you're executing at all, the join is the obvious easy way to do it, it's not some arcane optimization.
You do see it often in things like canned ecommerce software. They have this ecosystem that encourages you to add widgets to category listings, product listings, etc, that all create queries keying off the page context.
Where widgets might be "similar items", "people that bought x, bought y", "recent purchases of this widget", "best sellers in this category" and so on.
Re:LiteFS
by RussianCow on Wednesday September 21, 2022 @02:28PM
(#32929228)
That’s a really big “if”. In my experience, most application engineers aren’t very good at SQL because they don’t have to be; most apps just don't ever reach a scale where it matters, and something like Rails or Django with N+1 queries all over the place performs just fine.
Hence my 2 decade losing battle against ORM at every place I've worked :)
I'm, like, 1 for 10 maybe.
A for-loop in vanilla anything will do. Nothing special about PHP. Ruby, Python, Java, etc...
Of course. PHP is the one you will mainly encounter in the wilderness, though.
Most common place I saw N+1 is ActiveRecord (Ruby on Rails).
Because by default, no relationships are loaded and the way AR "loads" stuff makes is extremely easy to create N+M queries on 5 lines of ruby. Then, those people will tell you that you run out of database before you run out of ruby...
You definitely don't need an ORM to get to N+1 hell, a for-loop in vanilla PHP will do.