Preventing unbounded file growth

[M Prindle]

In theory you could can still read the whole database, but you could
split the read into two or three chunks to decrease the time it take
to load large files.

Mike

On Mon, Apr 19, 2010 at 4:44 PM, Derek Atkins <warlord at mit.edu> wrote:
> M Prindle <mprindle at pobox.com> writes:
>
>> At this point I don't see much of an issue of the file sizes getting
>> out of hand.  I started using GNUCash at the start of '09 so I now
>> have 1.25 years or so worth of data.  This includes several checking
>> and savings account, plus all of our small business stuff.  The
>> compressed file size is 183k.  In the future when the next stable
>> version is released it will be database driven so the file size pretty
>> much a moot point since the time to save and open pretty much goes
>> away with the XML file.
>
> Actually, the time to open is still O(n).  We still read in the whole
> data file, even from SQL.
>
> Hopefully that will change after 2.4, but in 2.4 it's still a while.
>
>> Please remember to CC this list on all your replies.
>> You can do this by using Reply-To-List or Reply-All.
>
> -derek
>
> --
>       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>       Member, MIT Student Information Processing Board  (SIPB)
>       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
>       warlord at MIT.EDU                        PGP key available
>