I'm a fair bit checked out on beanquery but dnicolodi has made a lot of
improvements, he would know.
I think your best service is found by inspecting the source code,
especially this file:
https://github.com/beancount/beanquery/blob/master/beanquery/query_env.py
should be fairly straightforward.



On Mon, Jan 6, 2025 at 1:27 AM Oon-Ee Ng <[email protected]> wrote:

> I had a beancount v2 setup working fine, just this weekend I updated to
> beancount v3. There was an arch-specific hiccup with beanquery not working
> due to an older version of python-tatsu, but that wasn't too hard to fix.
>
> Now when testing my queries I realise the changes in BQL don't seem
> documented anywhere I can find. There's some github commits which mention
> some changes, but otherwise I'm fairly lost. Where can I find some
> equivalent of the BQL documentation Martin had for v2?
>
> The specific issue I'm looking at now is why ORDER BY yearmonth, Account
> DESC has stopped working (instead it always orders ascending, meaning the
> latest results are at the bottom). But I'd like to be able to solve my
> queries myself, so wondering whether documentation for this just isn't
> updated yet.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Beancount" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion visit
> https://groups.google.com/d/msgid/beancount/CAGQ70es_M7o1WoxJnDH7wv4iL_DERMDHzAsODsPP5qLXS_ym2Q%40mail.gmail.com
> <https://groups.google.com/d/msgid/beancount/CAGQ70es_M7o1WoxJnDH7wv4iL_DERMDHzAsODsPP5qLXS_ym2Q%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/beancount/CAK21%2BhP-ioX3Zus_Yvp2TP70GXr4%3D83KDt9P5KiQYPJFDvXN7w%40mail.gmail.com.

Reply via email to