Hence, porting SQLite to a new
operating system is simply a matter of writing a new OS interface layer
or "VFS".</p>
<h2>2.0 Multiple VFSes</h2>
<p>
The standard SQLite source tree contains built-in VFSes for os/2, unix,
and windows. Alternative VFSes can be
added at start-time or run-time using the
[sqlite3_vfs_register()] interface.
</p>
<p>
Multiple VFSes can be registered at the same time.
................................................................................
If no other actions are taken, new database connections will make use
of the default VFS.
</p>
<p>
The default VFS can be changed by registering or re-registering the
VFS using the [sqlite3_vfs_register()] interface with a second parameter
of 1. Hence, if a (unix) process to always use the "unix-nolock" VFS
in place of "unix", the following code would work:
</p>
<blockquote><pre>
sqlite3_vfs_register(sqlite3_vfs_find("unix-nolock"), 1);
</pre></blockquote>

Hence, porting SQLite to a new
operating system is simply a matter of writing a new OS interface layer
or "VFS".</p>
<h2>2.0 Multiple VFSes</h2>
<p>
The standard SQLite source tree contains built-in VFSes for unix
and windows. Alternative VFSes can be
added at start-time or run-time using the
[sqlite3_vfs_register()] interface.
</p>
<p>
Multiple VFSes can be registered at the same time.
................................................................................
If no other actions are taken, new database connections will make use
of the default VFS.
</p>
<p>
The default VFS can be changed by registering or re-registering the
VFS using the [sqlite3_vfs_register()] interface with a second parameter
of 1. Hence, if a (unix) process wants to always use the "unix-nolock" VFS
in place of "unix", the following code would work:
</p>
<blockquote><pre>
sqlite3_vfs_register(sqlite3_vfs_find("unix-nolock"), 1);
</pre></blockquote>

This page was generated in about
0.004s by
Fossil version [f8e26879ac] 2015-07-27 16:16:36