diff options
| author | drh <> | 2024-10-15 14:00:29 +0000 |
|---|---|---|
| committer | drh <> | 2024-10-15 14:00:29 +0000 |
| commit | dcaae8fd4bb2831fd448c6b5c77885f0dcbcf947 (patch) | |
| tree | 133e811c29f5fd45b4082480fb72101bb494ee2f /src | |
| parent | 4924847cb9bfa0d2ff99b325a125bdf78c17cbb6 (diff) | |
| download | sqlite-dcaae8fd4bb2831fd448c6b5c77885f0dcbcf947.tar.gz sqlite-dcaae8fd4bb2831fd448c6b5c77885f0dcbcf947.zip | |
Cross-reference the sqlite3_backup_init() function to the documentation for
VACUUM INTO and sqlite3-rsync. Comment changes only. No changes to code.
FossilOrigin-Name: 405c23ce02cc7f970e732afc26e01d0267b8fa89d8edc3d53fae2b3bc8405cbb
Diffstat (limited to 'src')
| -rw-r--r-- | src/sqlite.h.in | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/src/sqlite.h.in b/src/sqlite.h.in index 5108d3c1e..6508b5439 100644 --- a/src/sqlite.h.in +++ b/src/sqlite.h.in @@ -9344,6 +9344,16 @@ typedef struct sqlite3_backup sqlite3_backup; ** APIs are not strictly speaking threadsafe. If they are invoked at the ** same time as another thread is invoking sqlite3_backup_step() it is ** possible that they return invalid values. +** +** <b>Alternatives To Using The Backup API</b> +** +** Other techniques for safely creating a consistent backup of an SQLite +** database include: +** +** <ul> +** <li> The [VACUUM INTO] command. +** <li> The [sqlite3-rsync] utility program. +** </ul> */ sqlite3_backup *sqlite3_backup_init( sqlite3 *pDest, /* Destination database handle */ |