Questions after xml->sqlite conversion

David T. sunfish62 at yahoo.com
Thu Feb 21 19:48:45 EST 2013


Stephen--

I don't know about #1, but I imagine that #2 results from teh fact that the XML file is by default compressed, and I am betting that compression isn't applicable/available in sqlite. I know that my XML file expands from ~4MB to something like ~20+MB uncompressed, so it wouldn't surprise me to hear the file size discrepancy.


David



________________________________
 From: StephenAndMandy Cleary <stephenandmandy at gmail.com>
To: gnucash-user at gnucash.org 
Sent: Thursday, February 21, 2013 9:08 AM
Subject: Questions after xml->sqlite conversion
 
Hello, folks -

Long time user of GNUCash here. I've been looking forward to the db file
format for a while, and recently updated my primary finances file to use
the new sqlite format. I've got ~6 years of transactions in there.

With the XML -> db conversion, I was expecting a reduced file size and
faster startup times, neither of which has happened. I no longer have to
save, but I notice that it doesn't keep open a lock file, either.

So, my questions:
1) Is GNUCash still safe for multiple users? I have my finances on Dropbox
and occasionally use multiple access (restricting writes to the first user
is fine, as long as the others can read). The lock file worked for this but
will sqlite?
2) Is the expected file size for sqlite much larger than xml? My xml db was
840,531 bytes and I thought it would go down when moving from xml to a
relational db. The sqlite file is 6,503,424 bytes. I went from <1MB to
6.5MB. Is there something wrong or is this normal?

Thanks,
      -Steve
_______________________________________________
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.


More information about the gnucash-user mailing list