I want to create a database schema where I will log all of my commits, via
a hook script, and perhaps also capture and store other statistics in the
process such as diff stats. My ultimate goal is to drive a
ViewCVS/WebSVN-type web application written in Java/JSP. Ideally, I would
like to have the web app work completely off the database, as opposed to
talking to the actual repository. Exception would be pages that display
file contents etc...
I am curious if someone has already done some of this, particularly the
database schema design. In particular, I am curious as to how best to
design the schema to make it easy to build the kind of repository/browse
and drill-down features as contained in ViewCVS. I have looked at it's
SQL database but I am unclear as to how it is actually used by the web
interface. I didn't see how the schema could support representing a
repository layout, as I saw nothing that indicated the relationships
between directories in the repository.
It would be easy to design a repository that just stored the commit info,
but ideally, I would like the file info from the commits to be stored in a
way that would make it easy to build a repository browser off of the info.
So, has anyone done this before?
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 Thu Aug 5 16:37:20 2004