> T.Pospisek's MailLists writes:
> > On 13 Jun 2000, Bill Gribble wrote:
> >
> > > Ben Stanley <[EMAIL PROTECTED]> writes:
> > > > When I last entered all of my transactions, which would have taken me
> > > > about an hour, I had just finished and then GNUcash had a crash. I can't
> > > > remember if it was a seg fault or bus error or what, but I subsequently
> > > > had to re-enter everything I had just put in, by referring to the log
> > > > file.
> > >
> > > Ouch. I'm sorry :( I guess that's yet another case where "save early,
> > > save often" is your friend.
> >
> > What about having a:
> >
> > [] autosave ever [] minutes
> >
> > option? That is by default set to ... let's say 1 minute?
>
> That's a good idea, but it'll of course have to wait till 1.5.
>
> For implementing this, what about checking a "time since last
> autosave" every time a transaction is committed (language might be
> less than precise here, correct me if I'm wrong). If we're over the
> threshold, autosave. Comments, anyone?
It seems to me that recover-from-log is a cleaner solution.
We make the logs for this purpose and keep them continuously
up-to-date, don't we?
This should fit in the engine, or immediately above it; the data base
could be considered to consist of the existing file togetner
with the log of all more recent transactions. When you load a file,
you could automatically check whether it has any associated
more-recent logs. This could be treansparent, or you could ask
the user for advice if you find any.
-- hendrik.
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
