Re: [viewvc-users] Veriying that the SQL Checkin DB contains data for all revisions in an svn repository
"C. Michael Pilato" <[email protected]>
| Newsgroups | gmane.comp.version-control.cvs.viewcvs.user |
|---|---|
| Organization | CollabNet, Inc. |
| Message-ID | <4DF76173.2010007__32698.7808839933$1308057997$gmane$org@collab.net> |
On 06/13/2011 05:37 PM, Asd Asdasd wrote: > Hi, > > How can one verify that each revision in an SVN repository has indeed been > captured in the SQL Checkin DB? It looks like descs.id column might be the > one, however when "browsing" this table the row count is less (by half) than > the number of revisions in the SVN repos. > > Basically I am looking for a rough indicator of completeness for Checkin DB > reflecting what's in SVN. If I recall correctly, the checkin database was designed to avoid duplicated data, so if you have several revisions which all have the same commit log message, that message is stored once and referred to by an ID in all the places it is used. Also, the database is driven on file changes. So, if half of your commits have, say, an empty commit log message, they will share a reference to a single item in the 'descs' table. And any commits in which all the changes made were made to directories will not be stored in the checkins database at all. > PS: It would be nice if "./svndbadmin rebuild" gave some rough stats, e.g. > the number of SVN commits/revisions processed. Since SVN makes things so > nice with its global-revision numbers, transactional processing (ACID), and > structured data, why not benefit from this? './svndbadmin rebuild -v' ? -- C. Michael Pilato <[email protected]> CollabNet <> www.collab.net <> Distributed Development On Demand ------------------------------------------------------ http://viewvc.tigris.org/ds/viewMessage.do?dsForumId=4255&dsMessageId=2765316 To unsubscribe from this discussion, e-mail: [[email protected]].
signature.asc
(application/pgp-signature, 198 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk33YX4ACgkQokEGqRcG/W4KkwCgrMJ/QApXxfPAUct3GmDgesue BNsAmgMIDKPHyEMzFF27LYdefMskQ+fK =dq8s -----END PGP SIGNATURE-----