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

RE: [PATCH] Fix for 1003, and URL stability

From: Bill Tutt <rassilon_at_lyra.org>
Date: 2002-12-04 02:40:09 CET

Well, I've updated the patch, tried to fix up the formatting goofs in
the patch, added a flag to open_path to allow some code paths to skip
this new code path, and updated the callers of open_path. (Although most
remaining callers of open_path who pass the flag should be calling
get_dag instead if possible.)

Now I've come to a crossroads. Should the data required by get_id_path
go into the changes table? (Which I've already done in the patch.) Or
should we change the schema to add a committed-path column to the
NodeRevision table? (Which I probably don't have time to do.)

Beside the reasons listed in 1003, an additional reason to fix this
issue is the entire DAV version URL stability thread that Greg Hudson
brought up a little while back.

This impacts the usefulness of HTTP caches for lazy parts of the
repository, and complicates the problem of adding an ACL system into

Any thoughts on how to proceed with this one? Either commit it because
we like the benefits for 1.0 and we don't want to change the schema
again, or attach the patch to the issue so that someone can accomplish
the schema change?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Dec 4 02:41:06 2002

This is an archived mail posted to the Subversion Dev mailing list.