Fixing bug applying VALUES outside of a GROUP BY #2188
Merged
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.
Summary of changes
Altering order in which aggregate variable aliases are renamed to user-defined variable names to ensure that when defining a
VALUES
pattern outside of aGROUP BY
, the variables in the query are correctly joined to those defined in theVALUES
pattern.The change fixes the following bug...
Example of bug
results in the following erroneous output:
I would expect the the
VALUES
pattern to have filtered the results down to only include the result where?obj
ishttp://example.com/something
, i.e.:this is indeed the outcome when passing the data and query through the Apache JENA command line tools.
Checklist
the same change.
./examples
for new features.CHANGELOG.md
).so maintainers can fix minor issues and keep your PR up to date.