Merged
Conversation
…h current element.
Applied fixes from StyleCI
Contributor
|
Seems good to me! I've also tested the examples in the section. |
There is probably a better way to do this, will fix when we face the problem.
…data into feature/fix-related-entity-aliases
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When related entity relies on the same table it is possible to run into problem when SQL is confused about which table to use.
To avoid this problem this PR introduces use of aliases in related entities. The related table alias does not have to be passed and it will be automatically deducted from field:
With this patch recursive models produce queries like this: