structure of fsfs?

[Roger Keays <ro...@ninthave.net>]

Hi all,

The new fsfs - does it look like CVS' backend where you can obliterate files by
deleting them from the CVSROOT, or is does it look like the existing bdb
backend where the data are stored in a magic format (maybe still accessed by
SQL)?

Cheers,

Roger

-- 
--
Ninth Avenue Software
http://www.ninthave.net


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: structure of fsfs?

[Greg Hudson <gh...@MIT.EDU>]

> The new fsfs - does it look like CVS' backend where you can
> obliterate files by deleting them from the CVSROOT, or is does it
> look like the existing bdb backend where the data are stored in a
> magic format (maybe still accessed by SQL)?

Because Subversion versions directories as well as files, our back end
can't really look like CVS's back end.  An FSFS repository stores two
files per revision (one file containing the revision data, which never
changes, and one file containing the rev-props).

FSFS does not make it any easier to obliterate files.  If anything,
it's more difficult than it is with the a BDB back end.

Neither back end accesses any data with SQL; Berkeley DB is not that
kind of database.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org