Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Clarification to the VACUUM INTO documentation. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
c7001012e1bd6f2b4de2d7e065e8a941 |
| User & Date: | drh 2019-02-05 12:58:26 |
Context
|
2019-02-05
| ||
| 16:45 | Update to the change log. check-in: f9f945c599 user: drh tags: trunk | |
| 12:58 | Clarification to the VACUUM INTO documentation. check-in: c7001012e1 user: drh tags: trunk | |
|
2019-02-01
| ||
| 22:06 | Fix typos and omissions in the change log. check-in: 91188df9ec user: drh tags: trunk | |
Changes
Changes to pages/lang.in.
5010 5011 5012 5013 5014 5015 5016 5017 5018 5019 5020 5021 5022 5023 |
<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() |
> > > > > > > > > > > > > |
5010 5011 5012 5013 5014 5015 5016 5017 5018 5019 5020 5021 5022 5023 5024 5025 5026 5027 5028 5029 5030 5031 5032 5033 5034 5035 5036 |
<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 filenames are 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() |