This release ports a single critical bug fix from the newly released 8.55 release to the current 8.6 beta/development tree:  If user edited data in RESULT-tab GRID and changed from Edit Mode to Read Only mode without saving, the UPDATE statement would omit the proper WHERE-clause. As a consequence all rows would be updated. This bug was introduced in 8.4. All users using 8.4 or higher should upgrade due to this serious bug.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(3)

Changes (as compared to 8.54) include:

Bug Fixes:
* If user edited data in RESULT-tab GRID and changed from Edit Mode to Read Only mode without saving, the UPDATE statement would omit the proper WHERE-clause. As a consequence all rows would be updated. This bug was introduced in 8.4. All users using 8.4 or higher should upgrade due to this serious bug..
* Sorting and filtering on YEAR-type columns in RESULT tab did not work.  Now it works with YEAR(4), but with YEAR(2) it still does not with this release.
* A connection tab/window can now be closed even if there is only one connection (this fix is backported from 8.6 beta release).
* Fixed an issue with Schema Sync when source and target differed in both columns and Foreign Keys. Sometimes the ALTER script would only specify the FK-changes to target (also this fix is backported from 8.6 beta release).

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(0)

Changes (as compared to 8.54) include:

Features:
*User Management is completely redesigned and rewritten. Now privileges on all levels – as well adding/deleting/renaming users and changing passwords – are managed from the same interface – an expandable tree view. Also GRANT and REVOKE syntax is now used (before the MySQL privileges tables were manipulated directly).
* Added a ‘custom filter’ option in DATA and RESULT tab GRIDs. With this option, user can filter on any value from any cell.
* A connection tab/window can now be closed even if there is only one connection

Bug fixes:
*In text-mode, columns in DATA and RESULT tab would not align properly with non-ASCII characters. We were basically counting bytes – not characters. This is now fixed. But note that alignment issues may still happen in special cases with some non-western scripts in cases where the font itself prints more characters with the width of a single character.
* Fixed an issue with Schema Sync when source and target differed in both columns and Foreign Keys. Sometimes the ALTER script would only specify the FK-changes to target.
* Fixed some bugs when migrating default values from SQL server using Import External Data. Issues were occurring with specific default values and datatypes.
* Terminating a job from SJA wizards was not killing the PLINK process used for SSH-tunneled connection.
* The dialog for defining ENUM/SET properties only appeared after clicking the ‘length’ cell from CREATE/ALTER TABLE. Now it pops up as soon as user has selected the ENUM/SET type.
*The output in the MESSAGES tab is restructured to make the output more readable when multiple queries are executed.
* Other small GUI fixes.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(4)

Changes (as compared to 8.53) include:

Bug fixes:
* With many servers/connections registered in SQLyog the drop-down list in the connections dialog would flicker. The flickering was introduced in 8.5.
* Query Formatter was not handling queries of size greater than 2 KB. Now the size is increased to 8 KB. The 2 KB limitation was introduced in 8.18.
* Import of data from .xlsx files from Excel 2007+ was failing with double-precision datatypes.
* Update-check failed if SQLyog was running behind a HTTP-proxy.  The settings will now be detected.  However proxies requiring authentication are not handled with this release.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(0)

Important note: Please note that if you have installed a MONyog 4.0 (beta) release you cannot install this one unless first completely removing the 4.0 installation including the complete MONyog data folder.

Changes (as compared to 3.76) include:

Bug Fixes:
* Fixed an issue with SQLite where incorrect handling of journal files could lead to corruption of the MONyog embedded database .

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(0)

Important note: Please note that a 4.0 release cannot be downgraded to 3.x as the database schemas are incompatible and the installer will not handle downgrades – only upgrades. However you can install this 4.0 beta 2 on top of any previous release.

Changes (as compared to beta1) include:

Features:
* Added an option to compare server configurations. This feature enables the user to compare changes in configuration between two instances of MySQL. Through this feature the user will gain a greater insight on why one server is performing better than the other as far as server configuration is concerned.
* Also changes in server configurations are tracked and recorded by MONyog. This feature enables users to track changes to global configuration of a MySQL server over a period of time and compare changes between revisions.

Bug Fixes:
* Monitors/Advisors Customization: The Group Name of a Monitor/Advisor can now be changed only when a new, custom, counter is created; once set it cannot be changed. Changing Group Names of Monitors/Advisors shipped with MONyog is not allowed.
* Helper functions’ migration: User-defined helper functions were not being migrated in 4.0 Beta 1. If the user wrote his/her own function to use in his/her custom Monitors/Advisors, he or she would lose all changes upon upgrading. Now all helper functions are migrated transparently.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(0)

Bug fixes:

• SJA was always using port 22 to connect to SSH, but now any valid SSH port can be used to establish connection with MYSQL server using SSH.
• Fixed a PLINK crash which was introduced in SQLyog 8.5.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(0)