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

Re: Question about atomic commits and "tree locking".

From: Stephen Butler <sbutler_at_elego.de>
Date: Mon, 16 Jun 2008 09:38:10 +0200

Quoting Alfred Perlstein <bright_at_mu.org>:

> Hey guys,
> How does Subversion deal with checkouts/updates at the same time
> as a commit in in progress?
> example:
> If you are doing a commit, let's say over 5000 files on your
> file:///path/project/trunk, if someone does a checkout during
> this time, will they get "locked out" during this commit. Or
> does it use some sort of system so that the checkout can happen
> at the same time, but you get all-or-none?

You get all-or-none.

The new revision created by the commit is not "visible" to the
checkout command until the commit has successfully completed.

> How does Subversion deal with two commits at the same time?
> If the changesets don't collide, can they proceed at the same
> time?

Yes. If the changes overlap, the second commit will error out.

See the SVN Book for more details on transactions in the repository


The second chapter of the "Beautiful Code" book may also be of
interest to you.



Stephen Butler | Software Developer
elego Software Solutions GmbH
Gustav-Meyer-Allee 25 | 13355 Berlin | Germany
fon: +49 30 2345 8696 | mobile: +49 163 25 45 015
fax: +49 30 2345 8695 | http://www.elegosoft.com
Geschäftsführer: Olaf Wagner | Sitz der Gesellschaft: Berlin
Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-16 09:38:51 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.