Released: Aug 19, 2016

Updates in v12.2.5

Updates in v12.2.5

Features:

• Added basic support for the JSON datatype as of MySQL 5.7.8+ and MySQL Cluster 7.5.2+. The datatype is now available in the CREATE/ALTER TABLE dialog and JSON data will open in the BLOB-viewer. The BLOB-viewer validates the content is valid JSON. Also JSON-related keywords and functions are recognized in syntax highlighting and autocomplete.
• SQLyog GUI now supports Foreign Key constraints between NDB tables for MySQL Cluster 7.3+.
• It is now possible to filter the users based on a string in the drop-down list in the ‘User Manager’. It is similar to filtering the tables, databases and connections, and an improvement to the filter in previous versions.

Fixes

• In “Backup Database as SQL Dump” when selecting ‘Data Only’ option, it was possible to select objects not containing data. This case is now handled more intuitive.
• At the bottom of the Object Browser there is a notification area (used for various purposes including security alerts, marketing campaigns etc). If SQLyog – for any reason – could not access the Webyog server checking for available notifications, the message “Internet access is restricted from this computer” would appear. It disturbed some users and does not display now.
• MySQL allows the columns with TIMESTAMP and DATETYPE datatypes to set the value to NULL, even if the column is defined with ’NOT NULL’. When set to NULL, MySQL will replace NULL with the CURRENT_TIMESTAMP value. Therefore it is now possible to select the option ‘Set To NULL’ for such columns by right clicking on the cell in the ‘Table Data’.
• When SQLyog restored the session after closing and reopening, editor tabs sometimes displayed editor line numbers only partially or otherwise incorrect as long as the tab did not have focus. This is now fixed.
• When pasting SQL templates for a table (from menu .. edit .. Insert Templates), INSERT and UPDATE query listed the virtual/generated columns in the template. This has now been removed from the templates.
• When deleting a connection tab the focus was not handled correctly in some cases, where it would highlight one connection tab and display the contents of another connection tab.
• CREATE/ALTER TABLE omitted a SPACE-character before the comment on a TIMESTAMP ON UPDATE CURRENT_TIMESTAMP column if a comment was specified, and the statement would fail.