search

symphonists / uniondatasource

A union datasources allows you to combine multiple datasources to output a single datasource for the primary purpose of a unified pagination.
13 stars 11 forks source link

Number of Entries #29

Closed designermonkey closed 11 years ago

designermonkey commented 11 years ago

I have set each datasource that I am attaching to be limited to 25 entries each sorted by random, and I have 4 datasources. This is because I need a maximum of 100 entries, but spread evenly over all 4 datasources.

Currently, only 2 of the datasources have entries, so I would expect to see only 50 entries being returned by the union DS, yet all of the entries from both sections are returned.

If I set the union DS to limit, then it limits, but I was under the impression that it would respect the limits set by each attached DS?

brendo commented 11 years ago

No actually, the limit for each is governed by the UNION datasource.

designermonkey commented 11 years ago

Damn. I honestly thought it took the union of the results of the other DSs. Is thee any way to get it to do that, or is it a massive headache in SQL?

brendo commented 11 years ago

To me, that is the reason the UnionDatasource was created, to avoid that situation. When you are trying to combine chronological content, you don't necessary want 25 of each. You want the most recent 25 of the combined result.

If you wanted 25 of the most recent from each datasource, then I would just use the 4 datasources individually and combine them in XSLT.

designermonkey commented 11 years ago

Yeah, I can see that. The use case was to have 25 of each of the latest entries, then randomise the 100 together. I just wanted to try and do it before xslt as random sorting isn't easy.

I've done it now though.