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

RE: Re: svn commit: rev 1957 - trunk/subversion/include trunk/subversion/libsvn_wc

From: <peter.westlake_at_arm.com>
Date: 2002-05-17 14:46:51 CEST

On 2002-05-17 02:21:58 "Bill Tutt" wrote:
>> From: Karl Fogel [mailto:kfogel@newton.ch.collab.net]
>> I don't really understand your question, I guess: "If the FS doesn't
>> know about modules, how can SVN answer questions about them?"
>> Answer: "In the manner described in issue #517, among other ways." :-)
>Err, that's not quite what I think he means.
>I think his question is more like this:
>"If the FS doesn't know about modules in a formal schema way, then how
>can the FS deliver answers to arbitrary queries about modules, their
>usages, and any other odd fact you'd want to find out about modules?"
>i.e. If the FS actually had a SQL store and modules were stored the way
>you suggested then you couldn't possibly write a SQL query (or stored
>procedure) that reasoned about modules in any decently easy way, form,
>or fashion.

That's right. The code to recognize a file as a module definition and
act on it is in the client, so Bill's hypothetical query would not be
able to use it. It would not know what was included in the module, so
it could not answer questions like "which files have changed in this
module since revision X?". This is a very basic question to ask of a
source control system. By putting the implementation into the client,
you limit its availability.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 17 14:59:15 2002

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.