code
If your collection has millions of rows, you are doing it all wrong.
code

Not the collection, of course! I meant millions of rows in the entity table, that cannot be efficiently skip/limited with JOIN-fetch. Unless using Window Function (great article!) but let's admit an approach like this it's hardly generalizable and should be treated class-by-class without a proper API.

The other problem is fetching multiple collections in the same graph.

P.S. Of course my suggestion to respect `@Fetch` annotation is totally opinionated, I'd obviously prefer an implicit solution without it!