Version History - 2019
SQLyog 13.1.5 (July 2019)
- Bug Fixes:
--On environments involving SSH-tunnel reconnection to the server could fail after timeout. This was caused by slightly different error reporting in some cases by the new MariaDB Connector/C v3.0 compared to v2.3, we used before SQLyog v13.1.3.
SQLyog 13.1.4 (June 2019)
- Bug Fixes:
--The encryption/decryption introduced in 13.1.3 overlooked that an encrypted binary string may contain a NULL-byte. As a NULL-byte in C and similar programming languages means “termination of a string” the stored password was not read fully and connection failed for specific passwords and -phrases affected. We now base64-encode the encrypted string and save the base64 value. For users that have already installed 13.1.3 this unfortunately means that passwords and phrases saved by 13.1.3 will need to be re-entered and connection saved again. We apologize for the inconvenience. However for users who upgraded to 13.1.3 from a previous version there is another workaround: the 13.1.3 installer created a backup of the pre-13.1.3 “sqlyog.ini” named “sqlyog_backup.ini”. This can be renamed to “sqlyog.ini” (ensure that program is not running and we recommmend creating a backup of both files before renaming).
SQLyog 13.1.3 (June 2019)
--With new connections saved by this release all passwords etc. saved in files (sqlyog.ini, XML-jobfiles, session restore database etc.) are now encrypted and not only “obfuscated” as before. Old saved connection details with obfuscated passwords will be re-encoded using encryption first time the respective connection is opened (however old SJA "jobfiles" will need to be recreated if encryption shall be used in the jobfile. A jobfile with an "oldstyle" obfuscated password will still work with this new program version). Please observe that, as a consequence of using true encryption, it is now technically impossible to “reverse engineer” a saved password to clear-text (what we sometimes have done for users earlier).--The “caching_sha2_password” authentication plugin (default in recent MySQL 8 servers) is now supported. This has been achieved by upgrading the MariaDB Connector/C from 2.3x to 3.0x. The same connector upgrade also solves a few rare issues with SSL and other rare connectivity issues.
--We updated the ‘keywords.db’ file (used for autocomplete and syntax highlighting) with new keywords and functions added in recent MySQL and MariaDB servers.
- Bug Fixes:
--“Duplicate Current Row” was unintentionally disabled (or “greyed out”) in SQLyog Community edition.--With MySQL 8.0.12+ Schema Sync displayed an extra ‘DEFAULT’ keyword for a table having a TIMESTAMP column with a default value. Older MySQL versions and MariaDB were not affected.
--Schema Sync displayed the CREATE VIEW query twice for Views on comparison. This is a regression bug introduced in SQLyog v13.1.2.
--SQLyog closed abruptly when executing a CREATE/ALTER TABLE statement using the GUI interface. This happened with MySQL v5.0.x and v5.1.x server versions only and is also a regression bug.