-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
LimitSubqueryOutputWalker: fix aliasing of property in OrderBy from MappedSuperclass #1377
Conversation
Hello, thank you for creating this pull request. I have automatically opened an issue http://www.doctrine-project.org/jira/browse/DDC-3680 We use Jira to track the state of pull requests and the versions they got |
Thanks - i'll merge after nitpick 👍 |
I'm not sure if it's fixed properly. Is this enough? |
092f12e
to
e501137
Compare
@fprochazka I think so - though there's no functional test for this case... |
@zeroedin-bill now I'm thinking it might be better to reverse the condition and only change the alias if the entity is in inheritance and it's the type of inheritance where you use multiple tables. Because it still might break with STI. Somebody might wanna write tests for that. |
@fprochazka we need more functional test cases... |
Sure, there is never enough tests :) But I won't be able to write more right now. Soonest would be somewhere around monday and I can't promise that. |
@fprochazka For now I'll merge this. I'd really appreciate if you could write some functional tests on Monday to cover this scenario if you have time! Thanks! |
LimitSubqueryOutputWalker: fix aliasing of property in OrderBy from MappedSuperclass
I'll try! |
http://www.doctrine-project.org/jira/browse/DDC-3679