Ben Collins-Sussman wrote:
>On Tue, 2004-04-06 at 10:54, C. Michael Pilato wrote:
>>Ben Collins-Sussman <firstname.lastname@example.org> writes:
>>>I guess what we're talking about here is a new svn_fs_* function and
>>>accompanying RA function to "return all revisions which have unversioned
>>>prop/val". Maybe we could file it as a new feature request? It would
>>>be useful not only for giving human names to revisions, but for any
>>>other use of unversioned revision-props... such as workflow systems.
>>I'd say this functionality belongs in libsvn_repos, not libsvn_fs. We
>>can loop over revision values and fetch one revision at a time, which
>>means we won't have to bother with cursor walks or the locking issues
>>that accompany them.
>Ah, yeah. I totally agree.
>Perhaps we should have other svn developers say something before I file
>a new feature request. Many svn developers only read the dev@ list, not
>the users@ list. I'll send a mail over to dev@.
I'm going to start you off. :-)
Whatever we do, I advise against linear searches in the strongest
possible terms. For this feature to be useful, it must _not_ be slow or
demanding on server resources.
I would propose to add another table for indexing revision properties.
The idea to index by date (and thus remove the restriction of
date-ordered commits, making it easier to combine repositories into one)
has been floating around for a while; I suggest extending it to all
revision props, with the following index:
(prop-name, prop-value) -> revnum
The keys must be non-unique, of course.
Um. No, not _all_ revision props; indexing by svn:log isn't very useful.
Perhaps repository-side configuration would define which properties
appeared in the index. svn:date and svn:author would be useful defaults.
If we add svn:name as a list of human-readable names for a revision,
each value from that list would appear in the index, too.
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Apr 6 22:40:21 2004