| ▲ | 9rx 5 hours ago | |||||||
> I don't see how anyone would design a system that executes 200 queries per page. They call it the n+1 problem. 200 queries is the theoretically correct approach, but due to high network latency of networked DMBSes you have to hack around it. But if the overhead is low, like when using SQLite, then you would not introduce hacks in the first place. The parent is saying that if you correctly design your application, but then move to system that requires hacks to deal with its real-world shortcomings, that you won't be prepared. Although I think that's a major overstatement. If you have correctly designed the rest of your application too, introducing the necessary hacks into a couple of isolated places is really not a big deal at all. | ||||||||
| ▲ | PaulHoule 4 hours ago | parent [-] | |||||||
I'd point to the difference between vector-based vs scalar-based systems in numerics. If your web programming language is more like MATLAB or APL than PHP than maybe it can naturally generate the code to do it all with sets. As it is we are usually writing set-based implementations in scalar-based languages. Part of the "object-relational mapping" problem has always been that SQL is superior to conventional programming languages in many ways. | ||||||||
| ||||||||