Re: bean-query transaction grouping for render?

On Thu, Aug 3, 2023 at 4:25 AM Daniele Nicolodi wrote: > On 03/08/23 08:27, Eric Altendorf wrote: > > When you do something like > >SELECT account, SUM(position) ... > > > > you get a nice table where the list of positions for each account is > > grouped (with expand=true, it renders like a

Questions on cost tracking

Couple questions on cost tracking: *1. When are acquisition dates tracked in Cost objects vs. not?* The query that I use for generating inventory reports at a particular time is this: SELECT account, SUM(position) as lots, UNITS(SUM(position)) AS total, COST(SUM(position)) AS total_cost FROM

Re: bean-query transaction grouping for render?

On 03/08/23 08:27, Eric Altendorf wrote: When you do something like   SELECT account, SUM(position) ... you get a nice table where the list of positions for each account is grouped (with expand=true, it renders like a nested set of rows within the row) and each account name is only printed

Re: Errors from run_query(), not from bean-query

On 03/08/23 07:20, Eric Altendorf wrote: On Wed, Aug 2, 2023 at 5:55 PM Martin Blais > wrote: On Thu, Aug 3, 2023, 08:54 Martin Blais mailto:bl...@furius.ca>> wrote: Use bn.loader.load_file(), not just the parser. Beancount has two stages: parsing,

bean-query transaction grouping for render?

When you do something like SELECT account, SUM(position) ... you get a nice table where the list of positions for each account is grouped (with expand=true, it renders like a nested set of rows within the row) and each account name is only printed once. When you do something like SELECT id,