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
This might be off the mark with BerlinDB direction, but It would be useful to have the ability to "SUM" specific columns in the database tables without having to write custom queries as a fallback. Having the ability to use AVG/MAX/MIN would also be beneficial in a lot of use cases.
The text was updated successfully, but these errors were encountered:
I think this would be useful, too. I currently have to write manual queries when I decide to do this sort-of thing.
A pattern that has worked fairly well with MongoDB has been the distinction between a query and an aggregation. I think Berlin does a great job with query, via the current Query class, perhaps it's time to consider something handles aggregations?
Theoretically, the query class could eventually turn into a wrapper for the core class that creates clauses.
I sort-of started that process in this PR, but I'm not convinced what I did should even be in the Query class.
Some more good news - it appears that BerlinDB already has support for group_by in Query, although as of this writing it is undocumented. Probably just an omission.
It adds aggregate functionality by hijacking the COUNT queries to perform different operations in a single query. GROUPBY queries are also supported and work as expected.
This might be off the mark with BerlinDB direction, but It would be useful to have the ability to "SUM" specific columns in the database tables without having to write custom queries as a fallback. Having the ability to use AVG/MAX/MIN would also be beneficial in a lot of use cases.
The text was updated successfully, but these errors were encountered: