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

Fetch after Select applies to wrong entity #3356

Open
bahusoid opened this issue Jul 11, 2023 · 4 comments · Fixed by #3392
Open

Fetch after Select applies to wrong entity #3356

bahusoid opened this issue Jul 11, 2023 · 4 comments · Fixed by #3392

Comments

@bahusoid
Copy link
Member

bahusoid commented Jul 11, 2023

See FetchAfterSelect test case added with GH3352 test case.

Query source is wrongly detected and fetch is applied to main entity instead of selected.

@hazzik
Copy link
Member

hazzik commented Jul 11, 2023

var selector = ((StreamedSequenceInfo) queryModelVisitor.PreviousEvaluationType).ItemExpression;
var querySource = QuerySourceExtractor.GetQuerySource(selector); // QuerySourceExtractor is a subclass of Joiner

However, even if query source is extracted correctly test does not pass because the Component property is still uninitialized after the query.

@bahusoid
Copy link
Member Author

bahusoid commented Jul 11, 2023

Yeah. Later wrong HQL node is used for applying property fetch. I already have a WIP fix for this issue.

bahusoid added a commit that referenced this issue Aug 4, 2023
Partial fix of #3356

Fix wrong hql From node detection logic. Query source detection is still broken.
@hazzik

This comment was marked as resolved.

@hazzik hazzik reopened this Aug 4, 2023
@bahusoid

This comment was marked as resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants