Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Find a better solution for the OPEN ON, CLOSE ON and CLEAR clauses #179

Open
dnicolodi opened this issue Jun 15, 2024 · 1 comment
Open
Labels
feature New feature

Comments

@dnicolodi
Copy link
Collaborator

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 of the SQL syntax that maybe could be expressed in a nicer way without leaking the domain specific issue into the general purpose query language. However, no better syntax comes to mind.

@blais
Copy link
Member

blais commented Jun 16, 2024

I gave this some thought in the past: these could be part of the table specification, e.g., ```

SELECT date, narration FROM beancount(/path/to/filename)

with options, e.g.

SELECT date, narration FROM beancount(/path/to/filename, open=2021-01-01, close=2022-01-01)


@dnicolodi dnicolodi added the feature New feature label Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature
Projects
None yet
Development

No branches or pull requests

2 participants