Description of problem:
The search results can have 15,30 or 45 rows per page. When changing that number, the parent column should be re-evaluated to check that all the resources on the new - larger - page are unique.
Steps to Reproduce:
1. With page size 15, find an odd-numbered page followed by an even-numbered page where one of them contains just a single parent and the other more than one parent in the parent column.
2. Change the page size to 30, navigate to the "same" page (i.e. if the found odd page was n-th in the original results, navigate to the (n + 1)/2 page in the results with page size 30).
3. Notice that the parents still look the same as they did for the smaller page size even though they all should contain more than one parent now.
Half of the results on the larger page size contain more than one parent, the other half doesn't
All rows on the larger page size should contain more than 1 parent.
Created attachment 406469 [details]
Odd page, size 15
Created attachment 406470 [details]
Even page, size 15
Created attachment 406472 [details]
Page, size 30
I think this has been fixed meanwhile?
This is no longer applicable.
In the meantime, we changed the implementation such that the ancestry of resources is precomputed, so we no longer suffer from the complexity and general brokenness of the previous approach.
Closing as this no longer is an issue.