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

Re: Database Schema for Commit Logs

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2004-08-16 16:38:01 CEST

Kapil Thangavelu <hazmat@objectrealms.net> wrote on 08/16/2004 12:43:59
AM:
> >
> > I do not think Trac stores Subversion info in their database (with the

> > possible exception of revision numbers), it looks like its browser is
> > using the Python bindings to browse the repository directly. That is
not
> > what I want. The Trac schema just has tables for the the Trac stuff
like
> > their tickets and Wiki. I am looking for an example schema that can
> > mirror the Subversion repository structue, in addition to the commit
info.
> >
> > Mark
> >
>
> i don't think you looked very closely then. trac indexes into its
> database each svn revision, to allow for unified searching across wiki,
> issues, and revisions as well other nicetites, like handling issue
> followups in log messages. it does this indexing (delta index against
> new revisions) every time it opens the repository, but it can optionally
> do this from a commit script, see the following link for the schema.
>
> http://projects.edgewall.com/trac/file/trunk/trac/db_default.py

What I meant to say is that Trac does not drive its repository browser off
of its database. Yes, it stores revision info in its database, but that
is not what drives its repository browser, and that is the part I am
trying to figure out a way to do.

My original plan was and is to store the same kind if information Trac is
storing. I just thought that since I am going to store this information,
it would be nice if I could structure it in a way that I could build a
repository browser off the database. I gave the reasons why I wanted to
do it that way in another email.

Thanks

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 16 16:38:26 2004

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.