Re: 'svn mv' between disjoint wc's of disjoint subtrees

Bert Huijben <bert_at_qqmail.nl> writes:

> We use a single transaction for moves within one db.
> (and a transaction on both dbs at the same time for multi db)

I think we use a single transaction for the copy half of the move, but
the whole move is two transactions with the delete half as the second
transaction. This is ugly because the move can be interrupted and then
a partial move is present in the database. I'd like to change:

      txn_to_copy
      rename
      txn_to_delete

into

      txn_to_copy_and_delete
      run_wq_to_rename

so that the problem goes away. Fundamentally that can't work with
disjoint working copies. I think move between disjoint working copies
will have to degrade to copy+delete, otherwise something like:

svn mv wc1/A wc2/B
svn up wc1

is going to have to update the disjoint wc2.

-- 
Certified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download