2.3.15/tax package: basic questions

[Phil Longstaff]

This actually makes sense.  I'm sure I know what the problem is.  With the XML 
backend, when you write, everything (transaction data, prices, tax code 
assignments, etc.) is written to the file.  When you Save As to a new sqlite3 
file, everything is written.  The difference is in what happens when you modify 
something.  For transaction data and prices, there is a special step to commit 
the changes.  With XML backend, this commit step does nothing (because 
everything will be written to the XML file when you save), but with the sqlite3 
backend, this commit step saves the changes to the sqlite3 file.  There is no 
commit step for tax code assignments.  With XML backend, this is fine, because 
they will be saved when the file is written.  For sqlite3, this is a problem 
because there is no clue that something needs to be written.

We ran into this previously with some of the business preferences which are 
stored in the same basic way that tax code assignments are.  These preferences 
weren't being saved until I added a commit step for them.  We also need to add 
this commit step for tax code assignments and everything else which is currently 
stored in the kvp-frame for the book.  I'll need to search the code to see what 
else might have the same problem.

 Phil
---------
I used to be a hypochondriac AND a kleptomaniac. So I took something for it.




________________________________
From: J. Alex Aycinena <alex.aycinena at gmail.com>
To: gnucash-user at gnucash.org; Jannick Asmus <jannick.news at gmail.com>
Sent: Fri, August 20, 2010 2:49:32 PM
Subject: Re: 2.3.15/tax package: basic questions

Jannick,

> ---------- Forwarded message ----------
> From: "Jannick Asmus" <jannick.news at gmail.com>
> To: gnucash-user at lists.gnucash.org
> Date: Thu, 19 Aug 2010 19:36:26 +0200
> Subject: AW: AW: 2.3.15/tax package: basic questions
> Derek Atkins wrote:
>>
>> "Jannick Asmus" <jannick.news at gmail.com> writes:
>>
>>>> I'm not sure what you mean by exporting to sql.
>>>
>>> Let me clarify: The latest (unstable) versions export the gnucash
>>> file to an sql to have it as a database. In this kind of export the
>>> tax attributes associated to accounts are not exported.
>>
>> By "exported" I suspect you mean "saved as"...   If Save-As to a SQL
>> DB does not save the tax attributes, that's a bug that should be
>> reported and fixed.
>
> Your suspicion is correct. ... bug filed: 
>https://bugzilla.gnome.org/show_bug.cgi?id=627393
>

<snip>

I have taken an xml based gnucash file with tax codes assigned to
accounts and saved it to a sqlite3 database file, closed gnucash and
re-opened the sqlite3 database file and all the tax code assignments
seem to be preserved properly and the Tax Report is exactly as it was
in the xml version. So this indicates that the tax attributes are
being saved. I will annotate the bug accordingly.

Alex
_______________________________________________
gnucash-user mailing list
gnucash-user at gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.