DDC-3336: Undefined property: Doctrine\ORM\Query\AST\SimpleArithmeticExpression::$field

[doctrinebot]

Jira issue originally created by user darkangel:

I upgraded from 2.4.1 to 2.4.4, and now I'm seeing this notice here & there:

{quote}Undefined property: Doctrine\ORM\Query\AST\SimpleArithmeticExpression::$field in /*/vendor/doctrine/orm/lib/Doctrine/ORM/Tools/Pagination/LimitSubqueryOutputWalker.php on line 200{quote}

This seems to be in a method with the description "Generates new SQL for Postgresql or Oracle if necessary." ... but we're on MySQL (Percona).

[doctrinebot]

• depends on DDC-3433: [GH-1210] DDC-3336 - undefined property with paginator walker and scalar expression in ORDER BY clause
• relates to DDC-1958: pager produces wrong results on postgresql
• is referenced by DDC-3434: LimitSubqueryOutputWalker does not retain correct ORDER BY expression fields when dealing with HIDDEN sort fields

[doctrinebot]

Comment created by darkangel:

Changed this to critical. It's also screwing up ordering, for example:

SELECT tp, p, CASE WHEN tp.memberTo IS NULL THEN 1 ELSE 0 END AS HIDDEN ord FROM Tournaments*Model*TeamPlayer tp INNER JOIN tp.player p LEFT JOIN p.user u WHERE tp.team = ?1 ORDER BY ord DESC, tp.memberFrom ASC

The paginator doesn't order the data correctly unless I remove the 2nd order by (tp.memberFrom ASC). The generated SQL from the QB/DQL is correct, so the paginator must be messing something up.

See: http://www.doctrine-project.org/jira/browse/[DDC-1958](http://www.doctrine-project.org/jira/browse/DDC-1958)?focusedCommentId=24010&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-24010

[doctrinebot]

Comment created by @Ocramius:

Need a test case in order to verify the issue

[doctrinebot]

Comment created by darkangel:

Okay, try this:

        $qb->from('Team', 't')
              ->select('t')
              ->orderBy('(1-1000)*1', 'DESC')
              ->getQuery()
              ->getResult();

This is simplified, the actual query works with field values, like this:

        ->orderBy('(((t.eloRating-1000)*t.reliability) + 1000)', 'DESC')

This causes the first issue.

[doctrinebot]

Comment created by darkangel:

The second issue is explained by Guilherme Santos.

[doctrinebot]

Comment created by @Ocramius:

The first comment goes to a new issue.

[doctrinebot]

Comment created by @Ocramius:

Moved that issue to DDC-3434

[doctrinebot]

Issue was closed with resolution "Fixed"

[doctrinebot]

Comment created by @doctrinebot:

A related Github Pull-Request [GH-1211] was closed:
#1211

[doctrinebot]

Comment created by @doctrinebot:

A related Github Pull-Request [GH-1211] was assigned:
#1211