Update the sqlite3_vfs_register() documentation to make

the behavior undefined for VFSes with a NULL or empty string
as the name or with duplicate names. (CVS 4310)

FossilOrigin-Name: e7a98b48384ea581d98dad5118ee33468d526c62

1 files changed, 5 insertions, 2 deletions

diff --git a/src/sqlite.h.in b/src/sqlite.h.in
index 3b1af5e9c..032c0895b 100644
--- a/src/sqlite.h.in
+++ b/src/sqlite.h.in
@@ -30,7 +30,7 @@
 ** the version number) and changes its name to "sqlite3.h" as
 ** part of the build process.
 **
-** @(#) $Id: sqlite.h.in,v 1.244 2007/08/27 21:10:36 drh Exp $
+** @(#) $Id: sqlite.h.in,v 1.245 2007/08/28 15:21:45 drh Exp $
 */
 #ifndef _SQLITE3_H_
 #define _SQLITE3_H_
@@ -3238,7 +3238,10 @@ int sqlite3_blob_write(sqlite3_blob *, const void *z, int n, int iOffset);
 ** new VFS becomes the default VFS if the makeDflt flag is set.
 ** The same VFS can be registered multiple times without injury.
 ** To make an existing VFS into the default VFS, register it again
-** with the makeDflt flag set.
+** with the makeDflt flag set.  If two different VFSes with the
+** same name are registered, the behavior is undefined.  If a
+** VFS is registered with a name that is NULL or an empty string,
+** then the behavior is undefined.
 ** 
 ** Unregister a VFS with the sqlite3_vfs_unregister() interface.
 ** If the default VFS is unregistered, another VFS is chosen as