[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: AW: How to check integrity of database?

From: Matt England <mengland_at_mengland.net>
Date: 2005-10-05 15:15:08 CEST

At 10/5/2005 07:55 AM, Gary Thomas wrote:
>It [svadmin verify] does check that every revision can be reconstructed
>to dumping the repository without saving the results). I don't see
>that anything else is necessary.

How about regenerating for each file revision--or at least some revision
set like the head revision of said repo--a hash (eg, MD5, SHA-x), and
comparing with a hash initially stored upon repo commit (would require
design/code changes if not already implemented).

In other words, regenerating is nice, probably helps verify all the meta
data to some extent, but what about schemes to verify the content of the
files? The one above seems to be common one.

Do existing schemes exist and/or could they be implemented in the
future? I'm building such schemes for another swdev project I'm managing,
and I'm particularly curious about the trade-offs of such schemes--my group
thinks we have idea what these trade-offs are, but I'm interested in what
the analysts/experts would have to say (without any initial bias) the
trade-offs would be for subversion.

Sorry if this is a faq; I didn't see any of "md5," "signature," or "hash"
in a quick search of http://subversion.tigris.org/faq.html .


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 5 15:17:19 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.