Pet peeve: why is the common term "n+1 query problem" when it's the 1 that happens first and the n that is the problem?
As a pedant, I've been referring to it as a "1+n" problem, but haven't managed to make it catch on yet!
As a pedant, I've been referring to it as a "1+n" problem, but haven't managed to make it catch on yet!
Also "n+1" looks more like a reference to concurrency/synchronization throughput - like, n concurrent threads or requests where the results are collected and used together. I was really confused the first few times I saw "n+1" because of that.
It looks like this page in the SQLite docs has had the "n+1" terminology for as long as it's been on the internet archive (2016): https://web.archive.org/web/20161112021608/https://www.sqlit...
Usually it's doing one query that returns n results, then doing one more query for each result. Therefore, you end up having done 1+n queries. If you'd used a join you could potentially have done only 1 query.