AUDIT: r23164 - gnucash/trunk/src/engine - Bug 684670 - Interest amount calculation is wrong in Sqllite3 format
mferrara at caltech.edu
Fri Sep 13 12:09:11 EDT 2013
Newbie here... Hope this isn't an obvious question, but wondering by the
way: Is there a stable trunk of gnucash that contains just the bare-bones,
double-entry core, sans the business features? Would one have to custom
recompile the program from scratch?
On Fri, Sep 13, 2013 at 8:43 AM, John Ralls <jralls at ceridwen.us> wrote:
> On Sep 13, 2013, at 7:11 AM, Derek Atkins <warlord at MIT.EDU> wrote:
> > John Ralls <jralls at code.gnucash.org> writes:
> >> Yet another corner where forgetting to run a edit-commit cycle when
> >> changing state breaks database save.
> > And people wonder why I still recommend against using the SQL backend
> > for real data.. ;)
> Yeah. I've been using SQL for my primary accounting for a couple
> of years without any trouble, but I don't use the business features and
> have only
> simple scheduled transactions. OTOH, I have a bit more understanding of
> the holes are than most users. :-/
> Anyway, I'm starting another sweep through the engine to find and fix
> state changes
> that don't happen in an edit/commit cycle, and edit/commit cycles that
> don't mark
> the instance dirty.
> I've been ignoring simple setters and getters in unit tests on the grounds
> that they're too
> trivial to test, but it occurs to me that I should be at least testing
> that the instance is dirty
> when a setter returns.
> John Ralls
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
More information about the gnucash-devel