On Thu, Jan 5, 2012 at 10:13 AM, Russell Adams <[email protected]> wrote: > 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.
Sounds interesting. I use SA at work quite a bit so I'd love to take a peek. On the topic of emulating the double entry set up with two tables, I had thought about it but for most of my reporting use cases I either don't really care since I'm wanting to know about accounts in isolation, or I can fake it with the transaction ID (starting line number of the transaction). Not dealing with raw SQL is nice sometimes but I don't really mind it. Optionally exposing Sequel (the ruby "ORM" I'm using) for reports to use might be a good idea for Ledger Web though, if that's actually a show stopper for others.
