On 03/19/2012 02:24 PM, Philip Martin wrote: > "C. Michael Pilato" <cmpil...@collab.net> writes: >> Is this problem specific to the FSFS backend? > > Yes, I think it is. > > For BDB the dag_node_t type in dag.c doesn't have a node_revision > member. When update_ancestry does svn_fs_bdb__put_node_revision it > writes to the database and subsequent svn_fs_bdb__get_node_revision will > see the updated value. > > For FSFS the svn_fs_fs__put_node_revision call writes to the > transactions subdir but the in-memory node_revision doesn't get changed.
Gotcha. Thanks for the response. I remember when the BDB code had an in-memory node-revision structure and tried to maintain that using the trail construct. I remember also the day I purged the code of that mess. :-) -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
