Right now, we store security quotes mingled in with the other splits
in a given security account. I'd like to consider the question of
whether or not this information should be broken out into a separate
database.
Currently I can think of:
reasons for:
- Semantically quotes aren't really financial transactions.
- Say you hold a security in four different accounts; right now with
each quote, we'll end up storing it four times, once in each
account.
- We may eventually want to use the quote archive for other
purposes, or alternately, provide a mechanism to hook up to a
"live" historical archive when you're on the net. This will be
even more useful when we get graphing and charting going and if we
decide to start expanding our stock/financial analysis
infrastructure.
reasons against:
- If there were ever a situation where the user wanted to have two
securities with the same name, with different quote sources
beacause they expected the information to be different from the
two sources, then having a centralized quote archive wouldn't make
sense, but when would this ever happen?
- If the user likes to see the running total of how they were doing
over time *in the ledger*. However, I'd tend to argue that that's
really better left to the reporting/graphing infrastructure.
The reason I bring this up is that I'm in the process of integrating
getting quotes directly into gnucash (no more external program), so
I'm thinking about this stuff right now.
Thoughts?
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
