On Mon, Jan 02, 2012 at 04:13:51AM -0600, John Wiegley wrote: > >>>>> Peter Keen <[email protected]> writes: > > > To answer the obvious question, I feel that the SQL+HTML combo allows quite > > a bit more flexibility than raw ledger with respect to the kinds of reports > > I can write and how they can be presented. Things that would require > > multiple calls to ledger and a bunch of shell scripting become a > > straightforward SQL query, especially with PostgreSQL 9's "with" expression > > and window queries. > > How exactly are you loading the Ledger data into SQL? I've actually been > wanting an 'sql' report for some data, to facility data mining with > professional DB tools... Maybe we can get native SQL generation in for 3.1 or > something. > > John >
On this same topic, I'm trying to reimplement my expense reporting logic in SQL and a Tkinter UI so I can pass the responsibility on to someone else. I've had little luck educating my end users with administering my ledger based expense reporting. I'm using SQLAlchemy with Postgres in Python, and simulating the same double entry records that Ledger uses. I'd be happy to share. The core is that there's a table for txns, and a table for postings, where many postings to one txn. Objectized in Python I'm not having to write raw SQL, which is nice. If there's interest, I may post my repo and a core of real sample data. Thanks. ------------------------------------------------------------------ Russell Adams [email protected] PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
