On Sep 13, 2013, at 7:11 AM, Derek Atkins <[email protected]> wrote: > John Ralls <[email protected]> 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 where 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. Regards, John Ralls _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
