Fixing SQL generation for queries selecting COUNT(DISTINCT...) w/ ORDER_BY #335
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #306, and PR #329 broke compatibility with a couple of queries we were using. Two regressions were introduced.
First, if the
COUNT(DISTINCT)had an alias applied to it, the alias would be used in thePARTITION BYvalue expression, which was invalid SQL, according to the Transact-SQL docs it cannot use aliases.Second, if the query (already having a COUNT(DISTINCT) and order clause) itself used a
selectcall like this:the outer select would lose some of the aliased columns due to the regex used when stripping out the aliases into
select_frags.Added a test to verify this, the issues are intertwined so it's just one test.
Thanks for the great gem!