Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regression after returning ResultSet instead of SortedQueryResultSet #11489

Closed
ahmetmircik opened this issue Oct 2, 2017 · 2 comments
Closed

Regression after returning ResultSet instead of SortedQueryResultSet #11489

ahmetmircik opened this issue Oct 2, 2017 · 2 comments

Comments

@ahmetmircik
Copy link
Member

@ahmetmircik ahmetmircik commented Oct 2, 2017

First see this group question.

Problem occurs in getSortedQueryResultSet method:
When returned object is SortedQueryResultSet there is no problem but when it is ResultSet failure happens.

@ahmetmircik ahmetmircik added this to the 3.8.7 milestone Oct 2, 2017
@stevehu
Copy link

@stevehu stevehu commented Oct 3, 2017

@ahmetmircik Thanks for opening the issue here. I wasn't sure if it was an issue or just there is a new way to use the API.

@tombujok tombujok modified the milestones: 3.8.7, 3.9 Oct 6, 2017
@tombujok tombujok self-assigned this Oct 6, 2017
@tombujok
Copy link
Contributor

@tombujok tombujok commented Oct 6, 2017

Set milestone to 3.9, will back-port to 3.8.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

4 participants
You can’t perform that action at this time.