Extended documentation to prevent exception when ordering on fetch joined to-many association #128
Conversation
This file contains 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
…ined to-many association
pilot
added a commit
that referenced
this pull request
Jun 24, 2015
…joined_to_many Extended documentation to prevent exception when ordering on fetch joined to-many association
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.
I got this exception on sorting: "Cannot select distinct identifiers from query with LIMIT and ORDER BY on a column from a fetch joined to-many association. Use output walkers." and it took me hours to find out, what the reason was and that the
Paginatoroptionwrap-queriesmust be used to use a subquery for distinct select, which prevents this exception.So I'd like to extend the documentation of that option to help others with the same issue (also mentioned in KnpLabs/KnpPaginatorBundle#106).