From 7618294b16f2f421606a04df71b6afb6fb409fe6 Mon Sep 17 00:00:00 2001 From: Mark Gregory Date: Fri, 16 Oct 2026 22:06:56 +0100 Subject: [PATCH] The second file contains a SHA-256 checksum of the SQL backup. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This allows the application to detect whether the backup file has changed or become corrupted. 2. Verify Backup button The Import/Export window now includes Verify Backup…. Select an exported SQL file, and the application calculates its checksum and compares it with the accompanying checksum file. 3. Automatic verification before import When importing an SQL file, WorkbenchReplacement checks for an accompanying .sha256 file. If one exists, its checksum must match before SQL execution begins. Third-party SQL files without checksum files can still be imported. 4. Large-file handling Checksum calculation reads files in 1 MB blocks rather than loading the entire file into memory. This reduces memory usage when verifying large backups. --- PHASE8-NOTES.md => docs/PHASE8-NOTES.md | 0 PHASE9-NOTES.md => docs/PHASE9-NOTES.md | 0 2 files changed, 0 insertions(+), 0 deletions(-) rename PHASE8-NOTES.md => docs/PHASE8-NOTES.md (100%) rename PHASE9-NOTES.md => docs/PHASE9-NOTES.md (100%) diff --git a/PHASE8-NOTES.md b/docs/PHASE8-NOTES.md similarity index 100% rename from PHASE8-NOTES.md rename to docs/PHASE8-NOTES.md diff --git a/PHASE9-NOTES.md b/docs/PHASE9-NOTES.md similarity index 100% rename from PHASE9-NOTES.md rename to docs/PHASE9-NOTES.md