Connect currency exchange transactions and pricedb, or not?

[Christian Stimming]

-----BEGIN PGP SIGNED MESSAGE-----

On Samstag, 30. November 2002 18:09, Derek Atkins wrote:
> You unfortunately did not understand my intentions and you
> misrepresented my views.  While your history of "how it's done in 1.6"
> is correct, you clearly have not looked at the issues involved here or
> listened to what I'm trying to do:

Ok, I'm sorry. Thanks for your detailed explanation now.

> 1) When viewing an account in auto-split or ledger mode, the "amount"
>    displayed in the register is the value in the transaction currency,
>    not the account currency.  This means that if the currencies do not
>    match (because you're viewing the transaction from another
>    account), the value "looks wrong" (because it is not the account
>    currency).  This was bug #99083.

which you have successfully fixed now (woo-hoo), as it seems. The amounts in 
the register view look very correct now.

> 2) The plan to use the pricedb is to store _one exchange rate per
>    commodity-pair per day_.  In other words, it is _NOT_
>    per-transaction.  Similarly, the pricedb entries are only used for
>    display purposes..  The transactions will still contain the exact
>    same information they do today.  In particular, each Split will
>    still contain the "amount" (in its account currency) and the
>    "value" (in the transaction currency).

The part about "txn will contain the same information they do today" sounds 
reasonable to me. I'm not really sure about what it means to store one 
exchange rate per day, and how this is going to be implemented (what if 
several balanced txns have different rates), but it seems we at least agree 
in that the important information will be stored in the transactions only.

> If you can come up with another way to deal with imbalanced,
> multi-split, multi-currency transactions, I'm all ears.  

No I don't have a better idea either -- this general case just goes over my 
head :-) . Thanks for the explanation.

Christian

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iQCVAwUBPeoXu2XAi+BfhivFAQEziQQAp3Z1vBMMIWSHtEXxP17AqauZxKRg/DiT
FRj9Bye6NvjDAXgKh8mAYQmp7ndaC2O/eFF7ZM6P3azTw73RfHR1v9ffHHUHxZfq
+cVQ4/b1mulG48b5h1fTRPsnQxF7+eW25hhYXBXlFg4Kt1V8V9VbMy4KRhRyvLqS
Ai05mP1FnjI=
=XYBX
-----END PGP SIGNATURE-----