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

Re: MySQL Backend

From: Dominic Anello <danello_at_danky.com>
Date: 2006-01-24 14:58:35 CET

On 2006-01-18 10:41:22 +0000, Greg Thomas wrote:
> On Wed, 18 Jan 2006 09:31:12 +0000, Greg Thomas
> <thomasgd@omc.bt.co.uk> wrote:
> >On Wed, 18 Jan 2006 15:06:08 +0800, Adrian Hoe <mailbox@adrianhoe.com>
> >wrote:
> >
> >>Replication, rollback, trigger and stored procedures. All these FSFS
> >>does not have
> >
> >But FSFS it need it?
> I'll try that again /after/ coffee:
> Does a Subversion repository filing system need all these DB features?
> What exactly do you want from Subversion that FSFS does not currently
> offer you that moving to MySQL will give you?

I for one would love a more robust query interface into the repo. I've
thought of loading the repo history into a RDBMS just to be able to
support asking questions like:

Where were all modifications to somefile.h made?

SELECT a.rev, r.author, a.path
FROM actions a
JOIN revisions r ON a.rev = r.rev
WHERE action='M' AND path like '%/src/somefile.h'

What tags have been made off of the project-2.3.1 branch?

SELECT path FROM actions
WHERE action='A' AND copy_from='/branches/project/project-2.3.1'

I've often had other devs me questions like these that I could only
answer by grabbing the log and grepping through it. It'd be nice to be
able to tell them "You know SQL, here's a read-only account on the repo
DBMS, knock yourself out".


  • application/pgp-signature attachment: stored
Received on Tue Jan 24 15:01:28 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.