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.
659 B
659 B
Phase 5 — Built-in MySQL routine and trigger export
Adds opt-in export of stored procedures, functions and triggers via SHOW CREATE, using DELIMITER directives compatible with the Phase 4 importer. Export requires relevant MySQL privileges. The export includes these objects only when table structure export is enabled. The existing schema/table/view selection is unchanged.
Limitations: not tested in Xcode or against a live MySQL instance; no consistent snapshot, deterministic pagination, or complete backup verification. Do not use as the only production backup. The importer executes individual statements and does not provide rollback on failure.