Re: proposed new SQL function: ANY_META

2016-11-20 Thread Martin Blais
Fixed. Sorry about that. On Sun, Nov 20, 2016 at 2:40 PM, Stefano Zacchiroli wrote: > On Sun, Nov 20, 2016 at 02:19:37PM -0500, Martin Blais wrote: > > I like it. > > Done: > > https://bitbucket.org/blais/beancount/commits/ > 90472db4ef144783408844a22cbc5dc4a54ba39b > > Thanks Martin! > > As a

Re: proposed new SQL function: ANY_META

2016-11-20 Thread Stefano Zacchiroli
On Sun, Nov 20, 2016 at 02:19:37PM -0500, Martin Blais wrote: > I like it. > Done: > https://bitbucket.org/blais/beancount/commits/90472db4ef144783408844a22cbc5dc4a54ba39b Thanks Martin! As a minor nit, can you fix the typo in my family name in the ChangeLog? (it's single 'l', not two) TIA, Chee

Re: proposed new SQL function: ANY_META

2016-11-20 Thread Martin Blais
I like it. Done: https://bitbucket.org/blais/beancount/commits/90472db4ef144783408844a22cbc5dc4a54ba39b On Mon, Nov 14, 2016 at 9:38 AM, Stefano Zacchiroli wrote: > Coming from the Ledger half of the Free accounting world, I'm used to > the fact that transaction metadata propagates down to post

proposed new SQL function: ANY_META

2016-11-14 Thread Stefano Zacchiroli
Coming from the Ledger half of the Free accounting world, I'm used to the fact that transaction metadata propagates down to postings. Please correct me if I'm wrong, but this doesn't seem to be the case in Beancount, at least according to my experiments with bean-query. I'm fine with Beancount mod