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

Re: filesystem oops?

From: Greg Stein <gstein_at_lyra.org>
Date: 2002-02-04 23:24:31 CET

On Mon, Feb 04, 2002 at 02:42:38PM -0600, cmpilato@collab.net wrote:
> Zack Weinberg <zack@codesourcery.com> writes:
> > There will, eventually, be changes which force a restructure pass over
> > the entire filesystem backing store. For bdb, we have db_dump and
> > db_load; for changes to the schema or other filesystem-level changes,
> > perhaps a svnadmin operation?
> Oh, yeah, there is already a bunch of cruft in the filesystem that
> needs to be removed/fixed. The easiest way to do this, and do it
> right, is to implement `svnadmin import/export', I'm thinking.

Yes. We also want the import/export tools for any number of other reasons.

What would be need is a Python-based import/export that directly reads the
DB file and exports it as a relational model. When we import the stuff, the
relations get new keys, which then cleans up some of the numbering issues.
Any data that isn't referenced, simply doesn't get included.

(oh, and then there is that part about importing into a relational DB...)


Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:04 2006

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.