Re: Swapping Subversion DB with native XML DB

Aloke Agarwal wrote:
>
> Hi,
>
> I am in the process of evaluating Subversion for using inside a shipping
> product. I was wondering whether the followin is possible for subversion:
>
> 1. Swapping the Berkeley DB with Berkeley XML DB.

I don't know if anyone has ever tried - the Berkeley XML DB would need to
provide the exact same API as Subversion uses in order to be a drop-in
replacement. And there would be some questions as to the performance of
the system when configured in that form, but that is just my guess and not
based on any actual testing of the XML DB.

> 2. I also noticed that subversion when storing the content mangles the
> file name etc. Is it possible to store the file as it is:
>
> so If i store /root/Foo.xml then if backing store is Filesystem then can
> I see
>
> c:\root\Foo.xml

Subversion is not a per-file VCS and thus does not really lend itself to storage
of files within the filename. Each revision is some set of changes to the
whole tree of files which may include actual file changes, deletion of files,
metadata changes about the files, and "copies" of a file from another point in
the tree (usually used for branching/tagging and currently for for rename)

A major point/feature is that changes (commits) are atomic in nature and all
of the changes (multiple files, metadata, etc.) are all part of that single
commit.

At a very high level, the filesystem based backend, for example, each revision
is a single file containing the information to describe the changes to the
repository at that revision.

-- 
Michael Sinz                     Technology and Engineering Director/Consultant
"Starting Startups"                                mailto:michael.sinz@sinz.org
My place on the web                            http://www.sinz.org/Michael.Sinz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org