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

Re: svn commit: r11930 - in branches/locking/subversion: include libsvn_fs_base

From: <kfogel_at_collab.net>
Date: 2004-11-22 20:03:45 CET

"C. Michael Pilato" <cmpilato@collab.net> writes:
> I can attest to Karl's favoring of that idea (we had this conversation
> in the office the other day). My only concern was related to
> transportability of locks. *If* we extend our dumpfile format and
> backing code to handle lock transport, then we want our lock tokens to
> be backend-inspecific. So, my requirements for our tokens are that
> they use a consistent format across all the backends (either by
> sharing the id-generating code or by simply agreeing to a format, such
> as the above) and that they not be tied to the likes of an
> auto-incrementing primary key in a particular implementation (since at
> load-time we'd have to ensure that we got those same indexes again).

They can be tied to an auto-incrementing key, as long as it gets
preserved in dumps. (I'm not sure there's any other way to do it,
without just using UUIDs in the first place.)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 22 20:06:40 2004

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.