beanquery
beanquery copied to clipboard
beancount
A customizable light-weight SQL query tool that works on tabular data, including Beancount.
`SELECT *` currently does not render all fields but only a "resonable" subset. This is motivated by the fact that the `postings` table contains a large number of redundant fields....
Quoting `TODO.md` > Rename ACCOUNT_SORTKEY(), it's a terrible name. Name this REPORD() for "report order". I'm not sure `REPORD()` is much better. Another option is to introduce an `ACCOUNT()` function...
Namely support ordering the result rows in an aggrergate query by a function of one of the aggregate columns. Use case: ``` SELECT account, sum(position) GROUP BY account ORDER BY...
Quoting from `TODO.md`: > The OPEN ON and CLOSE ON syntaxes get on my nerves. I'm not so bothered by the syntax, but it is a very Beancount centric extension...
There is already very minimal support: tags and links are exposed as columns of type `set` and there are the `IN` and `NOT IN` operators. This needs to be expanded...
I'm going through the `TODO.md` file checking what has been implemented already, what fits with the current vision for beanquery, and what remains to do. There are two entries related...
`JOIN`s would be very useful for creating more advanced reports. Example query: ``` SELECT account, bal1, bal2 FROM (SELECT account, sum(cost(position)) as bal1 FROM CLOSE ON 2014-01-01 CLEAR) JOIN (SELECT...
See `.output` and `.once` in `sqlite3`. Maybe also add a `.format` command to replace `.set format`
Currently a statement can be read from the standard input or passed as arguments. However, only one statement per command invocation is supported. Allow multiple statements, including interleaving BQL statements...