This maintenance release introduces a long requested feature – HEX-dumping of binary data – and adds a number of non-critical bug fixes.

Changes as compared to MySQL GUI 12.4 include:

Features:

* Added an option to HEX-dump binary data in Export as SQL and in Scheduled Backup.
* In read-only mode FLUSH-statements can now be executed from the GUI as well as editor, except for ‘FLUSH TABLE WITH READ LOCK’ (as we don’t allow acquiring explicit LOCKS in read-only mode).

Bug Fixes:

* On enabling HTTP, SSL or SSH checkbox in the connection manager, the checkbox wasn’t redrawn automatically. The checkbox were re-drawn only on hovering over them or switching to another tab in the connection window
* In Table Diagnostics, clicking on Analyse executed same query …

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 …

We are pleased to announce the release 1.0.16 of HoneyMonitor, our GUI for MySQL™ administration and monitoring.

In this release, available for immediate download, we have fixed many bugs and included several improvements.

We are working to release a RC version as soon as possible.

The following is the list of changes:

• New Features:
  • new Tab “Defaults Folders” in the “HoneyMonitor Options” Window to set the default folders to be used when storing Audit Reports, Standard Reports, HTML Reports, Queries, Backups, Scripts, Exported Data.
• …

We are pleased to announce the release 1.0.15 of HoneyMonitor, our GUI for MySQL™ administration and monitoring.

In this release, available for immediate download, we have fixed some bugs without adding many new features.

We are working to release a RC version as soon as possible.

The following is the list of changes:

- New Features:

1. new menu entry Auditing / Reports / Edit Report’s Template / Custom Report.

- Improvements:

1. minor bugs fix and improvements in the Report Designer.

- Bugs Fix:

1. on Vista™, the Report Designer was losing the connection after …