Mark Gregory
5948387b4e
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.
944 B
Phase 6 — SQL backup integrity
Adds streaming SHA-256 checksum creation for successfully exported SQL files, a Verify Backup… button, and automatic checksum validation before importing when a .sha256 sidecar is present.
The .sha256 file must be kept alongside the .sql file with the same basename. The verifier reads the SQL file in 1 MiB blocks rather than loading the file into memory. Third-party SQL imports without a sidecar are allowed.
Not yet implemented: transaction-consistent snapshots, reliable ordering of table rows across pages, import streaming, rollback on partial restore, cryptographic signing/authenticity, or end-to-end restoration tests. A matching SHA-256 proves file integrity relative to the stored checksum, not database completeness or correctness. Do not rely on this as a production backup system.
This Linux environment cannot run Xcode; build and live-MySQL testing are required on macOS.