Hi Robert,
> One thing that all of the *SQL backends do provide over the flat XML file
> storage: accessing the data (*read-only!*) between runs of GnuCash is easier.
> Instead of either trying to parse the XML or using Python bindings to the
> GnuCash API, one can write code using SQL (in any language that supports SQL)
> to grab data to generate reports, etc. outside of the GnuCash framework. I
> believe at least one person on this list does exactly that.
Oh! Do I understand the GnuCash parses the data and stores it in database
tables? --- like one table for each account? Or are all the rows going to be
the same with each row being an accounting transaction "acct 1 $X.XX acct 2
-$X.XX"? What about "splits"?
Thanks for the help,
--
Chris.
V:916.799.9461
F:916.974.0428
A: Because we read from top to bottom, left to right.
Q: > Why should I start my reply below the quoted text?
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
