GollumSF / rest-bundle

100%

master: 100%

LAST BUILD ON BRANCH v4.2.1

branch: SELECT

CHANGE BRANCH

x

• No branch selected
• 2.5.0
• 2.8.0
• dependabot/composer/symfony/http-foundation-5.0.7
• dependabot/composer/symfony/http-kernel-5.1.5
• dependabot/composer/symfony/http-kernel-6.0.20
• dependabot/composer/symfony/security-bundle-6.0.20
• master
• sf-4.4
• v1.3.0
• v2.3.0
• v2.4.0
• v2.4.1
• v2.4.2
• v2.4.3
• v2.5.0
• v2.5.1
• v2.6.0
• v2.6.1
• v2.6.2
• v2.6.3
• v2.6.4
• v2.6.5
• v2.6.6
• v2.7.0
• v2.7.1
• v2.8.0
• v2.8.1
• v2.8.2
• v2.8.3
• v2.9.0
• v2.9.1
• v3.0.0
• v3.0.1
• v3.0.2
• v3.0.3
• v3.0.4
• v4.0.0
• v4.1.0
• v4.1.1
• v4.2.0
• v4.2.1
• v5.0.0

Build # 33255798261

Build Type

push

github

Committed by Smeagolworms4

Commit Message

Count and paginate correctly across a to-many join

Joining a to-many relation multiplies the SQL rows, which showed up twice.

The total counted rows instead of entities: on the test fixtures, 40 authors joined to
their books were counted 56 as soon as a query callback joined the collection. The count
is now taken DISTINCT.

The limit applied to those multiplied rows, so a page came back short: asking for 5
authors ordered by id returned 4, and whether it happened depended on where the duplicate
rows fell in the window. A path crossing a collection is now ordered on an aggregate of
the joined column, MIN ascending and MAX descending, grouped by the identifier of the root
entity, which removes the fan-out altogether.

Doctrine's Paginator would have fixed both, but it rewrites the query into subqueries and
falls over on a query callback that already grouped or made the query distinct. Adding an
aggregate only ever adds to the query builder, so existing callbacks keep working, and it
still takes two queries.

Ordering on a plain column or across a to-one relation is untouched.

Coverage Stats

31 of 31 new or added lines in 1 file covered. (100.0%)

1053 of 1053 relevant lines covered (100.0%)

30.38 hits per line