On Sun, Apr 22, 2018 at 5:43 PM, Martin Michlmayr <[email protected]> wrote:
> * Martin Blais <[email protected]> [2018-04-22 17:31]: > > You can achieve the same thing already with a group-by on the (account, > > meta) pair: > > Doh, I should have thought of that. That's a good example of why BQL > is a great idea. > The most relevant insight in this whole thing is IMHO the fact that you can reduce all these accounting tasks to a single query on a single table (a join of transaction fields and postings fields). I started with the SQL thing not really knowing how far it would take us, but it turns out it pretty much can do it all, and you can factor out the reporting rendering code into two functions: one to render journals (generic, just a table), and one to render trees of accounts (implies a hierarchy from one particular column). Actual pivot tables (e.g., expenses by month) can be a post-processing of a group-by query with two columns (e.g., account, month-of-date, rendering sum(postings) in the cells). -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CAK21%2BhMpurrXtsgqDXR-F7AWXkRwgjJdFAXG36YGiikeUdiOGQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
