Re: Consistent revision when retrieving from repository

On 10/18/05, Stuart Celarier <SCelarier@corillian.com> wrote:
> Thanks, Douglas. However, the aspect I'm interested in is the
> consistency of the retrieved items, not whether they are atomic for the
> client. (That could be viewed as the operation being an atomic read from
> the repository, which is how I got off on the wrong terminology.)
>
> Ben and others on the Subversion lists have said that Subversion
> provides this consistency: when retrieving from a single URL from the
> HEAD, all items will be from a single revision. Responses on the TSVN
> mailing list indicated this wasn't the case, and that TSVN does
> additional work to get around this (incorrectly?) perceived limitation
> of Subversion.

I'm sorry, but we've never said that Subversion wouldn't provide this
for single targets.
If you read my answer again, I specifically mentioned that Subversion
doesn't do that for multiple targets, while TSVN does. And I even
mentioned how TSVN achieves this.

And no, Subversion hasn't changed in that area. When the API was
extendet to take multiple targets as a parameter (i.e. to update
multiple targets at once), I suggested to implement it the same way as
TSVN does. But it wasn't done that way.

Here's the part of the svn_client_update2() API doc:

 * The paths in @a paths can be from multiple working copies from multiple
 * repositories, but even if they all come from the same repository there
 * is no guarantee that revision represented by @c svn_opt_revision_head
 * will remain the same as each path is updated.

Stefan

--
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org