Fix Version/s: None
This query is non-chunked so the QuerySession.needMerge flag should be set to false
(grep ticket number in core/ to get the unit test where this issue appear)
- mentioned in
According to Nate Pease [X], in the current design, all queries have a merge step (e.g. to accommodate column renaming). This suggested optimization is no longer relevant.