Vlad, I could do the same to fetch Employee entities as suggested, however, when I do this I see the memory issue as mentioned in this post. Each query fetch will retrieve nearly 20-30K results. As also, I have a requirement where the fetched Employee List will be iterated so that all the child entity objects will in turned be mapped to their respective DTO’s. So I thought I can refine the code so that I can still manage with one DTO.
shiva
7
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| QueryImpl consuming more memory | 2 | 934 | February 21, 2018 | |
| How to fix "org.hibernate.QueryException: query specified join fetching, but the owner of the fetched association was not present in the select list" | 8 | 35181 | November 29, 2021 | |
| Join fetch multiple entities fails - query specified join fetching, but the owner of the fetched association was not present in the select list | 3 | 4160 | May 18, 2021 | |
| How to resolve QueryException: query specified join fetching, but the owner of the fetched association was not present in the select list | 1 | 1399 | May 5, 2023 | |
| Problems with Join Fetch using Criteria API | 1 | 530 | December 17, 2024 |