- 🇺🇸United States joecorall
This fix is in the latest release. Thanks for the patch!
Automatically closed - issue fixed for 2 weeks with no activity.
When retrieving records it's possible to get into situations where https://git.drupalcode.org/project/rest_oai_pmh/-/blob/dc118ef3b57937243... returns duplicate results as limit/offset chunking occurs without an order by clause.
For reference https://www.postgresql.org/docs/current/queries-limit.html
When using LIMIT, it is important to use an ORDER BY clause that constrains the result rows into a unique order. Otherwise you will get an unpredictable subset of the query’s rows. You might be asking for the tenth through twentieth rows, but tenth through twentieth in what ordering? The ordering is unknown, unless you specified ORDER BY.
While this is PostgreSQL specific documentation it also applies to MySQL.
Ingest n records such that the configured results to display for the resumption token requires paging.
Notice when using the resumption tokens records from previous chunks appear in the current result set.
Add a default order by to enforce a deterministic ordering.
Fixed
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This fix is in the latest release. Thanks for the patch!
Automatically closed - issue fixed for 2 weeks with no activity.