From 62106fba0abbb890833778036406cac345d5ca20 Mon Sep 17 00:00:00 2001
From: Boris Kolpackov
Date: Thu, 6 Sep 2012 14:36:20 +0200
Subject: Add ability to specify SQLite vfs module in database constructor
---
doc/manual.xhtml | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
(limited to 'doc')
diff --git a/doc/manual.xhtml b/doc/manual.xhtml
index adcc45a..26d9d38 100644
--- a/doc/manual.xhtml
+++ b/doc/manual.xhtml
@@ -13982,6 +13982,7 @@ namespace odb
database (const std::string& name,
int flags = SQLITE_OPEN_READWRITE,
bool foreign_keys = true,
+ const std::string& vfs = "",
std::[auto|unique]_ptr<connection_factory> = 0);
database (int& argc,
@@ -13989,6 +13990,7 @@ namespace odb
bool erase = false,
int flags = SQLITE_OPEN_READWRITE,
bool foreign_keys = true,
+ const std::string& vfs = "",
std::[auto|unique]_ptr<connection_factory> = 0);
static void
@@ -14031,7 +14033,11 @@ namespace odb
argument specifies whether foreign key constraints checking
should be enabled. See Section 14.5.3,
"Foreign Key Constraints" for more information on foreign
- keys.
+ keys. The vfs
argument specifies the SQLite
+ virtual file system module that should be used to access the
+ database. If this argument is empty, then the default vfs module
+ is used. Again, refer to the sqlite3_open_v2()
function
+ documentation for detail.
The following example shows how we can open the test.db
database in the read-write mode and create it if it does not exist:
--
cgit v1.1