svn commit: r1160645 - /subversion/trunk/subversion/include/private/svn_sqlite.h

[rh...@apache.org]

Author: rhuijben
Date: Tue Aug 23 12:06:38 2011
New Revision: 1160645

URL: http://svn.apache.org/viewvc?rev=1160645&view=rev
Log:
* subversion/include/private/svn_sqlite.h
  (svn_sqlite__with_lock): Update comment to match its implementation and
    usage.

Modified:
    subversion/trunk/subversion/include/private/svn_sqlite.h

Modified: subversion/trunk/subversion/include/private/svn_sqlite.h
URL: http://svn.apache.org/viewvc/subversion/trunk/subversion/include/private/svn_sqlite.h?rev=1160645&r1=1160644&r2=1160645&view=diff
==============================================================================
--- subversion/trunk/subversion/include/private/svn_sqlite.h (original)
+++ subversion/trunk/subversion/include/private/svn_sqlite.h Tue Aug 23 12:06:38 2011
@@ -373,13 +373,12 @@ svn_sqlite__with_immediate_transaction(s
 
 /* Helper function to handle several SQLite operations inside a shared lock.
    This callback is similar to svn_sqlite__with_transaction(), but can be
-   nested (even with a transaction) and changes in the callback are always
-   committed when this function returns.
+   nested (even with a transaction).
 
-   For SQLite 3.6.8 and later using this function as a wrapper around a group
-   of operations can give a *huge* performance boost as the shared-read lock
-   will be shared over multiple statements, instead of being reobtained
-   everytime, which requires disk and/or network io.
+   Using this function as a wrapper around a group of operations can give a
+   *huge* performance boost as the shared-read lock will be shared over
+   multiple statements, instead of being reobtaine everytime, which may
+   require disk and/or network io, depending on SQLites locking strategy.
 
    SCRATCH_POOL will be passed to the callback (NULL is valid).