Previously, the progress bar updated only after completing an entire table.
For large tables such as LIBARC, this could make the application appear to have stopped responding.
Phase 10 updates the interface while rows are being exported.
Previously, the progress bar updated only after completing an entire table.
For large tables such as LIBARC, this could make the application appear to have stopped responding.
Phase 10 updates the interface while rows are being exported.
Previously, the progress bar updated only after completing an entire table.
For large tables such as LIBARC, this could make the application appear to have stopped responding.
Phase 10 updates the interface while rows are being exported.
Previously, the progress bar updated only after completing an entire table.
For large tables such as LIBARC, this could make the application appear to have stopped responding.
Phase 10 updates the interface while rows are being exported.
Previously, the progress bar updated only after completing an entire table.
For large tables such as LIBARC, this could make the application appear to have stopped responding.
Phase 10 updates the interface while rows are being exported.
Previously, the progress bar updated only after completing an entire table.
For large tables such as LIBARC, this could make the application appear to have stopped responding.
Phase 10 updates the interface while rows are being exported.
Previously, the progress bar updated only after completing an entire table.
For large tables such as LIBARC, this could make the application appear to have stopped responding.
Phase 10 updates the interface while rows are being exported.
Previously, the progress bar updated only after completing an entire table.
For large tables such as LIBARC, this could make the application appear to have stopped responding.
Phase 10 updates the interface while rows are being exported.
Previously, the progress bar updated only after completing an entire table.
For large tables such as LIBARC, this could make the application appear to have stopped responding.
Phase 10 updates the interface while rows are being exported.
Previously, the progress bar updated only after completing an entire table.
For large tables such as LIBARC, this could make the application appear to have stopped responding.
Phase 10 updates the interface while rows are being exported.
Previously, the progress bar updated only after completing an entire table.
For large tables such as LIBARC, this could make the application appear to have stopped responding.
Phase 10 updates the interface while rows are being exported.
Previously, the progress bar updated only after completing an entire table.
For large tables such as LIBARC, this could make the application appear to have stopped responding.
Phase 10 updates the interface while rows are being exported.
Previously, the progress bar updated only after completing an entire table.
For large tables such as LIBARC, this could make the application appear to have stopped responding.
Phase 10 updates the interface while rows are being exported.
Previously, the progress bar updated only after completing an entire table.
For large tables such as LIBARC, this could make the application appear to have stopped responding.
Phase 10 updates the interface while rows are being exported.
Previously, the progress bar updated only after completing an entire table.
For large tables such as LIBARC, this could make the application appear to have stopped responding.
Phase 10 updates the interface while rows are being exported.
Previously, the progress bar updated only after completing an entire table.
For large tables such as LIBARC, this could make the application appear to have stopped responding.
Phase 10 updates the interface while rows are being exported.
Previously, the progress bar updated only after completing an entire table.
For large tables such as LIBARC, this could make the application appear to have stopped responding.
Phase 10 updates the interface while rows are being exported.
Previously, the progress bar updated only after completing an entire table.
For large tables such as LIBARC, this could make the application appear to have stopped responding.
Phase 10 updates the interface while rows are being exported.
Previously, the progress bar updated only after completing an entire table.
For large tables such as LIBARC, this could make the application appear to have stopped responding.
Phase 10 updates the interface while rows are being exported.
Previously, the progress bar updated only after completing an entire table.
For large tables such as LIBARC, this could make the application appear to have stopped responding.
Phase 10 updates the interface while rows are being exported.
Previously, the progress bar updated only after completing an entire table.
For large tables such as LIBARC, this could make the application appear to have stopped responding.
Phase 10 updates the interface while rows are being exported.
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.
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.
Mark Gregory