CompositeEntityManager now allows for reversible queries #545
Conversation
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
…r.setReversed was not accessible via NativeQuery)
|
It will be super nice to do a order by desc query. Is this merged and available ? |
Author
|
as far as I know, no, still not merged :-/ On Thu, Jul 2, 2015 at 1:27 PM, Prashanth Raghavan <[email protected]
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
CompositeEntityManager.createNativeQuery() would create a new NativeQuery but with no option to change the ordering of the resultset in the underlying column range. I just made RangeBuilder.setReversed accessible via NativeQuery (which is currently only used within CompositeEntityManager)