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
At the moment limt, filter etc have to be explicitly performed within aggregate nodes. This is due to both inline arrays (no current way to stream their items through nodes, e.g. limit), and because of the way grouping works (single pass).
Have a bit of a think on this and see if we can remove some of this duplication - it will continue to grow as more aggregates get added, and as more options get added to them.
The text was updated successfully, but these errors were encountered:
I thought about it, is not worth doing this now, especially given that arrays are all read into memory at the moment anyway. Might include additional locally-scoped refactorings with the array-order ticket, but nothing significant for 0.3.1
At the moment limt, filter etc have to be explicitly performed within aggregate nodes. This is due to both inline arrays (no current way to stream their items through nodes, e.g. limit), and because of the way grouping works (single pass).
Have a bit of a think on this and see if we can remove some of this duplication - it will continue to grow as more aggregates get added, and as more options get added to them.
The text was updated successfully, but these errors were encountered: