Softpedia >Windows >Portable Software >Database Utils >X-SQLyog Community >  Changelog

X-SQLyog Community Changelog

What's new in X-SQLyog Community 12.2.5 Rev 14

Aug 29, 2016
  • 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. In the BLOB-viewer we have added validation that content is valid JSON. Also JSON-related keywords and functions are recognized in syntax highlighting and autocomplete. Also please see note at the bottom.
  • 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.
  • Bug 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 our 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.

New in X-SQLyog Community 12.2.4 (Aug 29, 2016)

  • Bug Fixes:
  • Fixed a regression bug introduced in 12.2.3, that could have the result that various data dialogs displayed truncated or empty. Affected were “table diagnostics” and in some cases also Info, Data and Result tabs in text mode.

New in X-SQLyog Community 12.2.3 (Aug 29, 2016)

  • Features:
  • User Manager filter: when some characters are typed for user in User Manager first match with same starting characters will be selected.
  • Bug Fixes:
  • “Ignore Definer” did not work if “Drop Table if exist” and “Ignore Definer” both were ticked in cases where only procedures and/or functions were copied to another database.
  • The result of a multiline string in text mode displayed empty in case where the string started with a line break.
  • For “wide” BIT(n) types “0?-bits (even significant ones) could be truncated away due to a bug in a string conversion algorithm.
  • Miscellaneous:
  • The Plink executable shipped with the 64 bit installer is now a 64 bit binary. Before it was 32 bit.
  • The width of the dividers between the various panes of the SQLyog main window has been increased for better operability of resizing. This will be useful with touchscreens in particular.

New in X-SQLyog Community 12.2.2 (Aug 29, 2016)

  • Features:
  • The ‘date picker’ now has a GUI control to insert current date.
  • When running multiple statements in the editor and an error occured, SQLyog would continue to next statement. There is now an option to ‘halt on error’ in such cases.
  • Bug Fixes:
  • The `sys` database of MySQL 5.7 was erroneously backed up when choosing ‘all databases’ in the Scheduled Backup tool.
  • Tablel-level comments were truncated at 490 characters.
  • The ‘date picker ‘ calender could display distorted in DATA tab in some cases.
  • Miscellaneous:
  • MySQL username max-length in SQLyog connection settings has been increased from 16 to 32 characters, as MySQL 5.7 now allows for.

New in X-SQLyog Community 12.2.1 (Aug 29, 2016)

  • Bug Fixes:
  • Updates from RESULT tab could fail with MySQL 4.1 servers. The recent code changes in order to support MySQL 5.7 Virtual Columns overlooked that there is no Information_Schema database in MySQL 4.1 and a required condition could not be verified due to this.
  • In rare cases “copy database to a different host” option could generate incorrect statements and copying would fail with a ‘columns count mismatch’ error. Also this was introduced with code changes in order to support Virtual Columns in MySQL. Virtual columns did not need to be present in source for the error to occur.
  • Fixed a crash when copying table data to clipboard.
  • Miscellaneous:
  • Installer packages are now signed with a SHA2-hashed (and not SHA1 as before) certificate. Since recently Internet Explorer 11 has issued a security warning when installing from installer packages using a SHA1-hash with a build timestamp from Jan 1st 2016 or later. We were not aware of this policy-change by Microsoft when releasing SQLyog 11.1.9 and 12.2.0.

New in X-SQLyog Community 12.2.0 (Aug 29, 2016)

  • Bug Fixes:
  • Virtual Columns of MySQL 5.7 were not handled properly in ‘copy database to other host’.
  • .1.9 introduced a sluggishness when moving around the data GRID. In some cases it could be so bad that the program seemed to “hang” completely.
  • Miscellaneous:
  • Fixed inconsistent versioning. Earlier we could sometimes use format like “11.19? and sometimes “12.1.9?. We now consistently use the latter – like “12.2.0? with this release.

New in X-SQLyog Community 12.19 (Aug 29, 2016)

  • Features:
  • Virtual Columns support for MySQL 5.7 onwards (Virtual Columns with MariaDB were already supported). Please see note below for details.
  • SSL and SSH-tunnel are now not mutually exclusive. A SSL connection may now be established through an SSH-tunnel. This is in particular useful with various sorts of “private clouds” where connection to the cloud requires SSH and privacy of the cloud is enforced by using SSL for internal communication in the cloud.
  • Multiple files (.sql, .schemaxml, .queryxml) may now be opened in one operation in main editor window.
  • Bug Fixes:
  • When importing from some (not commonly used) external data sources using a WHERE-clause a SPACE was missing before the “WHERE” keyword causing an error. This is actually an issue with ODBC-drivers affected, but this release has a workaround.
  • In CREATE/ALTER TABLE dialog a default value could be specified for BLOB/TEXT columns. The server does not permit this and doing so will result in a server error. Now the GUI prevents it.
  • Fixed minor bugs with the Virtual Columns support for MariaDB.
  • Miscellaneous:
  • SQLite has been upgraded to version 3.10.0. This results in performance improvements (in autocomplete in particular).

New in X-SQLyog Community 11.2.4-0 [rev12] (Oct 23, 2013)

  • Bug fixes:
  • Fixed a memory corruption when accessing specific tables. In rare cases this could crash SQLyog. Only the 32 bit version was affected and only when using ‘compressed protocol’ for the connection.
  • LOAD DATA LOCAL could fail to import data from a data file using ‘Windows linebreaks’ (\r\n). This bug was introduced in 11.23 with the fix for non-ASCII characters in the file name.

New in X-SQLyog Community 11.0.0-2 [rev12] (Feb 19, 2013)

  • modified registry key exported