On Wed, Sep 15, 2010 at 09:45, <julianfoad_at_apache.org> wrote:
> +++ subversion/trunk/subversion/libsvn_wc/wc-metadata.sql Wed Sep 15 13:45:12 2010
> @@ -618,6 +618,21 @@ PRAGMA user_version =
> BASE nodes and on top of other WORKING nodes, due to nested tree structure
> changes. The layers are modelled using the "op_depth" column.
> + An 'operation depth' refers to the number of directory levels down from
> + the WC root at which a tree-change operation (delete, add?, copy, move)
> + was performed. A row's 'op_depth' does NOT refer to the depth of its own
> + 'local_relpath', but rather to the depth of the nearest tree change that
> + affects that node.
> + The row with op_depth=0 for any given local relpath represents the "base"
> + node that is created and updated by checkout, update, switch and commit
> + post-processing. The row with the highest op_depth for a particular
> + local_relpath represents the working version. Any rows with intermediate
Strictly speaking: <wc_id, local_relpath>
We just happen to only ever have one wc_id value right now. In the
future, should one metadata store be used for multiple working copies,
then the wc_id value will become very meaningful.
Received on 2010-09-15 22:19:49 CEST