What's new in DumpCat 1.1.0

Restore onto another instance

• The restore form connects to the chosen server first and shows its version, flavor and the databases already on it, warns about every database that would be overwritten (not only on the source server), and lets you add a new target server without leaving the page.
• Compatibility options for logical restores to another instance or version, suggested from the target: remove DEFINER from views, routines, triggers and events; convert MySQL 8 utf8mb4_0900_*, MariaDB uca1400 and utf8mb3_* collations (MySQL 8 → MariaDB / 5.7 and back); skip SET @@GLOBAL.GTID_PURGED. Only schema statements are rewritten, row data is never changed; mydumper schema files are rewritten after extraction.
• Physical restores: choosing the instance now fills its datadir, service and owner, and the form warns when the target runs another version series or flavor.
• New API endpoint POST /api/runs/{id}/restore-check.

Fixes

• The GTID set of MySQL 8 mysqldump backups (GTID_PURGED=/*!80000 '+'*/ '…') is now recorded, so point-in-time recovery to a GTID can tell when the target is already inside the backup.

This is an older version: install the latest one from the install guide. DumpCat 1.1.0 itself stays available at https://downloads.dumpcat.cc/1.1.0/.