SQLyog Community Edition full changelog

Features:
SQLyog now supports TLS 1.3 encryption for SSL connections.
SQLyog now supports the newly added collations in MariaDB version 10 and later above.
Added support for the new datatypes INET4, INET6, UUID in MariaDB version 10 and above.
Bugs:
With MariaDB v11.1 and above, the bug preventing data insertion by displaying an empty drop-down list and by clicking on the same leading to truncation of the existing data is fixed.

Features:
It is now optional if Schema Sync should synchronize the InnoDB Row Format -setting for tables or not.
Bug Fixes:
The setting in Query Profiler ‘preferences’ to include EXPLAIN EXTENDED is now ignored, if server does not support this (what is the case with MySQL from 5.7.4 – but not any MariaDB version).
Miscellaneous:
The “keywords.db” file (used by syntax highlighting, autocomplete and automatic lettercase handling for functions and keywords) was updated with new keywords and functions related to JSON, Roles, Common Table Expressions and Window Functions as of both MySQL 8.0 and MariaDB 10.3.

This maintenance release upgrades the MariaDB Connector/C to version 2.3.3 (current). Versions before this could time out incorrectly on some environments (and for unclear reasons). Affected in particular was Windows 8, but also all Windows versions running in a virtualized environment could be.

Features:
‘session restore’ will now also restore the current default database for every connection to what is was when the program was closed.
Added options to save and open session savepoints manually. The options are added to the file menu. This is working independently of the automatic session restore feature. With this it is possible to have a number of session savepoints for different use cases saved to the system.
When one or more connections saved in a session savepoint failed to open, the connections were discarded. When the program was closed next time the automatic session savepoint would be overwritten, and all queries, schema designs and query designs belonging to affected connections would be lost. Now, when a connection fails, a copy of the automatic session savepoint file will be created and user will be prompted to copy it for future use (using the new option to open a savepoint manually).
‘copy database’ now has an option to create the target database.

Features:
‘session restore’ will now also restore the current default database for every connection to what is was when the program was closed.
Added options to save and open session savepoints manually. The options are added to the file menu. This is working independently of the automatic session restore feature. With this it is possible to have a number of session savepoints for different use cases saved to the system.
When one or more connections saved in a session savepoint failed to open, the connections were discarded. When the program was closed next time the automatic session savepoint would be overwritten, and all queries, schema designs and query designs belonging to affected connections would be lost. Now, when a connection fails, a copy of the automatic session savepoint file will be created and user will be prompted to copy it for future use (using the new option to open a savepoint manually).
‘copy database’ now has an option to create the target database.

Includes all the changes featured in the previous Beta versions

Features:
'session restore' now saves and restores content of open Query tabs.
As a consequence user is not prompted to save open Query tabs when the program is closed and 'session restore' is enabled. User is still prompted when closing an individual tab.
With 'session restore' enabled, session is now also saved automatically in the background every 10 seconds.
A Query tab can be renamed (from the context menu of the tab itself). 'session restore' will open the tab with the user-defined name.
Added the HTTP content-type 'application/xml' as an option for HTTP tunnel.
Import external data will now create tables with the database collation of the database imported to, provided that database charset is utf8. Note that we cannot do this if database charset is not uft8 as imported tables are always created as utf8 and comparable collations do not always exist for unicode and non-unicode charsets in MySQL.
Bug fixes:
Fixed a crash when executing a single bracket ( “(” ) as a statement.

Upgraded libraries that theoretically could be vulnerable to the ‘Heartbleed’ OpenSSL bug. All users are urged to upgrade as soon as possible.

Features:
Added support (in syntax highlighting and autocomplete) for a number of keywords added in recent MySQL versions.