[IRCServices] Panic / Segmentation fault?
dblanch at home.com
Wed Jan 17 17:52:16 PST 2001
Here's an idea... Make a way to export the *.db to a ascii text file, and a
way to import it in the event of database corruption. Rebuilding the text
file would be much easier on the admin. Think of the way, for example, a
program like AutoCad handles the source, and compiled versions of its menu
files. This, coupled with the habit of regular backups, could really help
out a lot. I could go on and on with why this a good idea, but for now I'll
just let ya dwell on it :)
My 1.5 cents... lol
> Actually, I'm considering a fairly major change in the database
> format for 5.0 (my plan is to start 5.0 development shortly after
> releasing 4.5) to prevent this kind of problem, where a single corrupt
> entry renders the entire database unusable. However, the DBs shouldn't
> become corrupt in the first place, so the only real solution I can
> suggest is to take backups. On EsperNet we take two backups a day so
> we're never more than 12 hours behind, which should be more than enough.
> (Why would recovering from a previous day's backup not be an option?
> It's surely better than losing everything.)