Getting complete revision history with the current DB model

Sorry if this is a FAQ; I found quite a few messages in the archives
regarding version trees etc. but they didn't really answer my question...

Looking at a given node in a working copy, "svn log" lists all revisions
from the current one back to the root of version tree of your node. But
this is just one path in the version tree, and sometimes you want to see
the complete tree, e.g. to find out if someone has branched off from an
earlier version of your node and made some changes that you may have to
merge.

I remember reading a posting saying that all required information is
contained in the BDB "copies" table. Well, if I'm not mistaken, all the
information *is* contained in the DB, but you'd have to scan all entries
of some tables for lack of suitable indices or foreign keys.

You get the predecessor of each node revision and the children of each
directory node at constant cost, but to dump the complete history of a
node, you have to find the successor revisions and then the parent
directory to map your node to a path name.

Am I missing something obvious? If not, are there any plans to extend
the DB model? Or should we wait for an SQL DB backend and then get all
sorts of queries nearly for free?

Regards,
Harald

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 11 23:59:58 2003