Find the attached patch.
Typo fixes to bdb repos doc on structure
Patch by: Kamesh Jayachandran <firstname.lastname@example.org>
'path' to 'lock-tokens' are maintained in lock-tokens table not
lock-nodes or locks-nodes table.
seems like File System summary for CHANGE-KIND missing 'reset'
as the 'changes' table describes above.
--- subversion/libsvn_fs_base/notes/structure (revision 18697)
+++ subversion/libsvn_fs_base/notes/structure (working copy)
@@ -605,12 +605,12 @@
the lock will cease to be valid. (see svn_time_to_cstring())
In addition to creating a lock in the `locks' table, a new row is
-created in a `locks-nodes' table. The `lock-nodes' table is a btree
+created in a `lock-tokens' table. The `lock-tokens' table is a btree
whose key is an absolute path in the filesystem. The value of each
key is a lock-token (which is a key into the `locks' table.)
To test if a path is locked, simply check if the path is a key in the
-`locks-nodes' table. To see if a certain directory has any locked
+`lock-tokens' table. To see if a certain directory has any locked
children below, we ask BerkeleyDB to do a "greater or equal match" on
the directory path, and see if any results come back. If they do,
then at least one of the directory's children is locked, and thus the
@@ -619,7 +619,7 @@
Locks are epheremal things, not historied in any way. They are
potentially created and deleted quite often. When a lock is
destroyed, the appropriate row is removed from the `locks' table.
-Additionally, the locked-path is removed from the `lock-nodes' table.
+Additionally, the locked-path is removed from the `lock-tokens' table.
@@ -883,7 +883,7 @@
CHANGE ::= ("change" PATH ID CHANGE-KIND TEXT-MOD PROP-MOD) ;
- CHANGE-KIND ::= "add" | "delete" | "replace" | "modify" ;
+ CHANGE-KIND ::= "add" | "delete" | "replace" | "modify" | "reset";
TEXT-MOD ::= atom ;
PROP-MOD ::= atom ;
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Mar 3 11:33:58 2006