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 a call to Query::with() is mandatory (see 7dc53f1) in order to be able to differentiate a column from being solely used in a filter or from being selected.
The call to with() here shouldn't be necessary, the call to columns should do so instantly. Instantly because with() does the same and it is required for any filter optimizations to work correctly.
At the moment relations of selected columns are only resolved in Query::assembleSelect(). This is too late and can't be assumed as an requirement for e.g. filter optimizations.
The text was updated successfully, but these errors were encountered:
While thinking about this, it is (maybe) related to the ability to postpone filter column qualification. If so, it's possibly obsolete because when filter column qualification can be postponed this might not be an issue anymore.
Currently a call to
Query::with()
is mandatory (see 7dc53f1) in order to be able to differentiate a column from being solely used in a filter or from being selected.Consider the following:
The call to
with()
here shouldn't be necessary, the call tocolumns
should do so instantly. Instantly becausewith()
does the same and it is required for any filter optimizations to work correctly.At the moment relations of selected columns are only resolved in
Query::assembleSelect()
. This is too late and can't be assumed as an requirement for e.g. filter optimizations.The text was updated successfully, but these errors were encountered: