On Sun, 2010-01-24 at 15:35 -0500, D. Richard Hipp wrote: > Could this be a case of "we've never done it that way before"?
I think it's more a case of "been there, done that, never want to do it again." Just search for "Berkeley DB usage leading to respository corruption and data loss" on the Wikipedia page for Subversion. I think an analogous (and common experience) is losing most of a *.tar.gpg file because one byte early in the file is corrupt. (I think the same thing is true of *.tar.gz but not *.tar.bz2.) On the other hand, if your archive is just *.tar, one corrupt byte will cause you to lose at most up to the start of the next file in the archive. What's the story with SQLite? What's my exposure to a single corrupt byte? Thank You, Paul Serice _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
