Add "beancount" result set renderer #188
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm opening this PR mostly to record some thoughts. What it is implemented here is the bare minimum that would be required to make the
PRINT
statement a special case ofSELECT
withformat
set tobeancount
. This works:and prints all transactions in the beancount syntax. Actually, all transactions are printed one for every posting they contain. This could be solved with a
DISTINCT
clause, but entries are not hashable, thusresults in an error. This should probably be solved. Entries can be easily make hashable assuming that they are immutable.
However, when selecting for an account, this already does what is expected when filtering for an account:
and may already be useful to solve what @tbm was asking for in #123.
It is more tricky to make this work for tables that do not have a beancount entry type column. The best I can come up with is to use the
ROW()
construct. For example: