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.

Sign up for GitHub

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

Jump to bottom

Subselect fetching with setFirstResult/setMaxResults is broken #710

Closed
beikov opened this issue Dec 19, 2018 · 0 comments · Fixed by #700
Closed

Subselect fetching with setFirstResult/setMaxResults is broken #710

beikov opened this issue Dec 19, 2018 · 0 comments · Fixed by #700
Assignees
@beikov
Labels
component: entity-view kind: bug

Comments

@beikov
Copy link
Member

beikov commented Dec 19, 2018

Description

When using setFirstResult/setMaxResults for a view that subselect fetches some data, we currently copy over the values to the subselect query which is wrong. Note that this also means that we have to handle cases where we receive elements that do not have matching correlation values.

Expected behavior

Actual behavior

Steps to reproduce

Environment

Version: 1.3.0
JPA-Provider:
DBMS:
Application Server:
@beikov beikov self-assigned this Dec 19, 2018
beikov added a commit to beikov/blaze-persistence that referenced this issue Dec 19, 2018
@beikov
[Blazebit#710] Don't copy max results and first result to subselect f…
5582fad 
…etched query in entity views
@beikov beikov mentioned this issue Dec 19, 2018
Merged
beikov added a commit to beikov/blaze-persistence that referenced this issue Jan 11, 2019
@beikov
[Blazebit#710] Don't copy max results and first result to subselect f…
5961fee 
…etched query in entity views
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@beikov beikov

Labels
component: entity-view kind: bug
Projects
None yet
Milestone
No milestone
1 participant
@beikov