Budgets and inconsistent handling of account sign reversal.

Jeff Kletsky gnucash at allycomm.com
Tue Feb 23 16:27:30 EST 2010

On 2/23/2010 12:44 PM, Christian Stimming wrote:
> [...]
> You can always add kvp_frame entries at some of gnucash's top-level objects,
> like the Book, Account, Transaction, or Split. See e.g. the Notes field of an
> Account in xaccAccountSetNotes / xaccAccountGetNotes in engine/Account.c.
> The kvp data is transparently read and written again by all earlier versions.
> At least for XML, this is currently our most efficient solution when adding
> new fields without breaking backwards compatiblity.

Appreciate the pointers as to where to consider looking. I've been 
looking at using "user preferences" and that seemed to work. Always open 
to suggestions.

> [...]
>> Is there supposed to be guaranteed backward compatibility for anything
>> but the XML backend?
> As Derek said: The previous stable series 2.2.x only had XML backend, so the
> new backends don't have to be backwards compatible to anything. It would be a
> good time to build in some functionality to offer such a guarantee in the
> future, though...

Good to know -- I recall something about PostgreSQL or some other older 
option. Cutting down the test matrix is always a good thing!

Looking forward to making some meaningful contributions here as I learn 
to love gnc-numerics and all their friends.

More information about the gnucash-devel mailing list