![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
At first blush this seems to be a straightforward inventory table. On closer examination though, it appears that portfolio holdings (past and present) are actually a residual of transaction analysis of the investment account journal. An investor is not just interested in open positions, but closed positions as well. I'm not interested in current prices or historical analysis or comprehensive stock tables (the sorts of things that are discussed to death). Assume a journal has the following columns: ID Date Type Symbol Description Quantity Price Amount Type is in a separate table (Buy,Sell,Deposit,Withdraw,Dividend,Split, Interest) Symbol is in a table of company names The idea then is to generate open positions (or closed, or whatever) from the transaction journal. This solution must have been reinvented about a million times by now, but I can't seem to find much information on it. Surprisingly, I see recent calls for papers on the topic, so maybe nobody has a good solution yet... Is this approach completely wrong headed? Should I instead be focusing on the inventory approach? I have this prototyped and working in the small, but being a noob I don't want to get too invested in a schema that won't scale, or violates some DB design principle that will eventually result in my regret ;-) Thanks in advance for your thoughts, bullshark I think that keeping the data at the transaction level is probably |
#3
| |||
| |||
|
|
"bullshark" <bullshark (AT) gmail (DOT) com> wrote: ID Date Type Symbol Description Quantity Price Amount I don't know about elsewhere but, in Australia, your transaction lacks some vital information. |
![]() |
| Thread Tools | |
| Display Modes | |
| |