dan
|
a3e4156745
|
Add test case to backup5.test to verify that detaching the destination database from its handle is handled correctly.
FossilOrigin-Name: 50cce4758361379f1585b30c619f2c9f7f8873dbfaeaec3ff357e26c1034546c
|
2026-06-25 10:36:51 +00:00 |
|
dan
|
1968870813
|
Avoid trying to delete a database file while it is still open in backup5.test.
FossilOrigin-Name: 395cbed103af08e3a4fafd9a3041205535e019d4aeb58b46c4a7e4f3bca545c9
|
2026-06-24 14:17:52 +00:00 |
|
dan
|
ade8954c40
|
Revert the fixes to backup in [1f940357f7] and [e5db80350c] and instead fix the problem reported by forum post [forum:15d82885e2 | 15d82885e2] (that a call to sqlite3_deserialize() after sqlite3_backup_init() but before the first call to sqlite3_backup_step() on the destination db of a backup could cause a crash) by deferring caching the pointer to the destination Btree until after it is locked. This addresses bug [bugs:/info/2026-06-24T08:41:13Z | 2026-06-24T08:41:13Z].
FossilOrigin-Name: 44a0f396daa13f382fd839cd8be49148aa24114968b97fed7f365307d1f8280a
|
2026-06-24 11:50:08 +00:00 |
|
dan
|
764881119d
|
Avoid a use-after-free problem that could occur if ATTACH statements are executed while a backup operation is active. Bug [bugs:/info/2026-06-23T15:46:48Z | 2026-06-23T15:46:48Z].
FossilOrigin-Name: 9454592878b5732d37d61f4541bd6f0c1f893c20fc833ce4c600f9470e62d6f2
|
2026-06-23 19:14:44 +00:00 |
|
dan
|
fad01993b7
|
Have calls to sqlite3_backup_init() fail if there is already a read or read-write transaction open on the destination database.
FossilOrigin-Name: 169b5505498c0a7ee2b5dbb2ba13c41dfaa7c62f
|
2014-11-13 14:18:25 +00:00 |
|