* ch03-advanced-topics.xml

  (svn.advanced.locking.meanings): Add "SQLite locks" and
    a comment about mutexes.

Patch by: Daniel Shahaf <d.s{__AT__}daniel.shahaf.name>

git-svn-id: https://svn.code.sf.net/p/svnbook/source/trunk@6051 b70f5e92-ccc6-4167-9ab2-d027528d294b

diff --git a/en/book/ch03-advanced-topics.xml b/en/book/ch03-advanced-topics.xml
index 5d85b13..b182f33 100644 (file)
--- a/en/book/ch03-advanced-topics.xml
+++ b/en/book/ch03-advanced-topics.xml
@@ -4057,12 +4057,25 @@ $
         <indexterm>
           <primary>locks</primary>
           <secondary>svnrdump</secondary>
-        </indexterm>Finally, there are <firstterm>svnrdump
+        </indexterm>Next, there are <firstterm>svnrdump
         locks</firstterm>.  These are very much like svnsync locks, but
         are associated with the <command>svnrdump load</command> command
         (described in <xref linkend="svn.reposadmin.maint.migrate.svnrdump"
         />) instead of <command>svnsync</command>.</para>
 
+      <para>
+        <indexterm>
+          <primary>locks</primary>
+          <secondary>SQLite</secondary>
+        </indexterm>Finally, there are <firstterm>SQLite
+        locks</firstterm>.  These are used by the SQLite library (<ulink
+        url="https://www.sqlite.org/" />) to serialize access to SQLite
+        databases used by Subversion under the hood.  See, for example,
+        the <literal>exclusive-locking</literal> option in <xref
+        linkend="svn.advanced.confarea.opts.config" />.</para>
+
+      <!-- No need to mention svn_mutex__t at this time. -->
+
       <para>You can generally forget about these other kinds of locks
         until something goes wrong that requires you to care about
         them.  In this book, <quote>lock</quote> means the first sort