We simultaneously release SQLyog versions 8.32 (GA) and 8.4 beta1.

8.32 contains those fixes added since 8.3 that we consider GA quality.  Most of those were included in 8.31 beta1 already.  However for others we have decided that they will require more refinement or more testing before they will be included in a GA release.  Those are included with 8.4 beta1 along with new fixes  added after 8.31 beta1.  So for some time (a few weeks probably) there will be a stable tree (8.3x) and a development tree (8.4x).

Details for 8.32  (as compared to 8.3) are:

Bug Fixes:
* If ’all rows’ option for a table was selected in DATA tab this setting had effect when switching to a table that had never been viewed before. Consequently first selecting ‘all rows’ for a small table and next selecting a huge table could cause system memory exhaustion. This bug was introduced with the table-level row-number persistence in 8.22. Now a table that has never been opened before will be opened first time with the default LIMIT setting.
* First time a specific query was executed paging in RESULT tab (as introduced in 8.31 beta1) did not work properly for that query.
* If paging was disabled for RESULT tab the ‘rows in a range’ radiobutton was still selected (but ‘greyed out’ though).
* When printing from Schema Designer blank sheets could be printed if a table object was positioned close to the border of a page.
* Fixed (yet another) multimonitor issue.
* When a Query Builder tab was closed with an unchanged QB layout, SQLyog prompted if changes should be saved.
* If tables named identically except for lettercase existed in same database on a unix/linux server one of those tables would display data for the other table  in DATA tab.  The wrong table was specified in the query sent to MySQL. This bug was introduced in 8.0.
* Fixed a crash when copying data to clipboard from DATA tab using toolbar icon.
* Improved GUI in ‘Import External Data Tool’ wizard (explaining limitations with various Microsoft ODBC drivers).
* SQLyog connection manager required a user name, what prevented connection as a MySQL  ’anonymous user’.
* The automatic detection of what local port to use for SSH-tunneling (as introduced in 8.21) could in rare situations detect a port from where connection was not possible.
* Schema Sync could generate an invalid USE .. LIMIT … statement. This bug was introduced with paging in RESULT tab in 8.3.

Additionally 8.4 beta1 includes:

Features:
* Dumps created with ’scheduled backup’ can now be zipped. Note: the limitation with the archive file name in 8.31 beta1 has been lifted. Now the full unicode range can be used.
* ‘Notifications Services’ can now read queries from an external file.
* Added an option to send a mail alert if an error occurs while executing a ‘maintenance query’ from Notifications Services.
* In RESULT tab data can now be sorted by clicking on column headers like already possible in DATA tab. However note the difference as compared to sorting in DATA tab: in DATA tab we will send a SELECT .. ORDER BY .. query to MySQL – in RESULT tab we will sort inside the internal SQLyog data buffer. That means that for strings sorting in RESULT tab does not respect the collation defined for the data. Also all sorting on string values in RESULT tab is currently always case-insensitive (and note: this also applies to binary types: binary, varbinary and BLOB).
* ‘copy to clipboard’ and ‘export to CSV-file’ -settings are now independent.

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

Comments(0)

Changes (as compared to 3.72) include:

* If SHOW ENGINE INNODB STATUS returned an error that was not privilege-related, MONyog reported MySQL as non-available.  That could happen for instance if MySQL was started with –skip-innodb option. This bug was introduced in 3.71 with the support for InnoDB deadlock detection.
* A bug in the MONyog startup script could on Linux have the result that MONyog was still reported as running if it had been killed or had crashed.

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

Comments(0)

Changes (as compared to 8.3) include:

Features:
* Dumps created with ‘scheduled backup’ can now be zipped.  Note: there is one limitation with current implementation in this beta: the archive name is restricted to use characters from current ANSI codepage.
* ‘Notifications Services’ can now read queries from an external file.
* Added an option to send a mail alert if an error occurs while executing a ‘maintenance query’ from Notifications Services.
* In RESULT tab data can now be sorted by clicking on column headers like already possible in DATA tab. However note the difference as compared to sorting in DATA tab: in DATA tab we will send a SELECT .. ORDER BY .. query to MySQL – in RESULT tab we will sort inside the internal SQLyog data buffer. That means that for strings sorting in RESULT tab does not respect the collation defined for the data. Also all sorting on string values in RESULT tab is currently always case-insensitive (and note: this also applies to binary types: binary, varbinary and BLOB).

