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
Currently we simply copy the base query for implementing the subselect strategy but this has some limitations. If the base query uses select aliases in the order by clause, it won't work because we strip off the select items although we should actually append only the necessary ones to the end of the query.
When a subview is correlated that contains collections, the use of limit and offset is broken currently when having a normal CriteriaBuilder. We should detect the use of collections somehow and convert the CriteriaBuilder to a PaginatedCriteriaBuilder via page() in that case.
The text was updated successfully, but these errors were encountered:
Currently we simply copy the base query for implementing the subselect strategy but this has some limitations. If the base query uses select aliases in the order by clause, it won't work because we strip off the select items although we should actually append only the necessary ones to the end of the query.
When a subview is correlated that contains collections, the use of limit and offset is broken currently when having a normal CriteriaBuilder. We should detect the use of collections somehow and convert the CriteriaBuilder to a PaginatedCriteriaBuilder via
page()
in that case.The text was updated successfully, but these errors were encountered: