Version History - 2014

SQLyog 12.04 (December 2014)

  • Features

    -- Added support for the ‘clear-text plugin’ (used by Oracle/MySQL LDAP authentication) and the ‘dialog plugin’ (used for MariaDB PAM authentication). Unlike the LDAP support available in early 11.x versions there is no user setting for either. SQLyog will transparently for user detect how to communicate with the server during authentication.Data Sync will now run in a single transaction using REPEATABLE READ transaction isolation mode on source.
    -- It is now possible to save current setting of Visual Data Compare in a job file. This job file will be compatible with Data Sync (ie. a job file generated by one may be used with the other and vice versa).
    -- ‘copy database/table(s) ‘ now has an option to copy triggers defined ON tables selected for copy.

  • Bug Fixes

    -- Fixed a rare crash caused by ‘session restore’ code. It could happen when executing a LOAD DATA LOCAL statement, for instance. Only Windows 8.1 was affected (+ some Wine beta version(s) according to user reports, that we were never able to reproduce).

SQLyog 12.03 (November 2014)

  • Features

    -- Data Sync will now run in a single transaction using REPEATABLE READ transaction isolation mode on source.

  • Bug Fixes

    -- The fix in 12.02 related to (DATE)TIME datatypes using fractional seconds was not complete. In some cases Schema Sync could still add quotes where it should not.
    -- If the target for Schema sync differed from the currently selected database in the main program dialog, inconsistent database name could display in some cases. A consequence was that SQLyog mistook what was the current active database and SQLyog GUI would keep showing incorrect active database afterwards, until it was changed.
    -- In Schema Sync some items could incorrectly be blue-colored and redundant statements would be generated for those affected.

SQLyog 12.02 (October 2014)

  • Features

    -- exports to CSV and Excel XML can now optionally include BOMs (Byte Order Marks) or not. Before this, BOMs were not an option. Some Windows programs will require BOMs in order to recognize the encoding as UTF8.

  • Bug Fixes

    -- The fix in 11.3 for databases named identically except for lettercase would fail in some cases. One such case was if database default charset was utf8mb4.
    --The checkbox in CREATE/ALTER TABLE dialog for setting ON UPDATE CURRENT_TIMESTAMP failed for TIMESTAMP and DATETIME columns using fractional seconds.
    --Also in in CREATE/ALTER dialog, for TIMESTAMP and DATETIME columns using fractional seconds a default specified as CURRENT_TIMESTAMP(n) (with ‘n’ being a number in the range 1..6) was incorrectly ‘quoted’ and thus failed.
    --The checkbox in CREATE/ALTER TABLE dialog for setting ON UPDATE CURRENT_TIMESTAMP failed for TIMESTAMP and DATETIME columns using fractional seconds. MySQL 5.6+ from Oracle was affected. MariaDB 10 was not.

SQLyog 12.01 (August 2014)

  • Bug Fixes

    -- Version 12.0 introduced a bug where the copy options from the icon bar did not function. Same functionalities from menu and context menu were not afffected.

