3 ms·
Yes. We have a bunch of n+1’s in our product, but they are in places where it literally does not matter. A single record getting pulled down, on a page deep in
by SkyPuncher 3y ago
Yes. We have a bunch of n+1’s in our product, but they are in places where it literally does not matter. A single record getting pulled down, on a page deep in a UX flow.
It’s not worth our time unless they work into pages with large data sets or core flows.
- Ensorceled 3y agoI have "ignore this n+1 warning" in a few places in our unit tests for exactly this reason (details page, so n will never be more than 1). But these don't cause a problem on any database. So, again, not sure how this is a win for SQLite.