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

Obliterate - design status - table row changes

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Tue, 24 Nov 2009 18:46:11 +0000

My recent focus on Obliterate has been learning how the DB tables hang
together, working out how I need to change the stored data at the level
of DB tables, and drawing diagrams of that.

Links to the diagrams are at the end of
<http://svn.apache.org/repos/asf/subversion/trunk/notes/obliterate/design-repos.html>

and, of those, the pair I've just drawn and committed are "before",
<http://svn.apache.org/repos/asf/subversion/trunk/notes/obliterate/schema-bdb-dd1-before.svg> and "after", <http://svn.apache.org/repos/asf/subversion/trunk/notes/obliterate/schema-bdb-dd1-after.svg>.

Those show what table rows I think need to change to do a simple
obliteration of a file "foo", like the first one shown in
<http://svn.apache.org/repos/asf/subversion/trunk/notes/obliterate/fspec-dd1/dd1-file-ops.svg>.

It's not in full detail.

Comments, please?

"Tables"? I'm using "tables" terminology because I'm looking at BDB at
the moment because it seems better documented. I do intend to implement
on FSFS first, though, if I can translate what I learned. However, if it
is difficult to translate this from BDB to FSFS I will probably
implement first on BDB to get something going, as I think it's important
to have some working repositories to play with. (I thought I'd have that
by now but it's not as simple as ... OK, I never believed it would be
simple, but still.)

- Julian

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2423923

Please start new threads on the <dev_at_subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <dev-subscribe_at_subversion.apache.org>.
Received on 2009-11-24 19:46:35 CET

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

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