Is anyone actively working on backing up the database?
If not how about something as simple as making a copy of cards.db at
program start up (before the database is read)? Allow the user to specify a
maximum amount of space to use for backups and just keep as many cards.db
backups as possible, named by date and time? This gives an advantage of
being able to restore the whole database even in the event of filesystem
corruption.
For now just keep the backup copies and allow the user to manually replace
them. In the future add an interface to load a backup db instead of the
current one? I'm just picturing a list of backups available. If the
database is so corrupt it cant load the user could be informed and
presented a list of database backups to load.
I'm imagining a preferences option with a tick box for keep backups (which
should be the default IMHO) and a text box (or slider) to pick a maximum
number of MB of Databases.
I have my cards inventoried as well btw, hence why I care :)
As an aside the backups could be compressed which reduces the db size from
about 5MB to about 900K using gzip.
Personally, no. I still wanna work on unit testing and automake-autoconf
stuff first. I had couple ideas for backing up the database but have no
time for it.
Just a note about this bug. It was a small error in the way information
was written to the database so now the error should be fixed. I think that
the database backup is more a feature request than a bug anymore and should
be designated as such.
However, I do think its a good idea to always backup a database.
Rob Woodruff
JFHarden, Just another less vague comment.
I like the idea of what your talking about with the backup database.
It sounds nice. And if and when graham does another build I would like for
you to see the fix I made to the inventory function. Any changes you would
recommend I will look at. I will hack away at the source and see if I can
get it to do the backup your talking about. I am also playing around with
having DRAFT text added to certain cards.
Rob