You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lets elaborate with a simple example using entities defined in the library : Organizations?$top=0&$expand=Roles
This will deterministically return empty results when query.execute() is performed on the core entity. Currently, there is no check in JPANavigationRequestProcessor class to verify if the core entity result set is empty before proceeding with triggering the subsequent queries on the associated collections of the core entity or the expanded entity. This results in unnecessary computation on the server side since the overall result is always empty.
The text was updated successfully, but these errors were encountered:
dbhandari555
changed the title
The queries on expanded entities/collections are triggered despite the core entity results being empty
The queries on expanded entities/collections are triggered despite the core entity result being empty
Nov 11, 2024
Lets elaborate with a simple example using entities defined in the library :
Organizations?$top=0&$expand=Roles
This will deterministically return empty results when query.execute() is performed on the core entity. Currently, there is no check in JPANavigationRequestProcessor class to verify if the core entity result set is empty before proceeding with triggering the subsequent queries on the associated collections of the core entity or the expanded entity. This results in unnecessary computation on the server side since the overall result is always empty.
The text was updated successfully, but these errors were encountered: