What's new
Support for dumping MySQL EVENTs. You can now dump MySQL EVENTs on top of the existing support for TABLEs, VIEWs, PROCEDUREs, FUNCTIONs, and TRIGGERs. The database backup engine is also smarter, allowing you to dump TABLE/VIEWs, PROCEDUREs, FUNCTIONs, TRIGGERs, and EVENTs with identical names.
Improved database dump engine. The database engine got revamped. You can now back up MySQL Events. It is now possible to back up procedures, views, and triggers which have the same name as a table or view. Foreign keys constraints, as well as table references in views are now resolved more precisely using the database's INFORMATION_SCHEMA, and a dependency graph resolver. The result is a more accurate backup of large, complex databases with lots of interlinked tables and views at the expense of a slight overall speed decrease of the database backup.
More accurate information about PHP CLI in the Schedule Automatic Backups page. We are now automatically detecting the best path to the PHP CLI executable instead of using the generic /path/to/php placeholder. On most local and live servers this will now return a completely accurate command line you can copy and paste directly to your host's CRON management tool, or your SSH session, without having to ask your host what the path to the PHP CLI executable is. Yay, simplicity!
Multi-row select and row show/hide in the Manage Backups and Profiles pages. We have fixed an integration issue with Joomla which prevented this feature from working. You will now be able to select multiple rows at once by clicking on the first row and then SHIFT-clicking on the last row. For discontinuous selection you can use CTRL-click (Windows, Linux) or CMD-click (macOS).
Bug fixes and minor improvements. Please take a look at the CHANGELOG below.
Changelog
Critical bugs and important changes
- Could not work with MySQL 5.x and MariaDB 10.x
