Follow-up from @codex P2 on PR #173 (head bbf4b96), thread comment 3859937768.
CollectionEndpoints.cs:84 lists entries with sibling Include(Tags) + Include(Genres) executed as one joined query,
so each item materializes ~ tag_count × genre_count rows before EF de-duplicates. With up to 500 items this can be
disproportionately slow/memory-heavy.
Fix: use a split query (AsSplitQuery) or project the two collections separately.
Not a blocker for PR #173; filed as fast-follow.
Follow-up from @codex P2 on PR #173 (head bbf4b96), thread comment 3859937768.
CollectionEndpoints.cs:84 lists entries with sibling Include(Tags) + Include(Genres) executed as one joined query,
so each item materializes ~ tag_count × genre_count rows before EF de-duplicates. With up to 500 items this can be
disproportionately slow/memory-heavy.
Fix: use a split query (AsSplitQuery) or project the two collections separately.
Not a blocker for PR #173; filed as fast-follow.