Bug Fixes:
* If  ’all rows’ option for a table was selected in DATA tab this setting had effect when switching to a table that had never been viewed before.  Consequently first selecting ‘all rows’ for a small table and next selecting a huge table could cause system memory exhaustion.  This bug was introduced with the table-level row-number persistence in 8.22.  Now a table that has never been opened before will be opened first time with the default LIMIT setting.
* When printing from Schema Designer blank sheets could be printed if a table object was positioned close to the border of a page.
* Fixed (yet another) multimonitor issue.

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

Comments(0)

Changes (as compared to 8.22) include:

Features:
* Added an option to define a ‘color code’ for a connection. The color will be used as background color in the Object Browser.
* A Query Builder session can now be saved and resumed.
* In Query Builder a table alias can be defined for any table by double-clicking the title bar of the table symbol.
* In RESULT tab results can now be retrieved page-wise. This is ON as default with this build with a defined LIMIT of 1000 rows. For a specific query user can change and for this specific query the setting is persistent across sessions. Also read ‘miscellaneous’ paragraph below.
* Added a context menu to Query Builder canvas.

Bug Fixes:
* Deleting a user would leave non-global privileges orphaned in the ‘mysql’ database. Now we use DELETE USER syntax if server supports.
* Also using EDIT USER dialogue to change host or user specifier for a user would not move non-global privileges. We have split the old ALTER USER dialogue into two: a EDIT USER and RENAME USER dialogue. The latter will use RENAME USER syntax if server supports.
* On Wine Data Sync could generate a malformed XML-string what would case Data Sync to abort.
* Fixed an issue where SSH-tunneling failed with public/private key authentication. Technically the fix is in the PLINK binary shipped with SQLyog.
* SJA failed to send notification mails if Yahoo SMTP servers were used. Note that the fix disables encryption option with Yahoo SMTP servers – but it won’t work anyway due to a non-standard SMTP implementation server-side.
* When importing data from a Universe ODBC-source string data could be truncated.
* The fix in 8.22 for the issue that horizontal scrollbar in GRID would sometime not appear was not complete. It could still happen.
* SQLyog will now trim trailing whitespaces in Connection Manager and Create object dialogs to avoid MySQL Errors..
* Opening a file from ‘recent files’ list could crash SQLyog if a Query Builder or Schema Designer tab was selected and the file specified was not a valid XML file for that tab. This bug was introduced in beta 1.
* When calling a Stored Procedure with more than one SELECT statement from ‘Notifications Services’ only one result set was sent by mail.
* The sja.log file had no line-breaks between what was recorded for two jobs.
* On multi-monitor system resizable dialogues could open on the wrong monitor. New implementation is like this: on multi-monitor systems main program dialogue and ‘first child dialogue’ (example: ALTER TABLE) will open where they were closed (if possible), second and higher child dialogues (example: table advanced properties) will always open on top of its ‘parent’ dialogue. Non-resizable dialogues (such as confirmation boxes) will always open on top of their ‘parent’.
* With multiple SSH-tunnelled connections open stopping and re-executing queries in multiple connections in a fast manner could crash SQLyog.
* If more than one comment occurred before a SELECT statement in the editor, the statement was not identified as a SELECT statement by the Query Profiler and the Query Profiler TAB would not display.
* We did not validate client-side if user checked atoincrement option for a bit column with Create/Alter table dialog.
* If an error occurred while renaming a trigger then trigger was lost as SQLyog was not recreating it back.
* Small GUI fixes.

Miscellaneous:
* The default LIMIT setting for DATA tab has been removed. The setting is not required since we introduced table-level persistence for number of rows displayed. The default for new tables that have not been opened before is 50 – but when user changes the value and next ‘refresh’es SQLyog will save the LIMIT for that particular table persistently across sessions. This in combination with page-wise display in RESULT tab results in a more uniform User Interface for DATA and RESULT tabs.

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

Comments(1)