Custom Selects with an additional order by or query constraint ar not working #57
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.
Hi Aaron,
thanks for this package! This has speed up our queries tremendously :)
We encountered a little inconvenience with custom selects used in order by or where clauses.
For example, if you have a query llike this:
or that
We get an error that the column doesn't exist. The problem here is, that the "Inner"-query is stripping away all the custom selects.
I added some failing tests in this PR so you can see this in action.
I think its for performance reasons because in most of the cases you only need the ids for the inner query.
What do you think, is there any possibility this gets fixed/added?
King regards
Markus