Re: Locking: repos upgrades?

On Fri, Nov 19, 2004 at 11:28:54AM -0600, Ben Collins-Sussman wrote:
>...
> 1. I seem to recall that when we added the 'uuids' table, there was
> some magic code that instantly created the table if not present. Do we
> need to repeat that technique?

Yeup.

> 2. Are we allowed to increment the 'format' file? I'd certainly like
> to. Otherwise, a process using libsvn_fs 1.1 can create a lock, but
> then a process using libsvn_fs 1.0 would silently ignore the lock
> without realizing it. Does incrementing 'format' break our
> compatibility promises?

I would say that you can increment it. A newer version can read all
old version repositories (and migrate forward as needed). An older
cannot read newer.

But I think that might be subject to argument. For example, on the
protocol side, we say that an old client against a new server just
doesn't get to use the new features. It might also be arguable that an
old FS implementation just can't use locking.

Personally, I think we stick to a strict "no dump/load to upgrade"
policy and allow that a repos can have its format changed to prevent
old FS libs from working with it.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org