Data loss during pagination on several entities #181
Description
Tested with Mintaka 0.6.0
When requesting temporal data on several entities, for example by using idPattern=xxx or type=xxx, if the number of returned temporal instances is higher than the pagination limit, then Mintaka returns the exact same number of temporal instances for each entity, and the end-date provided in the content-range header is correct for only one of the entities. This results to missing data : some data that should have been returned in the next pas is never returned.
Example:
I use the following query:
/temporal/entities?idPattern=urn:ObservationPoint:PeopleFlow&timeproperty=modifiedAt&timerel=after&timeAt=2022-07-01T04:38:00Z
Mintaka returns 2 entities (let's say EntityA and EntityB), with 50 emporal instances for each one.
And the following response header: content-range: date-time 2020-01-01T00:00-2022-07-01T10:00
This date (2022-07-01T10:00) is correct for EntityA, but for EntityB Mintaka has returned data until 2022-07-01T04:38:25Z, while there is actually exisiting data between 2022-07-01T04:38:25Z and 2022-07-01T10:00 for EntityB (that will of course not be retured in the next page of data).