Thanks for your information that makes me confident to use CouchDB for this task.
Before getting start, I think to calculate the balance seems difficult, no matter it is schema-less or not. For example, if I delete a older transaction, then all balance in following transactions must be updated one after another. For CouchDB, maybe some views need to be rebuilt, too. It seems to be time consuming. (Suppose there is a balance field in each transation --- CouchDB doc.) Any idears for this? 2009/4/14 Nicholas Orr <[email protected]>: > I've looked into doing my own accounting app as well. Sitting with an > accountant the main thing she had an issue with, in regard to all the > products currently available, is tracking what the amount is for on each > side of the transaction. > > Example, say I as an individual transfer $10K into a company I'm a director > of. On the individual side (withdraw) of the transaction info needs to be > recorded as one thing, then on the other side (deposit) different > information needs to be recorded. This whole transaction needs to exist in > both places so come tax time the account doing the work for tax can follow > everything simply. > > The concept of schema-less documents now starts to shine as ideal. I have a > few other projects on the go right now and will not be getting to this one > anytime soon. Interested in what you guys come up with :) > > Nick > > > -- Li Zhengji ------------------------------------------------------------- If all you have is a hammer, everything is a nail. -------------------------------------------------------------
