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
Implemented several more changes requested during the pull request review #69
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with suggestions of std::make_shared
src/engine/QueryPlanner.cpp
Outdated
// Create a group by operation to determine on which columns the input | ||
// needs to be sorted | ||
SubtreePlan groupByPlan(_qec); | ||
std::shared_ptr<Operation> groupBy( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could use std::make_shared
src/engine/QueryPlanner.cpp
Outdated
final._qet->resultSortedOn() == sortColumns[0].first)) { | ||
// Create an order by operation as required by the group by | ||
std::shared_ptr<Operation> orderBy( | ||
new OrderBy(_qec, final._qet, sortColumns)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
std::make_shared
Looking at builds all day I noticed we still get some compiler warnings in GTests. Somehow I (mis-)remember that this warning was fixed by one of your changes!? Maybe we could fix it in this PR either way. |
…ning. There was a missing 'break' in Filter.cpp that created a implicit fallthrough warning.
On Travis CI I still see one more simple compiler warning that can be fixed by doing |
The pattern trick check ignored the DISTINCT keyword in the alias which leads to false results.
Several of the changes requested during the review of the grouping pull request were not yet pushed upstream, as the problem with integers internally being stored as floats was not yet resolved.