Re: SQL support

Brian Behlendorf <brian@collab.net> writes:

> On Mon, 17 Oct 2005, Lester Caine wrote:
> > Simple things like a view of number of commits by user over
> > timeframe -
> > linked to their profile in a framework user database. Access to a
> > list of who modified a particular file. All the sorts of things that
> > can be built and filtered as SQL queries without having to write
> > code.
>
> Sounds like much of the value of being in SQL lies in reporting, not
> in production; would it be better to take logs of commits made against
> the current database (content and metadata) and process them into
> commits against a relational database with a SQL schema optimized for
> reporting?

Yep. ViewCVS's svndbadmin tool does exactly this, basically crawling
a repository for commit information (in full, or incrementally) and
squirreling that away into a MySQL database. ViewCVS then provides a
Web-based query interface into that database. I can't vouch for the
completeness of SQL-stored data -- I imagine that since svndbadmin was
modeled after cvsdbadmin, that there are piece of information not
stored. But it might be a good starting point for someone interested.

-- 
C. Michael Pilato <cmpilato@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org