For me this is simply a must! I'm using SQLite in my e-mail client which I hope will be one of the first large scale deployments of SQLite where it will be used heavily on a daily basis. If the database is corrupted then people lose all their e-mails and that's simply intolerable! I can't release my e-mail client on the general public until this issue has been addressed or at least until someone shows me how to repair a corrupted database programmatically.
Olaf ----- Original Message ----- From: "Dave Dyer" <[EMAIL PROTECTED]> To: <sqlite-users@sqlite.org>; <sqlite-users@sqlite.org> Sent: Wednesday, August 16, 2006 10:39 PM Subject: [sqlite] Re: fault tolerance > > I realize that sqlite uses the best available techniqes to > always fail safe and therefore avoid database corruption, it > remains that case that "shit happens" and when it does, sqlite > databases become hopelessly corrupted. > > Traditional file systems have evolved an array of techniques > to limit the damage caused by corruption - redudnant records, > checksums, and so on. > > I would like to see features of this type in future versions of sqlite. > > > -------------------------------------------------------------------------- --- > To unsubscribe, send email to [EMAIL PROTECTED] > -------------------------------------------------------------------------- --- > > ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
