I was also looking for strong cross-currency support for my accounts where
prices do get very transitive... I ended up writing my own code to do this.
The algorithm is as follows
1) Examine all cross-currency transactions to find all conversion
"vertices" of a graph
2) Find the shortest distanc
Theoretically that can happen but in practice I don't think hit happens.
And even if it does the effect is more noticeable.
My personal accounts that I have represented in beancount are probably
close to the worst case scenario of real-life transitivity... I have income
in GBP, I earn in CNY. I
11 Mar (12 hours ago)
That's a nice idea, but one problem is that if the number of transactions
flip-flops the path in the graph after inserting new ones, you will
experience potentially confusing differences in your reporting. The user
has to be aware of this.
- show quoted text -
> - show q
Theoretically that can happen but in practice I don't think it happens. And
even if it does the effect is not noticeable in practice
My personal accounts that I have represented in beancount are probably
close to the worst case scenario of real-life transitivity... I have income
in GBP, I earn
