Verify SQLite backups and restores
This commit is contained in:
parent
4d5eb22e66
commit
030f18aeb0
7 changed files with 205 additions and 22 deletions
|
|
@ -328,6 +328,9 @@ Implemented foundation:
|
|||
- SQLite foreign-key enforcement is enabled explicitly for every context
|
||||
- the distribution-board repository receives its database dependency explicitly
|
||||
- distribution-board setup has real in-memory SQLite commit and rollback coverage using production migrations
|
||||
- database backups use SQLite's online backup API and include committed WAL data
|
||||
- every backup is opened independently and checked for integrity and foreign-key violations
|
||||
- an integration test restores the backup into a separate database and verifies its snapshot contents
|
||||
- circuit-device-row creation/deletion and reserve-state changes use an explicitly injected transaction store
|
||||
- a new circuit and all of its initial device rows use the same transaction store
|
||||
- device-row moves, reserve-state updates and optional target creation share one transaction
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue