<p>
^The filename in the INTO clause can be an arbitrary SQL expression
that evaluates to a string.
^The file named by the INTO clause must not previously exist, or
else it must be an empty file, or the VACUUM INTO command will
fail with an error.
<p>
The VACUUM INTO command is transactional in the sense that
the generated output database is a consistent snapshot of the
orgininal database. However, if the VACUUM INTO command is
interrupted by a unplanned shutdown or power lose, then
the generated output database might be incomplete and corrupt.
Also, SQLite does not invoke fsync() or FlushFileBuffers()

<p>
^The filename in the INTO clause can be an arbitrary SQL expression
that evaluates to a string.
^The file named by the INTO clause must not previously exist, or
else it must be an empty file, or the VACUUM INTO command will
fail with an error.
<p>^The argument to INTO can a [URI filename] if URI filenamesare enabled.URL filenames are enabled if any of the following are true:<ul><li> The SQLite library was compiled with [-DSQLITE_USE_URI=1].<li> The [sqlite3_config]([SQLITE_CONFIG_URI],1) interfaces was invoked at start-time.<li> The [database connection] that is running the VACUUM INTO statement was originally opened using the [SQLITE_OPEN_URI] flag.</ul>
<p>
The VACUUM INTO command is transactional in the sense that
the generated output database is a consistent snapshot of the
orgininal database. However, if the VACUUM INTO command is
interrupted by a unplanned shutdown or power lose, then
the generated output database might be incomplete and corrupt.
Also, SQLite does not invoke fsync() or FlushFileBuffers()

This page was generated in about
0.012s by
Fossil 2.12 [16d68b0d4c] 2020-06-04 14:23:44