Mark Gregory
7618294b16
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.
949 B
949 B
Phase 9 — Native streamed table export
- Removes the non-null unique index requirement (including LIBARC).
- Uses a single MySQL SELECT result stream per table, within the existing dedicated InnoDB consistent-snapshot session.
- Does not use LIMIT/OFFSET and does not buffer complete table results or impose the SQL editor's 100,000-row limit.
- Uses optional unique-key ORDER BY when available, but supports tables without a unique key.
- Counts streamed rows and compares against snapshot row count.
- Existing SHA-256 verification and temporary-file cleanup remain in place.
Limitations: The SQL exporter still formats rows using MySQL SQL expressions; very large individual values and packet sizes may be limited by server/client protocol settings. Non-InnoDB tables are still rejected for data exports. DDL changes during backup are not protected. Streaming cancellation may wait for network reads. Not Xcode-built or live-server tested.