Remove references to population and population (combined)

[wemod123]

Ninja Edit by @derrickmehaffy

We need to remove all information about being able to paginate relationships, as it's not possible and will not be implemented per Alex in #752 (comment)

Can not implement Combining Population With Pagination

Following this document, to implement pagination in population, it should work, for example:

const qs = require('qs');
const query = qs.stringify({
  fields: ['title', 'slug'],
  populate: {
    comments: {
      fields: ['name'],
      pagination: {
          start: 50,
          limit: 200
      }
    },
  },
}, {
  encodeValuesOnly: true,
});

await request(`/api/articles?${query}`);

But it not work as expected

Steps to reproduce the behavior

1. As described above, implement pagination in API call
2. API response not respect to pagination in population

Expected behavior

If the document is correct, pagination in population should work.

If this is not designed to be work in this way, the document should be modified to reflect what had been designed.

System

• Node.js version: v14
• Strapi version: v4.0.7"
• Database: pg
• Operating system: windows

[derrickmehaffy]

@alexandrebodin correct me if I'm wrong but we can't do this due the performance hit on how we generate joins right?

[alexandrebodin]

Yes the doc is wrong this is not supported. Adding pagination would result in running one query per entry to get accurate pagination.

[derrickmehaffy]

I'll transfer this over to the documentation repo then to be fixed as a bug. @wemod123 we will not be able to add this as from a technical perspective it's simply not possible.

[wemod123]

@derrickmehaffy, Thank you for confirmation, this is a SQL limitation having it's rule, and here good to defined clear bound to avoiding misunderstanding in docs.