Repro case for scoped findAndCountAll failure #253
+66
−28
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.
I have two models (in the example,
FooModel
andOtherModel
).FooModel
has ahasMany
association withOtherModel
, with a scope that references an aliased column (i.e. a DB column with a different name from the model attribute).Selecting
FooModel
instances usingfindAll
and includingOtherModel
works as expected. However, when usingfindAndCountAll
, invalid SQL is generated, because the column alias is not resolved, and the query fails with an error: