Just some questions and annotations. Now, if we do something like this, do we still need the filesystem in a proper DB or would an ad-hoc DB (aka text file) do the job just as well?
> 4) We are not in a single-file pristine case, but we no longer have > issues with "spurious" files on the pristine directory. Was thinking about this for a second. Three kinds of pristine corruption are possible: - adding stuff to pristine that shouldn't be there -- solved - taking something away -- solved (we can complain) - modifying something in pristine -- reduced risk (below) I guess... that would at least 'fix' my scare scenario, people using Unison to synchronise files (because I know some non-expert darcs users who do make heavy use of it). You rm a file, record and unison. Either Unison or the user gets confused and puts the file back into pristine. Pristine is hereby corrupted. But this kind of thing would be handled correctly, right? > 5) Filenames are made up, so no find / sed issues. It reduces the risk anyway; some stupid sed tricks might not involve looking at filenames Are there any kinds of issues with the table getting out of synch with the data, that is any fancy new kinds of corruption that can sneak in as a result of this scheme? -- Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon français.
pgpapKsFY95Av.pgp
Description: PGP signature
_______________________________________________ darcs-devel mailing list darcs-devel@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-devel
