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

Are Updates and Checkouts also atomic?

From: Noah Spurrier <NoahS_at_SHARECHIVE.com>
Date: 2005-05-19 21:41:39 CEST

After I perform an "svn update" am I guaranteed
that every file in my local workspace all have
the same revision as the remote repository?
(Note, I understand that COMMITS are atomic.
This is a different question.)

We are considering using Subversion as a way
to distribute sets of files to clients.
The sets of files must all be updated to match
the repository or not at all. If the client
looses connection during an "svn update" operation
we want to be sure that the client does not have
some files from the current revision and some file
from the previous revision.

As far as I can tell Subversion uses transactions on
the server-side for updates, but this seems to be
used for locking the database to build diffs before
sending them down to the client.
It is not clear that updates are
an "all or nothing" operation on the client side.

If this is not the case, then it wouldn't be too hard
for us to wrap this feature around svn, but it would be nice
if we got this for free from Subversion.

Another idea would be to have the clients all run
Subversion servers with copies of the repository.
So to update the clients we would do an "svn commit" operation;
then have the client "svn update" from localhost. We can accept
the risk of assuming that "svn update" from localhost would never fail.
This process seems a bit convoluted.

Am I trying to shove a square peg in a round hole?
Is there a more obvious solution to this problem?

Yours,
Noah Spurrier

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 19 21:43:38 2005

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