Hey,
> The other thing I'm considering is keeping a syncronised SQL database
> (2) going with Subversion which could be used to do things like
> allocate custom permissions to resources, more complicated searching
> and the storage of custom "resource types". This is very similar to
> the mod_dav_dbms architecture that allows searching (DASL) to DAV
> resources. All that is required is that when subversion commits a
> change, (eg a document's locations is changed) that it spawns a call
> to a wrapper class that logs this to the database.
>
Before a SQL effort can be cranked out, the FS backend needs to be made
"pluggable". Watch for threads with "pluggable-db" in the subject.
The SQL work I've done (I can't speak for anyone else) is focused on
providing a SQL DB backend as an alternative to BDB. The FS API will
not change early on. I'm sure any query extensions to the FS API will
require much debate. Also don't assume that once we have a SQL backend
that it will be as simple as whipping up few fancy queries behind the
scenes. The Subversion FS schema will make for some tricky queries. I
plan to *grow* into the more sophisticated query capabilities over time:-)
I got behind do to illness but I'm back on track now. Watch for a new
pluggable-db design document soon.
gat
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 28 17:21:32 2003