Mark Gregory
0d0b46761f
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.
894 B
894 B
Phase 8 — Dedicated InnoDB snapshot exports
- Uses an isolated native MySQL session for the entire export.
- Starts a REPEATABLE READ consistent, read-only transaction.
- Rejects non-InnoDB tables when exporting data.
- Keeps the same session across all paginated reads and row-count checks.
- Closes the dedicated session on cancellation/failure (rolling back its transaction).
- Preserves all Phase 7 export, import and integrity features.
Limitations
This is NOT a full production backup guarantee: schema changes during export, non-transactional objects, and offset pagination remain limitations. A stable snapshot makes offset pagination consistent for InnoDB row data but not fast for large offsets. Backup and restore validation against live MySQL is still required. The MySQL wire protocol does not currently negotiate TLS, so do not send credentials over untrusted networks.