Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Merge changes from the 3.27 branch. |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
50513b6f28701a44250961e3cac434c9 |
| User & Date: | drh 2019-04-01 14:45:47.608 |
Context
|
2019-04-02
| ||
| 01:06 | Update the fts3_tokenizer() documentation to describe how it now wants parameters to be bound. (check-in: 30e7de5540 user: drh tags: trunk) | |
|
2019-04-01
| ||
| 14:45 | Merge changes from the 3.27 branch. (check-in: 50513b6f28 user: drh tags: trunk) | |
| 14:44 | Improvements to VACUUM documentation - describe more clearly when another transaction might block a vacuum. (check-in: 0f897a0268 user: drh tags: branch-3.27) | |
|
2019-03-29
| ||
| 16:41 | Fix spelling error in the previous check-in. (check-in: cfd3eb70b4 user: drh tags: trunk) | |
Changes
Changes to pages/lang.in.
| ︙ | ︙ | |||
5078 5079 5080 5081 5082 5083 5084 | named on the INTO clause in place of the temporary database and omits the step of copying the vacuumed database back over top of the original database. <p>^The VACUUM command may change the [ROWID | ROWIDs] of entries in any tables that do not have an explicit [INTEGER PRIMARY KEY]. </p> | | > > | > > > | 5078 5079 5080 5081 5082 5083 5084 5085 5086 5087 5088 5089 5090 5091 5092 5093 5094 5095 5096 5097 5098 | named on the INTO clause in place of the temporary database and omits the step of copying the vacuumed database back over top of the original database. <p>^The VACUUM command may change the [ROWID | ROWIDs] of entries in any tables that do not have an explicit [INTEGER PRIMARY KEY]. </p> <p>^A VACUUM will fail if there is an open transaction on the database connection that is attempting to run the VACUUM. ^Unfinalized SQL statements typically hold a read transaction open, so the VACUUM might fail if there are unfinalized SQL statements on the same connection. ^VACUUM (but not VACUUM INTO) is a write operation and so if another database connection is holding a lock that prevents writes, then the VACUUM will fail. <p>^(An alternative to using the VACUUM command to reclaim space after data has been deleted is auto-vacuum mode, enabled using the [auto_vacuum] pragma.)^ ^When [auto_vacuum] is enabled for a database free pages may be reclaimed after deleting data, causing the file to shrink, without rebuilding the entire database using VACUUM. ^However, using [auto_vacuum] can lead to extra database file fragmentation. ^And [auto_vacuum] |
| ︙ | ︙ |