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

Re: svn commit: rev 6157 - trunk/notes

From: Branko Čibej <brane_at_xbc.nu>
Date: 2003-06-06 03:55:20 CEST

kfogel@tigris.org wrote:

>+ [Note from kfogel: Is there some reason we can't store successor
>+ nodes at commit time? That is if N is a director successor of M,
>+ then when we create N, we add it to M's "successors list". Then we
>+ could track forward as well as backward... Nothing against having
>+ an SQL backend someday, of course, just pointing out that this
>+ particular problem can be solved simply in Berkeley DB.]
No, there is no reason why we couldn't do that, and I think that
(long-term) we should. Also, note that a SQL back-end won't help one bit
here; this is a high-level schema issue; our schema simply doesn't
contain successor pointers, and a SQL back-end won't be able to add them
unless the FS DAG layer does the work.

Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 6 03:54:01 2003

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.