Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DDC-3336 - undefined property with paginator walker and scalar expression in ORDER BY clause #1210

Conversation

Ocramius
Copy link
Member

@Ocramius Ocramius commented Dec 5, 2014

@doctrinebot
Copy link

Hello,

thank you for creating this pull request. I have automatically opened an issue
on our Jira Bug Tracker for you. See the issue link:

http://www.doctrine-project.org/jira/browse/DDC-3433

We use Jira to track the state of pull requests and the versions they got
included in.

@Ocramius
Copy link
Member Author

Ocramius commented Dec 5, 2014

Needs to also be merged back into the 2.4 branch.

@Ocramius
Copy link
Member Author

Ocramius commented Dec 5, 2014

Requires an additional test about hidden properties as well.

guilhermeblanco added a commit that referenced this pull request Dec 5, 2014
…erty-with-paginator-and-scalar-expression-select

DDC-3336 - undefined property with paginator walker and scalar expression in ORDER BY clause
@guilhermeblanco guilhermeblanco merged commit a6cf714 into doctrine:master Dec 5, 2014
@Ocramius Ocramius deleted the hotfix/DDC-3336-undefined-property-with-paginator-and-scalar-expression-select branch December 5, 2014 15:43
Ocramius added a commit that referenced this pull request Dec 5, 2014
…r-walkers-with-scalar-expressions-in-order-by-clause' into 2.4

Close #1210
@Ocramius
Copy link
Member Author

Ocramius commented Dec 5, 2014

Merged!

master: a6cf714
2.4: c398f8c

@stof
Copy link
Member

stof commented Dec 5, 2014

@Ocramius this probably also needs merging into the 2.5 branch (master is now 2.6)

@Ocramius
Copy link
Member Author

Ocramius commented Dec 5, 2014

Ah, scratch that: I'll probably kill the 2.5 branch entirely and tag from master once we are ready, then create the 2.5 branch.

@stof
Copy link
Member

stof commented Dec 5, 2014

@Ocramius yeah, makes sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants