- Issue created by @leontin
- cac34fe9 committed on 1.0.x
Issue #3447393: Pager is not shown for pages having attached UNION to...
- cac34fe9 committed on 1.0.x
- πΊπΈUnited States gribnif
The problem with using UNION ALL is that it creates new rows for every row that each subquery has in common. So if the main query returns entity IDs (1,2,3,4) and the first UNION returns (2,3,5), the result set will be (1,2,3,4,2,3,5). While there might be a rare case where this is the desired result, it would break backward compatibility.
Instead, I have added a dummy HAVING clause so that the built-in query constructor won't try to remove the entity ID field from the UNION query. This fixes pagination.
I could see the argument for relying on the Distinct option in Query Settings to determine which behavior is used. But I wouldn't want to do this in a minor version because of the BC problem.
- Status changed to Fixed
6 months ago 4:14pm 29 May 2024 Automatically closed - issue fixed for 2 weeks with no activity.