Skip to content

Updating date parsing instructions after previous syntax was removed #46

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/beancount_query_language.md
Original file line number Diff line number Diff line change
Expand Up @@ -175,7 +175,7 @@ The data attributes extracted from the postings or transactions have particular

- String (Python str)

- Date (a datetime.date instance). You can parse a date with the `#"..."` syntax; this uses Python’s dateutil module and is pretty liberal in the formats it accepts.
- Date (a datetime.date instance). Dates are entered in `YYYY-MM-DD` format: `SELECT * WHERE date < 2024-05-01`.

- Integer (Python int)

Expand Down Expand Up @@ -241,7 +241,7 @@ We also provide a regular expression search operator into a string object:

At the moment, matching groups are ignored.

You can use string, number and integer constants with those operators, and parentheses to explicitly state precedence. You can use the `#”...”` literal syntax to input dates (valid contents for the string are pretty liberal, it supports anything Python’s dateutil.parser supports).
You can use string, number and integer constants with those operators, and parentheses to explicitly state precedence.

Here is an example query that uses a few of these:

Expand Down