This release introduces a new major feature – ‘read-only’ connections – as well as Kerberos authentication support and a few bug fixes.

Changes as compared to MySQL GUI 12.3.3 include:

Features:

* Added an option for defining a connection as ‘read-only’.  There is a checkbox in the connection settings and when checked the title bar will inform user about the ‘read-only’ state. In ‘read-only’ state statements that write cannot be executed. For more details please see note at the bottom.
* Added support for the MariaDB auth_gssapi (Kerberos) plugin. This plugin is available with the latest 3.0 (alpha) Connector/C from MariaDB. But there seems to  be a huge popular demand for this already, and we have backported it to the 2.3 connector version we use in SQLyog.  Note that support …

This is a bug-fix release.  Please refer details below.

Changes as compared to SQLyog MySQL GUI 12.3.2 include:

Bug Fixes:

* Fixed an issue where Import External Data -jobs failed to authenticate SMTP.
* The sja.log would record syntax errors on recent servers if  Scheduled Backup was running with ‘Flush Master’ option. The generated backup file was OK. ‘Flush Master’ was deprecated in MySQL 5.6 and replaced with ‘Reset Master’. We now use ‘Reset Master’ with such servers.
* In email settings of Import External Data wizard it was possible to leave the subject empty.
* When re-ordering columns, an ON UPDATE -clause could be lost in specific cases.
* Fixed cases where index-level comments were not saved and …

This release fixes a few issues in the new GUI transactions supporting with specific and uncommon server settings.

Changes as compared to SQLyog MySQL GUI 12.3.1 include:

Bug Fixes:

* If an INIT_CONNECT setting in server configuration specified SET AUTOCOMMIT = 0 and global AUTOCOMMIT was 1 (or non-existent as in MySQL 4.1 and 5.0), the ‘transactions’ menu in SQLyog would incorrectly display AUTOCOMMIT as 1 after connection.
* Same code change as above also fixes a crash that could occur with 4.1 servers.
* Transactions support would fail to initialize with servers running global ANSI mode. SQLyog will not work in ANSI mode but connection and initialization should work, so that user as the first step may specify a supported session sql_mode (from the editor or from ‘advanced’ tab in connection …

This release fixes a rare crash as well as a regression bug introduced in 12.3.0.

Changes as compared to SQLyog MySQL GUI 12.3.0 include:

Bug Fixes:

* 12.3.0 introduced a slowness when displaying the saved connections list with a large no. (100+) of saved connections. This is fixed now.
* Fixed a rare crash occurring sometimes when typing in the editor inside an invalid query longer than 128 characters. Auto-complete was at fault.

Downloads: https://www.webyog.com/product/downloads
Purchase: https://www.webyog.com/shop

The post SQLyog MySQL GUI 12.3.1 Released …

This release introduces a new major feature – GUI transaction support – as well as some minor features and bug fixes.

Changes as compared to MySQL GUI 12.2.6 include:

Features:

* GUI transactions support. This new feature is available in Enterprise and Ultimate editions. Also please see note below.
* Added a tooltip on column headers in Data tab informing about column name, column type and length. In Result tab the tooltip will display column name only, as the result returned by MySQL does not have information of storage type details.
* Added GUI support for index-level comments in CREATE/ALTER TABLE.

Bug Fixes:

* Fixed an issue where GUI could ‘hang’ when executing queries with very large subqueries.
* Fixed an issue with the …

This release fixes two rare crashes and also we have upgraded the (MariaDB) C-connector to latest version (2.3.1). Most important this solves an issue when connecting to Amazon RDS using SSL. This was not possible before.

Changes as compared to MySQL GUI 12.2.5 include:

Bug Fixes:

* SQLyog was not able to connect to RDS instances using SSL encryption. Attempting to do so returned the error “Failed to connect to MySQL: SSL connection error: certificate verify failed”.
* After having a connection open for very long time, SQLyog could crash when closing this connection.
* Corrupted connection information in the ‘session restore’-database could cause a crash. We had one reproducible report of this, but please note that there is no indication that SQLyog itself caused the corruption. It may be due to a hardware error, for …

When I wrote this blog about “bash on Windows” a few days ago I omitted one issue, that I already knew about. This is because it needs some elaboration that did not ‘fit in’ the previous blog. So I will do it here.

It is about Unicode. Unicode always was a pain in “cmd” and with the arrival of “bash” in Windows, this has become more significant and important. Actually on any recent *nix platform user will not do anything to make Unicode work ‘out of the box’ in the console and display all or almost all scripts (though I have noticed that the completeness of the ‘monospace’ font mostly used in the Linux console varies between Linux distros – with …

When I wrote this blog about “bash on Windows” a few days ago I omitted one issue, that I already knew about. This is because it needs some elaboration that did not ‘fit in’ the previous blog. So I will do it here.

It is about Unicode. Unicode always was a pain in “cmd” and with the arrival of “bash” in Windows, this has become more significant and important. Actually on any recent *nix platform user will not do anything to make Unicode work ‘out of the box’ in the console and display all or almost all scripts (though I have noticed that the completeness of the ‘monospace’ font mostly used in the Linux console varies between Linux distros – …

With SQLyog MySQL GUI 12.2.5, JSON comes to SQLyog. This is a new and major thing.  Also, Foreign Key management with NDB tables was added and the user- filter was improved in the User Manager. Additionally, some non-critical GUI bugs were fixed.

Changes as compared to MySQL GUI 12.2.4 include:

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 …

With SQLyog MySQL GUI 12.2.5, JSON comes to SQLyog. This is a new and major thing.  Also, Foreign Key management with NDB tables was added and the user- filter was improved in the User Manager. Additionally, some non-critical GUI bugs were fixed.

Changes as compared to MySQL GUI 12.2.4 include:

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 …