SQLyog 12.0 (August 2014)

  • Features

    -- In addition to UTF8, exports to CSV and Excel XML can now be written with a number of non-unicode charsets/encodings. Note that in the SQLyog interface we identify those with their “MySQL name” and not what they may be termed in other contexts (‘latin1' and not ‘ANSI/Western’ for instance).
    -- The CREATE/ALTER TABLE dialog now has a column of checkboxes where the “ON UPDATE CURRENT_TIMESTAMP”-clause can be specified by user for TIMESTAMP columns and also for DATETIME columns if the server connected to is 5.6+.
    -- DATA and RESULT tabs can now be ‘unsorted’ from a selection in the context menu. This is in particular useful if you have sorted on multiple columns . In this case ‘unsorting’ could be a little tricky.

  • Miscellaneous

    -- The title bar now displays if SQLyog running is a 32 bit or 64 bit version.
    -- Added the keyboard shortcut F4 for CREATE (table/view/stored procedure/stored function/trigger/events/index depending on current Object Browser selection).

SQLyog 11.52 (July 2014)

  • Features

    -- 'session restore' will now also restore the current default database for every connection to what is was when the program was closed.
    -- Added options to save and open session savepoints manually. The options are added to the file menu. This is working independently of the automatic session restore feature. With this it is possible to have a number of session savepoints for different use cases saved to the system.
    -- When one or more connections saved in a session savepoint failed to open, the connections were discarded. When the program was closed next time the automatic session savepoint would be overwritten, and all queries, schema designs and query designs belonging to affected connections would be lost. Now, when a connection fails, a copy of the automatic session savepoint file will be created and user will be prompted to copy it for future use (using the new option to open a savepoint manually).
    -- 'copy database' now has an option to create the target database.

  • Bug Fixes

    -- Wrong execution time could display in MESSAGES tab.

SQLyog 11.51 (June 2014)

  • Features

    -- Query Builder and Schema Designer tabs are now handled by 'session restore' exactly the way that Query tabs were in 11.5.

  • Bug Fixes

-- In a multimonitor setup SQLyog was always opening in the primary monitor if closed in maximized state.
-- In Schema Sync altering an Event could generate an incorrect query.
-- Recent files were not displayed in file menu. This bug was introduced in version 11.5.
-- 'session restore' would not always open connection tabs in same order as was the case when program was closed. This happened if user had re-organized the tab-order manually.
-- Saved SQL files were not being marked as dirty when edited after it was restored by 'session restore'. -- When the content of an editor tab had just been saved as a file before closing the program, 'session restore' would sometimes not save and restore that particular tab.
-- If SQLyog was closed with no connections open, 'session restore ' would still restore the last connection that was open.

  • Miscellaneous

    -- Upgraded the linked OpenSSL library to version1.0.1h (OpenSSL is used for SSL-connections - not for SSH tunnel).

SQLyog 11.5 (May 2014)

  • Features

    -- 'session restore' now saves and restores content of open Query tabs and History tabs. As regards History tab the content will not be allowed to grow beyond 50,000 queries.
    -- As a consequence user is not prompted to save open Query tabs when the program is closed and 'session restore' is enabled. User is still prompted when closing a single connection tab or a single query tab.
    -- With 'session restore' enabled, session is now also saved automatically in the background every 10 seconds.
    -- A Query tab can be renamed (from the context menu of the tab itself). 'session restore' will open the tab with the user-defined name.
    -- Added the HTTP content-type 'application/xml' as an option for HTTP tunnel.
    -- Import external data will now create tables with the database collation of the database imported to, provided that database charset is utf8. Note that we cannot do this if database charset is not uft8 as imported tables are always created as utf8 and comparable collations do not always exist for unicode and non-unicode charsets in MySQL.

  • Bug Fixes

-- Fixed a crash when executing a single bracket ( "(" ) as a statement.
-- Import External Data could fail when creating indexes on imported TEXT columns as the tool did not specify the mandatory index prefix length.

  • Miscellaneous

    -- The HTTP-tunneler has been updated with this release and users making use of HTTP tunnel must update the tunneler on their MySQL host. The previous tunneler - released with SQLyog 8.8 more than 3 years ago - used the function 'set_magic_quotes_runtime()' that has been deprecated for some time in recent PHP versions. Till now we have suppressed any errors resulting from this, but this is a permanent solution.

SQLyog 11.42 (April 2014)

  • Miscellaneous

    -- Version 11.41 introduced a dependency on the shared library 'msvcr100.dll' (installed with the 'VC++ 2010 SP1 redistributable' from Microsoft). Users that do not upgrade regularly from Windows Update for any reason (including company policies) could experience that the program failed to launch with a message about the missing .dll. This dependency has now been removed.

SQLyog 11.41 (April 2014)

  • Miscellaneous

    -- Upgraded libraries that theoretically could be vulnerable to the 'Heartbleed' OpenSSL bug.

SQLyog 11.4 (March 2014)

  • Features

    -- Added a notifications area appearing in the lower part of Object Browser area. This will be used to communicate important information to users (example: critical bugs affecting version currently used). When no notifications are available or when there is no Internet connection to the notifications service, the area will not display.
    -- In Copy database, Export as SQL-Dump, Scheduled Backup and Schema Sync there is now an option to ignore/omit DEFINER-clause for database objects where it applies. Note that the target server will then create DEFINER as current SQLyog user when creating the object.
    -- Added fractional seconds support for relevant data types if server supports (MySQL does from 5.6.4 and MariaDB does from 5.3) in CREATE/ALTER TABLE as well as in 'Import External Data'.

  • Bug Fixes

    -- Since version 11.0 SQLyog failed to read theme files other than the default 'twilight' theme.
    -- Copying into clipboard from MESSAGES tab could result in garbage characters.
    -- SSH usernames and passwords with a doublequote character were not escaped properly.

SQLyog 11.33 (February 2014)

  • Bug Fixes

    -- Import External Data would map Oracle VARCHAR2 types to unneccesarily wide MySQL VARCHARs
    -- Very long LONGBLOB/LONGTEXT values could fail to copy and export. This bug was introduced in 11.2.
    -- If a CHUNK setting was specified 'copy table/database' would only copy the number of rows specified as the CHUNK. This bug was introduced in 11.31.
    -- In exported HTML style tags were not always closed properly.
    -- No tooltip hovered for the 'execute query' icon.

SQLyog 11.32 (January 2014)

  • Bug Fixes

    -- If SQLyog was started with the -dir switch, SJA running from the GUI wizards could fail to access the temporary jobfile it had generated itself and the job would abort.
    -- Excel files using .xlsm and .xlsb file formats were not detected by default in Import External Data.
    -- With specific server settings for .lower_case_table_names and specific lettercases used for creation of databases, routines (stored procedures and stored functions) would sometimes not display in the Object Browser. This was introduced in version 11.3. The underlying reason is an inconsistency in MySQL as the server returns the database name with different lettercases from different statements (SHOW DATABASES, SELECT FROM I_S.ROUTINES) in some cases.

SQLyog 11.31 (January 2014)

  • Features

    -- Restoring connections is now faster with multiple connections. Each connection is restored in a separate thread.
    -- Added support (in syntax highlighting and autocomplete) for a number of keywords added in recent MySQL versions.

  • Bug Fixes

-- ESC key did not work in confirmation dialog in editor after reaching end of the document.
-- The keyboard shortcut Ctrl+R now sets focus on the active tab In Result Pane.
-- Copy database/table will now use the CHUNK setting in preferences. Before only 'backup as SQL dump' did and 'copy ..' used a fixed CHUNK size of 1000 rows in the LIMIT clause. We had reports that 1000 rows could sometimes be too much for the HTTP buffer to handle with HTTP tunnel on some webserver environments.
-- With HTTP-tunnel a malformed XML data stream could in rare cases crash SQLyog.
-- When a SSH connection had applied a database filter, using that connection either as source or as the target for ‘copy database to other host’ the copy operation would fail with an invalid database name. 

Still need help? Contact Us Contact Us