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

Re: Current state of SQL backend

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2005-03-07 19:01:00 CET

Graham Leggett <minfrin@sharp.fm> writes:

> friedbert.widmann@hoerbiger.com wrote:
> > Can anyone tell me, how far is the integration of SQL databases for
> > backends in Subversion?
> > We are interested in using Subversion for our SCM - but managing a Berkeley
> > DB beside our existing Microsoft SQL Server isnĀ“t our aim.
> We have chosen the fsfs backend for our system, which to date has
> needed zero administration. I feel happier with keeping something
> fundamental like source code in as simple a system as possible - to me
> SQL is complexity that doesn't seem to add any value.

The value-add for an SQL backend is mainly two-fold:

   * Trivial, customizable reporting. Write any query you want to
     suck whatever data out of the repository you so desire, munge it
     for human consumption, and you're done. No changes to core
     Subversion required at all.

   * Enterprise buzzwordiness. Some folks (for reason I neither
     understand nor offer justification for) just don't feel good if
     there data doesn't live in the database system they're forking
     out the big bucks for.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 7 19:05:14 2005

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.