What's new in SQLyog Community Edition 13.1.7

Oct 13, 2020
  • Bug Fixes:
  • SQLyog was unable to connect to a MySQL server using SSL when the client did not provide a CA Certificate file.
  • Editing a user password was not working for MariaDB server version prior to 10.4.
  • Calculating Optimal Datatypes in the Info table, returned syntax error for MySQL version 8 and above.
  • Copy Database was not working properly when the chunk size was set to 0 or less.
  • SQLyog returned random errors when importing a SQL dump using HTTP tunnel.
  • In some places, the connections and databases names longer than 44 characters were truncated on the right-side in the drop-down list of connections/database names.
  • Miscellaneous:
  • The MariaDB C Connector is upgraded to version 3.1.8.

New in SQLyog Community Edition 13.1.3 (Jun 25, 2019)

  • Features:
  • With new connections saved by this release all passwords etc. saved in files (sqlyog.ini, XML-jobfiles, session restore database etc.) are now encrypted and not only “obfuscated” as before. Old saved connection details with obfuscated passwords will be re-encoded using encryption first time the respective connection is opened (however old SJA "jobfiles" will need to be recreated if encryption shall be used in the jobfile. A jobfile with an "oldstyle" obfuscated password will still work with this new program version). Please observe that, as a consequence of using true encryption, it is now technically impossible to “reverse engineer” a saved password to clear-text (what we sometimes have done for users earlier).
  • The “caching_sha2_password” authentication plugin (default in recent MySQL 8 servers) is now supported. This has been achieved by upgrading the MariaDB Connector/C from 2.3x to 3.0x. The same connector upgrade also solves a few rare issues with SSL and other rare connectivity issues.
  • We updated the ‘keywords.db’ file (used for autocomplete and syntax highlighting) with new keywords and functions added in recent MySQL and MariaDB servers.
  • Bug Fixes:
  • “Duplicate Current Row” was unintentionally disabled (or “greyed out”) in SQLyog Community edition.
  • With MySQL 8.0.12+ Schema Sync displayed an extra ‘DEFAULT’ keyword for a table having a TIMESTAMP column with a default value. Older MySQL versions and MariaDB were not affected.
  • Schema Sync displayed the CREATE VIEW query twice for Views on comparison. This is a regression bug introduced in SQLyog v13.1.2.
  • SQLyog closed abruptly when executing a CREATE/ALTER TABLE statement using the GUI interface. This happened with MySQL v5.0.x and v5.1.x server versions only and is also a regression bug.

New in SQLyog Community Edition 13.1.1 (Oct 24, 2018)

  • This release fixes a rare crash as well as a regression bug introduced in 13.1.0.
  • Bug Fixes:
  • Fixed a regression bug introduced in 13.1.0, an error was returned on adding or editing the data in the 'Result' tab. The same steps also caused SQLyog to crash sometimes. This is fixed now.

New in SQLyog Community Edition 13.0.1 (May 2, 2018)

  • Features:
  • It is now optional if Schema Sync should synchronize the InnoDB Row Format -setting for tables or not.
  • Bug Fixes:
  • The setting in Query Profiler ‘preferences’ to include EXPLAIN EXTENDED is now ignored, if server does not support this (what is the case with MySQL from 5.7.4 – but not any MariaDB version).
  • Miscellaneous:
  • The “keywords.db” file (used by syntax highlighting, autocomplete and automatic lettercase handling for functions and keywords) was updated with new keywords and functions related to JSON, Roles, Common Table Expressions and Window Functions as of both MySQL 8.0 and MariaDB 10.3.

New in SQLyog Community Edition 12.5.0 (Nov 15, 2017)

  • Features:
  • Added command-line syntax for applying registration details when doing a ‘silent install’. You may refer this FAQ for details. Note that this option is only available for Ultimate edition.
  • A notification is now displayed when a large operation has finished (program icon in taskbar will 'blink').
  • Bug Fixes:
  • Fixed a bug in JSON export where reserved characters for JSON were not escaped properly.
  • Miscellaneous:
  • SJA for Linux now requires Linux kernel version 2.6.32 or higher.
  • Now Date along with Time is also displayed in History tab.

New in SQLyog Community Edition 12.4.3 (Jun 14, 2017)

  • Miscellaneous:
  • This maintenance release upgrades the MariaDB Connector/C to version 2.3.3 (current). Versions before this could time out incorrectly on some environments (and for unclear reasons). Affected in particular was Windows 8, but also all Windows versions running in a virtualized environment could be.

New in SQLyog Community Edition 12.4.2 (May 18, 2017)

  • Important notice:
  • The tunneler file for HTTP-tunnel has been updated with this release and must be replaced on the server.  Earlier HTTP-tunnel required PCRE-support in the server-side PHP-environment. Now it does not.
  • Features:
  • Search function in Object Browser now supports regular expressions.
  • Bug Fixes:
  • Fixed a rare connection failure using SSH-tunnel to specific BSD systems.
  • Removed unnecessary virtual column check for older servers with no support for this.
  • Fixed a crash when a menu-item, that is disabled in read-only mode, was clicked with no active connection tab.
  • Miscellaneous:
  • In Scheduled Backup wizard renamed the ’Flush Master Logs’ -option to ‘Purge Binary Logs’. This is in order to comply with ‘mysldump’. Further removed ‘Flush Slave Log’ -option, as using it on a replication environment could break replication.

New in SQLyog Community Edition 12.4.1 (May 18, 2017)

  • 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 re-drawn 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 irrespective of ‘Local’ being checked or not.
  • Changed the row count in Data Synchronisation Wizard to use a 64-bit integer. Before this the rowcount displayed would stop incrementing at a 10-digit number.
  • Import from Excel did not handle cells with multiline text properly. A linebreak became a SPACE.
  • For a non read-only connection, on right-clicking on a table, the Import External Data option was greyed out even though it could be accessed from the Powertools and shortcut key.
  • The ‘date picker’ did not handle dates with a ZERO-day/month/year (as allowed in specific sql_modes). In such cases current date would be selected and inadvertedly clicking “OK” in the dialog would overwrite. Now nothing is selected and the OK button is ‘greyed out’ in such cases.
  • Fixed a rare crash occurring when editing the password for a connection.
  • Regression fix: In SQL backups an extra r was added for every rn in stored routines.
  • Schema Sync sometimes failed to sync indentations to target exactly like on source.

New in SQLyog Community Edition 12.4.0 (May 18, 2017)

  • 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 for this plugin is not available with SJA for Linux with this release.
  • Bug Fixes:
  • In User Manager, if a MySQL username contained certain special characters (including  “@”),  it was not possible to GRANT privileges TO or  DROP the user due to misplaced quotes in the generated SQL.
  • Adding a new user in the ‘User Manager’ wasn’t populating the the newly added user_name in the ‘User’ field.
  • On localized keyboards with an ALTGR key, this key unintentionally behaved like CTRL with autocomplete popups. With some such keyboards using a non-QWERTY layout, this could prevent typing of specific characters.
  • A note about ‘read-only’ connections:
  • With the read-only flag checked in the settings for a connection, ‘read-only’ is enforced client-side from the SQLyog GUI and the editor no matter if user’s server-side privileges allows for writes. In ‘read-only mode’ you will be able to retrieve data from the server, use user variables, define SESSION-scope of server variables and everything else you need to work with data as long as you don’t need to write to the server.
  • In the GUI, controls that trigger statements that write to the database are ‘greyed out’ and do nothing. In the editor the same statements will be caught and not sent. This is accomplished by filtering against a ‘positive list’ of statements that are allowed. They are SHOW, SELECT, DO, DESCRIBE, EXPLAIN, USE, SET (except for SET GLOBAL|SET @@GLOBAL..), HELP, HANDLER, CHECK, ANALYZE, OPTIMIZE as well all transactional statements.
  • Further we also allow for CALL and please observe that ‘read-only mode’ is not enforced when executing a Stored Procedure or Function. It is also not enforced in the SJA – no matter whether launching an SJA-job from the GUI or from command-line. The SJA simply does not read this flag.
  • For the reasons above – and also because any user can easily turn the ‘read-only’ flag OFF – you should not consider this feature a ‘security feature’ (not a bullet-proof one, at least), but rather a ‘convenience feature’: With this flag ON, you will not accidentially (due to distraction, accidentially clicking with the mouse the wrong place or whatever) execute a statement that writes to the database. You are maybe not ‘fully secure’, but you are ‘safe’.
  • The ‘read-only’ feature is available in Professional, Enterprise and Ultimate editions of SQLyog.

New in SQLyog Community Edition 11.5.1 (Jun 13, 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.
  • ‘sesson 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 ‘sesson 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).

New in SQLyog Community Edition 11.5.0 (May 20, 2014)

  • Includes all the changes featured in the previous Beta versions

New in SQLyog Community Edition 11.5.0 Beta 1 (May 8, 2014)

  • Features:
  • 'session restore' now saves and restores content of open Query tabs.
  • 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 an individual 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.

New in SQLyog Community Edition 11.4.2 (Apr 17, 2014)

  • 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.

New in SQLyog Community Edition 11.4.1 (Apr 12, 2014)

  • Upgraded libraries that theoretically could be vulnerable to the ‘Heartbleed’ OpenSSL bug. All users are urged to upgrade as soon as possible.

New in SQLyog Community Edition 11.4.0 (Mar 26, 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.

New in SQLyog Community Edition 11.31 Beta 1 (Jan 6, 2014)

  • Features:
  • Restoring connections is now faster with multiple connections. Each connection is restored in a separate thread.
  • 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.

New in SQLyog Community Edition 11.3 (Jan 6, 2014)

  • Features:
  • The Query Profiler results can now be exported as HTML.
  • Bug Fixes:
  • Multiple 'reorder columns' operations in same instance of the dialog for this operation could have unexpected ordering results.
  • Strings containing a double-quote character are now escaped by doubling the double-quote character when also double-quote is selected for 'enclosed by'. This is a special rule for the double-quote character (other characters are escaped - if needed - with the backslash character) added for compliance with Excel and CSV-standards (at least Microsoft's interpretation of same) and -practices.
  • If databases named identically except for lettercase were available in a connection, Stored procedures, Stored Functions and Events could display in Object Browser where they should not.
  • When typing an object name (database or table) followed by a dot, the Autocomplete list of sub-objects could fail to popup. This was introduced in 11.28. Affected users may need to 'rebuild tags' after installing this build.

New in SQLyog Community Edition 11.28 (Nov 15, 2013)

  • Bug fixes:
  • Schema Sync requires SELECT privilege to the `mysql` database for syncing non-table objects. If user did not have this privilege, SQLyog would display a generic message that the sync failed, but with no further information. We now ask user to check for privileges.
  • A slugginess could occur in the editor when typing a function name followed by a bracket. It could happen for instance if specific versions of the Notepad++ text editor was installed on the system before SQLyog was installed.
  • Miscellaneous:
  • The color used to indicate the selected row in DATA and RESULT grids is now clearer/brighter than before and thus more easily distinguishable from the darker rows of the grid.

New in SQLyog Community Edition 11.27 (Oct 24, 2013)

  • Bug Fixes:
  • 11.25 introduced a dependency on the VC++ redistributable for some Windows platform(s). If the redistributable was not installed SQLyog would not start. Affected was Windows 2008 Server r2 (at least).
  • Another dependency was introduced in 11.26 affecting Wine. Also here SQLyog could fail to start.
  • Fixed a rare case where connection to a SSH daemon failed while copying a database.
  • Fixed a crash in SJA when "To email" recipient was not specified in the job file.
  • With SSL connection the 'helper connection' opened in order to stop a running query would not use SSL. As a consequence the server could refuse this 'helper connection'.
  • When SQLyog was closed immediately after a 'copy database' operation and reopened by 'connections restore' only the database copied in previous session would display in Object Browser for the connection. Only SSH-connections were affected.
  • Miscellaneous:
  • SQLyog now uses "ALTER VIEW" statement instead of DROP and CREATE VIEW statements for ALTER VIEW operation.

New in SQLyog Community Edition 11.26 (Oct 24, 2013)

  • Bug Fixes:
  • Fixed a random crash in Schema sync.
  • Messages were not displaying in MESSAGES tab after creating/altering Views, Triggers, Stored Procedures etc.
  • Horizontal scrollbar was not handled properly in Blob Viewer.
  • Pressing ESC key to cancel the DROP TABLE operation was dropping the table on Wine.
  • Comments inside a 'quoted string' were not escaped properly in query when executing in Query tab.
  • On Windows Server 2008 r2 SQLyog could close down unexpectedly immediately after it was started.

New in SQLyog Community Edition 11.25 (Oct 24, 2013)

  • Bug Fixes:
  • When executing queries in more connections at the same time all connection tabs would only display the results when all query instances had returned.
  • If focus was on the table in Object browser selecting "copy table to" -option was not setting the focus to the selected table in the dialog.
  • Menu option 'Paste SQL Statement' will now format the query as per the SQL Formatter Preferences settings.
  • Sometimes SQLyog failed to connect to MySQL server via SSL. This was introduced in 11.2.
  • While copying a table/database, pressing SPACE would abort the copying process. Now it will not (but ENTER key will still abort the process).
  • On Wine expanding triggers- and stored procedures -folders in copy database dialog could crash SQLyog.
  • FIND option in Blob viewer could crash SQLyog with specific sequences of user operations.
  • Miscellaneous:
  • Preference dialog will now display the the last closed tab.

New in SQLyog Community Edition 11.24 (Oct 24, 2013)

  • Bug Fixes:
  • Fixed a memory corruption when accessing specific tables. In rare cases this could crash SQLyog. Only the 32 bit version was affected and only when using 'compressed protocol' for the connection.
  • LOAD DATA LOCAL could fail to import data from a data file using 'Windows line breaks' (\r\n). This bug was introduced in 11.23 with the fix for non-ASCII characters in the file name.

New in SQLyog Community Edition 11.23 (Oct 24, 2013)

  • Bug Fixes:
  • Fixed a rare crash which could occur while stopping query execution.
  • Fixed a crash while expanding tables in Scheduled backup with no connection open.
  • Import External Data truncated DOUBLE and FLOAT values to 6 digits after decimal point.
  • Paste did not work in a column where a 'Foreign Key Lookup' icon displays (FK 'children' columns).
  • When opening a SJA wizard multiple times and selecting an existing jobfile, the jobfile details were not displayed 2nd and higher times. Instead details from first time a job file was opened during the session were displayed.
  • Exporting to a SQL-dump failed to escape properly, if a view contained columns with backtick(s) in the column identifier.
  • Specifying a filename with non-ASCII characters in LOAD DATA LOCAL raised the error 'file not found' even if file existed and was valid.

New in SQLyog Community Edition 11.22 (Oct 24, 2013)

  • Bug Fixes:
  • Fixed stability issues when running SQLyog with a non-English language interface on a system running a non-western locale. 'Hangs' and random crashes could occur. This bug was introduced in 11.2.
  • With specific settings for the formatter the formatting preview in 'preferences' would not always show exactly how formatting would actually be done.
  • After closing a maximized SQLyog program window with no connection window inside, SQLyog would open in non-maximized mode when started next time.

New in SQLyog Community Edition 11.21 (Oct 24, 2013)

  • Features:
  • The interface for restoring connections from previous session has been changed due to user requests. There is now no popup dialog at startup, but instead a setting in Tools-> Preferences-> Others tab.
  • Bug Fixes:
  • Fixed a rare crash in HTTP-tunnel typically happening when copying huge databases or tables. Exact details of this crash would depend on the environment.
  • LOAD DATA LOCAL would hang indefinitely if a non-existing file was specified as argument. This bug was introduced in version 11.2.
  • In Schema Sync a comma could be missing before a COLLATE clause thus resulting in an invalid SQL statement.
  • A very large .zip archive generated by Scheduled Backup could fail to open due to a checksum error.
  • Miscellaneous:
  • MySQL 3.23 and 4.0 servers are no longer supported and a connection attempt to such will be denied.

New in SQLyog Community Edition 11.2 (Oct 24, 2013)

  • Features:
  • When opening SQLyog it is now posibble to have the same connections tab opened as when the program was closed last time. The feature is optional and individual connections can be selected.
  • Bug Fixes:
  • If memory was exhausted SQLyog could crash. We will now exit gracefully.
  • Miscellaneous:
  • Support for the clear-text plugin has been removed.

New in SQLyog Community Edition 11.13 (Oct 24, 2013)

  • Bug Fixes:
  • The fix for incorrect escaping in DSN-authentication in 11.12 introduced a new problem with some ODBC-drivers - most important drivers for Oracle. Actually we belive that the code in 11.12 is correct according to ODBC standards and Windows API requirements. But affected drivers do not follow standards as regards to escaping of authentication details. We will now try to authenticate 'the old way' if authentication 'the new way' fails.

New in SQLyog Community Edition 11.12 (Oct 24, 2013)

  • Bug Fixes:
  • Fixed a case where support for the 'cleart text plugin' did not work as expected and authentication failed.
  • Import External Data could fail to authenticate to the ODBC-source if dsn-password contained a semicolon.
  • Autocomplete would sometimes hang or crash while editing stored procedures. This bug was introduced in v11.0.
  • Export table data as SQL generated an incorrect create table in the 64 bit version. Also this was introduced in v11.0
  • For DATETIME fields in MySQL 5.6+, if CURRENT_TIMESTAMP was given as default, the default would be incorrectly quoted.

New in SQLyog Community Edition 11.11 (Oct 24, 2013)

  • Bug Fixes:
  • Enum field drop down was not available in table data or result tab when http connections were used - introduced in v10.0
  • Schema sync could generate an incorrect alter table statement for addition of foreign keys - introduced in v11.0.
  • SJA was not decoding the dsn password and the ssh passphrase/password after reading it from the xml file.
  • SQLyog 64 bit was extremely slow on some systems.

New in SQLyog Community Edition 11.1 (Oct 24, 2013)

  • Features:
  • Added an option in the Connection Manager to keep a connection alive by pinging the server (using mysql_ping() ) at a user-specified interval.
  • Encoding of all passwords in all job files in the same way that the passwords are encoded in the SQLyog.ini file. The job files created with version 11.1 will not work with previous versions of SQLyog/SJA. However, job files created with older versions of SQLyog will work with the new version.
  • A setting in the connection manager for enabling the MySQL Cleartext Authentication Plugin. This sends the password in clear text and is to be used only if the user has a secure connection and a specific need for this. For example, if the server has PAM authentication enabled, then the password needs to be sent in clear text.
  • Bug Fixes:
  • Incorrect mapping of the double data type when importing from access in import external data.
  • Fixed a crash which would occur while dropping an index when table data was in focus - introduced in v10.
  • In Visual Data Compare, an incorrect query could be generated if the primary key column was not the first column in the table - introduced in v10.5.
  • COLLATE clause not handled properly in Schema Sync.
  • If the difference between the structure of 2 tables was only the character set, then Schema Sync could incorrectly generate a comma in the alter table statement.
  • Session timeout value was not stored in the job files.
  • DataSync in SJA for linux 64 bit would fail in some cases due to incorrect typecasting.
  • Miscellaneous:
  • Changes in the order of execution of statements when opening a new connection. Now the user specified init-command(s) will be executed after SQLyog's init-command(s).

New in SQLyog Community Edition 11.01 (Oct 24, 2013)

  • Bug Fixes:
  • Fixed 2 issues introduced in 'Import External Data' when rewriting program code for 64-bit compilation as of version 11.0: 1) A job file with a (NDB-cluster) TABLESPACE specification and a WHERE clause failed to load in the wizard 2) non-ASCII defaults defined on non-unicode/ANSI string columns on source would be mapped against a UTF8 byte pattern and would garble for same reason.
  • Fixed a rare crash occurring when dropping indexes from the Object Browser repeatedly.

New in SQLyog Community Edition 11.0 (Oct 24, 2013)

  • Features:
  • Now SQLyog (including SJA for both Windows and Linux) is available as both 32 and 64 bit binaries. Obviously the 64 bit version will require a 64 bit Windows. 32 bit version will install to 'Program Files (x86)' and 64 bit to 'Program Files' on 64 bit systems.
  • Autocomplete is now context-aware. The keyword before any type of autocomplete popup/dialog will be used for filtering and displaying only object types relevant in the context.
  • Bug Fixes:
  • Copy to clipboard from GRID could in rare cases truncate the last row away. This bug was introduced in version 9.51.
  • Fixed a bug in import external data where clicking on "select all" would select tables even when no data was returned from the source. This could cause a crash while executing the job. This was introduced in 10.1.
  • If there was no default database selected in the main dialog of SQLyog, changing the database from the dropdown in 'backup as SQL dump' dialog would cause SQLyog to hang. Introduced in version 10.5.
  • When using drag and drop to create a Foreign Key constraint in Schema Designer, the ALTER TABLE pop-up dialog would have the view scrolled to the right, resulting in the leftmost two columns being hidden. This issue was introduced in 9.6.
  • The position from where the 'Themes' folder was read did not honor a specified -dir startup switch. It will now read from a 'Themes' subfolder to the folder specified with -dir if exists.
  • Schema Sync could attempt to DROP and CREATE a Foreign Key in one ALTER TABLE statement in cases where a Foreign Key existed on both source and target specified on same columns but details for ON UPDATE and/or ON DELETE were different. This will not work and now two statements are generated.
  • Miscellaneous:
  • Explain Extended (executed by Query Profiler) now pops up an error dialog instead of logging to MESSAGES tab if an error occurs with the statement.

New in SQLyog Community Edition 10.51 (Oct 24, 2013)

  • Bug Fixes:
  • Executing a SQL-statement with a comment inside could cause the Query Profiler to send an incorrect EXPLAIN statement - thus raising a syntax error. This bug was introduced in 10.5
  • Accessing Visual Data Compare could raise the error 'Could not connect to SJA' on systems/user accounts with limited access to write to installation folder. The reason is that Visual Data Compare attempted to create temporary files in installation folder. They are now created in user's 'User Profile'
  • If the 'Custom Filter' or 'Foreign Key Lookup' dialog was open SQLyog did not appear in the list displayed by Windows ALT+TAB dialog
  • With (only) a view/procedure/function/trigger selected in Object Browser the 'Backup database as SQL dump' dialog did not open. This bug has existed since version 6.5
  • Fixed an issue in SJA mails with HTML-encoding of "" -characters where they were not used for specifying HTML tags
  • Specific operations by user in the GUI could cause 'Export As SQL Dump' to show database objects of another database than expected

New in SQLyog Community Edition 10.5 (Oct 24, 2013)

  • Features:
  • New major feature: "Visual Data Compare" (in short 'VDC'). It is a third option for Data Sync in addition to the two already existing ('one-way synchronization' and 'two-way synchronization'). A VDC-job is started from a modified version of the Data Sync wizard (from the 'powertools' menu). With VDC you will be able to compare differences visually and specify tables and rows that shall be sync'ed as well as to decide in what direction to sync. A SQL preview is available. VDC is an ULTIMATE feature.
  • Explain and Explain Extended for queries can now be executed from Query Editor context menu. Also this is an ULTIMATE feature.
  • Query Profiler now supports Explain for Insert, Update and Delete statements if server supports. MySQL servers from 5.6.3 servers do.
  • Copy DB and Backup as SQL Dump will now respect the defined Object Browser filter if any.
  • Bug Fixes:
  • A style issue caused e-mails sent by SJA not to display properly in some clients. A tag was placed in header section which is generally truncated/omitted by most mail clients. HTML styles are now embedded internally in the body of the mail.
  • It was possible to rename a table by clicking it twice in the Object Browser. This functionality has been removed as it too easily could cause a table to be renamed by mistake. Tables can still be renamed from menu/context menu and corresponding keyboard shortcut (F2).
  • Fixed an issue where autocomplete failed to handle identifiers with an underscore character properly.
  • The selection in object browser was reset to the 'container node' of current object when a filter was defined or cleared. This will only happen now when a filter is applied and the currently selected object becomes hidden due to the filter setting.
  • Fixed a painting issue in the Schema Sync dialog.
  • Fixed an issue where autocomplete would display the same option twice. It happened in some cases if the same identifier was in use on different levels of the schema (such as if a table had a column named identically to the table itself).
  • In Table Diagnostics, table list was not getting updated after selection was cancelled from database combo box.
  • Miscellaneous:
  • Removed comments from query when it is shown in History Tab, Messages Tab and Query Profiler.

New in SQLyog Community Edition 10.42 (Oct 24, 2013)

  • Bug Fixes:
  • Inserting a string literal identical to a supported 'smart keyword' from GRID/FORM view by enclosing it in backquotes (like `NULL`) did not remove the backquotes before insertion. This bug was introduced in 10.0 and the fix is backported from the current 10.5 development tree.
  • When updating or deleting from the RESULT tab and if the tab displayed a JOIN of columns from multiple tables and if all columns of a composite Primary Key of one or more tables were not displayed a wrong DELETE or UPDATE query could be generated. Also this bug was introduced in 10.0.

New in SQLyog Community Edition 10.41 (Oct 24, 2013)

  • Bug Fixes:
  • SQL-exports did not 'quote' TIMESTAMP values. For that reason a dump with such data did not restore. This bug was introduced in 10.4.

New in SQLyog Community Edition 10.4 (Oct 24, 2013)

  • Features:
  • Added a filter in the Object Browser for hiding display of database objects here. More precisely: database objects, where the typed filter string is not a substring of the object identifier, will be hidden. When focus in on the connection node, the filter will act as a database filter. If focus is on a database, a table, a table folder or any sub-table object, it will be a table filter on current database. If the focus is on a stored program or stored program folder of any kind it will be a filter on that type of stored program in current database. The filter is specific for each database object (connection, tables of a database, or a type of stored programs of a database) and is persistent within a SQLyog session (but not persistent across sessions).
  • NULL-values are now displayed with italics like (NULL). This eliminates any confusion with a literal value.
  • Added ALT+F5 as a keyboard shortcut for refreshing a DATA tab.
  • SQLyog will now "USE `mysql`;" when User Management is opened and reset the default database again when it is closed. Before using User Management on a replication master could break replication with specific binlogging settings. This is a workaround for what we consider a bug in MySQL.
  • When 'rebuilding tags' in auto-complete we are now committing small transactions to SQLite. Before it was one big transaction. This ensures normal operations for indexed data while 'rebuilding tags'.
  • Drastically improved auto-complete performance. This is actually the third time we do so, but recent additions to SQLite makes this possible again (technically autocomplete now uses SQLite 'WAL mode').
  • Added support for the 'Windows authentication plugin' (available from MySQL 5.5.16).
  • Bug Fixes:
  • Fixed a 'commands out of sync' error when executing a stored procedure multiple times.
  • Fixed a bug where the foreground/background color applied for Messages tab failed to paint properly.
  • The 'SQL Scheduler and Reporting Tool' could fail to deliver server messages in mails sent.
  • Creating views/sp's/function/triggers/events added statements twice to messages tab.
  • The 'total time' displayed for a query would not always correctly calculate the sum of 'execution time' and 'transfer time'. This bug was introduced in 9.2.
  • Improved Schema Sync performance if Foreign Keys were involved. We now execute fewer statements in such cases.
  • A database name would not be completed by autocomplete if the database was listed in connection manager.
  • Fixed some cases where autocomplete CTRL+Space/Enter incorrectly did not return a table/alias.
  • Fixed some issues where autocomplete did not immediately return objects created - most important objects added by 'Import External Data' tool and 'Copy Database/Table to Other ..' would not display immediately. It was necessary to 'rebuild tag'. It is not now.
  • Loading a Unicode file with BOMs (Byte Order Marks) into the editor could strip characters (3 characters with UTF8 - 2 characters with UCS2/UTF16) from the pasted content. A buffer length allocated did not consider BOMs properly.
  • MESSAGES tab could display conflicting messages about warnings. This bug was introduced in 10.3.
  • When copying from MESSAGES tab and pasting into SQLyog editor - or any editor or program - the pasted content could add garbage characters.
  • Silent uninstall' was not working as expected.
  • UPDATE statement generated by Data Sync did not use 'fully qualified table names' where as INSERT and DELETE statement did.

New in SQLyog Community Edition 10.3 (Oct 24, 2013)

  • Features:
  • The list of connections in Connection Manager can now be managed by typing directly in the 'dropdown'. What is typed acts as a 'prefix search' and first connection name starting with the prefix will be selected. This applies to both the Connection Manager of the main program as well as SJA wizards.
  • Filter is implemented in the Schema Synchronization dialog for filtering tables and other objects. This is a 'exact match filter'. However SQL-wildcards ("_" and "%") may be used.
  • Added a filter option to MESSAGES tab. You may show only queries returning a result set, queries not returning a result set, queries returning errors or queries returning warnings only as well as queries returning either warnings or errors. Also MESSAGES tab will now display the (first 128 characters of the) query.
  • Bug Fixes:
  • F6 shortcut did not open ALTER TABLE/DATABASE when the focus was outside the Object Browser.
  • Adding '%' to the filter string in 'custom filter' was not handled properly and could result in wrong results. This was introduced in version 10.0.
  • Updating an image stored in a BLOB field using the Blob Viewer could fail. Also this was introduced in 10.0.
  • Miscellaneous:
  • It is now default for new connections to use the GLOBAL sql_mode for the connection. But user may still specify whatever sql_mode he wants.

New in SQLyog Community Edition 10.2 (Oct 24, 2013)

  • Features:
  • Saved connections can now be exported and imported. The option is available in the 'tools' menu.
  • Added an option to open exported CSV and Excel XML files directly with the program associated with the file extension on the system.
  • Bug Fixes:
  • Exporting Schema Designer canvas as image on Wine generated empty boxes for tables with no information about columns. It is actually a bug in Wine (incomplete Windows API implementation for drawing routines).
  • The height of GRID-cells will now adjust to fit font setting for the GRID.

New in SQLyog Community Edition 10.12 (Oct 24, 2013)

  • Bug Fixes:
  • With specific settings for GUI appearance (DATA tab in lower pane, ‘autorefresh DATA tab on focus’ enabled) switching from one connection to another and back would reset filter in the first connection. This was introduced in 10.11.
  • Editing data from GRID and pressing arrow-up/down key could scroll the view a full page. Also this was introduced in 10.11.
  • Export table as .. SQL’ from RESULT tab generated invalid SQL if the tab was in ‘read-only’ state. This was introduced in 10.0. Also ‘Export table as .. SQL’ has now been disabled for multi-table result sets. This is an old issue, but exporting data from multiple tables to SQL never made sense.
  • SQL Formatter would add whitespace around non-ASCII characters in identifiers and aliases.
  • The rowcount displayed in status line is now a count of rows available in current DATA/RESULT tab. Before it was the number of rows fetched from MySQL with the last executed SELECT query for that tab and did not reflect INSERTS and DELETES executed later from GUI. Also when a filter is used, the display will show the rowcount after applying filter. It did not before in RESULT tab.
  • Small GUI fixes.

New in SQLyog Community Edition 10.11 (Oct 24, 2013)

  • Bug Fixes:
  • Pressing the ESC key while cursor was positioned in an empty row of the GRID could cause a crash. Introduced in 10.1
  • Hide optimal datatypes’ of a table in INFO tab/HTML view did nothing. Also this was introduced in 10.1

New in SQLyog Community Edition 10.1 (Oct 24, 2013)

  • Features:
  • It is now optional whether DATA, INFO and HISTORY tabs shall display in ‘upper pane’ (as in 10.0) or in ‘lower pane’ (as before 10.0). The setting is available in tools .. preferences .. general. Note that for DATA tab this applies to the ‘non-sticky’/non-persistent DATA tab. A ‘sticky’/persistent DATA tab will always display in ‘upper pane’.
  • DATA, INFO and HISTORY tabs appearance will now be persistent across sessions when configured to display in upper pane. If visible when program was closed they will open when program starts next time – if hidden when program was closed they will not. When configured to display in lower pane they will always be visible.
  • The checkbox to ‘select all’ as added in DATA and RESULT tab in 10.0 is now implemented all over the program, including SJA wizards.
  • The background color for the editor can now be defined by user. Same applies to Query Builder and Schema Designer canvas. Also settings for syntax highlighting in the editor can now be defined using a full color palette.
  • Multi-column sort in DATA tab now uses CTRL+CLICK modifier when clicking the column header. A simple CLICK (with no CTRL) will discard previous sort setting (if any) and do a single-column sort.
  • Added an option to copy selected text into clipboard with all whitespace (SPACE characters, TAB characters and linebreaks) replaced with a single SPACE character. The option is available from menu and the keyboard shortcut ALT+C .
  • Sorting (single-column) of results is now possible in Data Search tab.
  • Bug Fixes:
  • With Windows classic theme enabled, switching SQLyog’s theme could replace the ‘minimize’ button with garbage text.
  • Paste SQL statements’ could crash COMMUNITY. This bug was introduced in 10.0.
  • Persistence of display mode (GRID, FORM, TEXT) will now only have effect after the tab has loaded with data. If user interrupts loading of data the current mode will not change.
  • Since version 10.0 undefined data of an auto-increment column will display as “AUTO” and not “NULL”. But with specific table definitions “AUTO” could display for the wrong column.
  • Editing second and higher table from a multi-table result set could fail due to incorrect SQL generated. Introduced in 10.0.
  • In the Import External Data mapping columns dialog, using “Edit SQL” to view/edit the query could generate a query with an incorrect encoding of the statement. As a consequense the statement failed.
  • If an existing connection (in connection manager) with unsaved changes is open “New Connection using Current Settings” would not take the current settings, but the settings saved for the connection instead.
  • The query generated for INSERT from table data/result tab now include only values entered by the user. Columns that were not specified by user are not listed in the statement. UPDATE bahaved like this for a long time, but INSERT did not. This could result in an error when inserting to a table with NOT NULL column(s) with no DEFAULT defined.
  • When SELECT was executed, Auto-paging in Result tab was always enabled even if the option “Enable Autopaging in Data/Result tab” was unchecked. This bug was introduced in 10.0 with the common LIMIT setting for DATA and RESULT tab.
  • Updating and deleting from RESULT tab could fail if PK-column(s) were not included in result set. This bug was introduced in 10.0.
  • In a 'fully qualified' object name (`database`.`table` etc.) there may be SPACE characters on both sides of the ".". SQLyog did not handle this and with autocomplete enabled a crash could occur as autocomplete was not able to identify object name(s) correctly.
  • Export as Excel XML' could generate an empty file with no data. This bug was introduced in version 10.0.
  • When inserting/updating the last column in a row in Data/Result tab, pressing tab from keyboard would point to the first coulmn of the next row but the scroll bar failed to bring the selected column into display. This bug was introduced in 10.0.

New in SQLyog Community Edition 10.00 (Oct 24, 2013)

  • Features:
  • The DATA tab is now moved to the upper pane. This completes the GUI redesign we started with version 9.5 (but we will continue after 10.0 release to provide optionality for this). A DATA tab will now open from table menu/context menu, keyboard shortcut F11 or from the “+” icon to the right of open query etc. tabs. Also if not the option to ‘paste object name to editor on double-click ‘ is selected in ‘preferences’ it will open on double-click on the table in Object Browser.
  • Added an option to open a DATA tab in ‘sticky’/persistent mode. A DATA tab opened like this will remain open until closed manually by user. If a DATA tab is opened in ‘non-sticky’/non-persistent mode it will be replaced when opening another table in ‘non-sticky’/non-persistent mode.
  • Redesigned the tool bar in DATA and RESULT tab including new icons.
  • SQLyog now opens as default with a blue-colored interface. The old non-colored interface can be selected from preferences .. ‘others’ tab .. ‘theme’ (the 10.0 blue default theme is named ‘twilight’). Currently ‘themes’ to the main program dialog only and not popup dialogs. It is actually possible for user to modify a ‘theme’ or to create his own ‘theme’. Information about this will appear after GA release.
  • Several improvements to Schema Sync performance: 1) Before an ALTER TABLE statement would be generated for every schema change. Now in most cases they are aggregated to a single ALTER TABLE statement. 2) Optimized queries and internal processing.
  • The current row in DATA and RESULT grid can now be selected using Ctrl+SPACE.
  • Added multi-column filter and sort option in Table data tab.
  • Added a control for select all/deselect all rows in DATA and RESULT grid.
  • Keyboard shortcuts added: 1) Ctrl+Alt+V will now rotate between GRID, TEXT and FORM display modes for DATA and RESULT tab. 2) ALT+Ins and ALT+Del shortcuts added in Table data/Result tab/Data search for Insert and Delete like already available in CREATE/ALTER TABLE.
  • Selection of any display mode (GRID, FORM, TEXT) is now persistent in RESULT tab. The currently active mode will have effect when executing a new query.
  • SQLyog installers are now digitally signed. When downloading with IE9 a false warning appeared due to lack of certificate and also UAC ('User Account Control' of Vista+ Windows) would warn that the program was from an 'unknown publisher'.
  • When upgrading, the installer will now remember what shortcuts were created previously'.
  • Table data will now read default limit values from preferences. Same default setting now applies to both DATA and RESULT tabs.
  • Bug Fixes:
  • Using a WHERE clause in data sync could cause the wizard to terminate prematurely. This bug was introduced in 8.6x.
  • Import external data could generate incorrect SQL when a Primary Key was present in source and PK-column(s) were not selected for import.
  • Fixed a crash occuring when opening a file that was not a valid jobfile from a SJA wizard.
  • SQLyog could crash when connected with HTTP tunnel and exporting to a fixed-length CSV-file.
  • Quite a lot of GUI fixes.
  • Miscellaneous:
  • The shortcut to 'execute all queries' has been changed from SHIFT+F9 to CTRL+F9 . This is changed because SHIFT+F9 on some keyboards (including most English keyboards) could easily be mistyped if user wanted to type a bracket ( "(" or ")" ).

New in SQLyog Community Edition 9.63 (Mar 22, 2012)

  • Features:
  • Added an option to specify the font used in the Object Browser
  • Schema Sync now has an option to add SET FOREIGN_KEY_CHECKS = 0 to the script generated
  • Added an option to specify INIT_COMMAND(s) for a connection. INIT_COMMAND(s) are executed when SQLyog connects and reconnects. The primary purpose is to override settings specified with ‘init_connect’ setting in server configuration for the SQLyog session. For instance if ‘init_connect’ server setting specifies “SET AUTOCOMMIT = 0" you may enter “SET AUTOCOMMIT = 1" in the SQLyog connection manager if you want a non-transactional behavior for the SQLyog session
  • Bug Fixes:
  • If both a column default and a column comment was specified in CREATE/ALTER TABLE a SPACE-character was missing in the generated statement causing invalid syntax error. This bug was introduced in 9.5
  • Fixed a crash (reported internally) in the ‘Indexes’ tab of the CREATE/ALTER TABLE interface
  • Schema Sync did not handle BIT-column defaults properly. A redundant apostrophe caused the statement generated to be invalid
  • Also if Schema Sync operated on a table where only column-level comments differed on source and target an invalid statement would be generated

New in SQLyog Community Edition 9.62 (Mar 5, 2012)

  • Features:
  • A Korean translation is now included.
  • Miscellaneous:
  • The localization tools have been updated. The compiler for building localizations is now up to 100 times faster than before. Also the XML has now been properly versioned.

New in SQLyog Community Edition 9.61 (Feb 25, 2012)

  • Features:
  • A Chinese (Simplified) translation is now included
  • Bug Fixes:
  • When there was an INFO tab open the server was unnessarily queried for the content of the INFO tab (based on Object Browser selection) when closing the program. This could cause a slow shutdown
  • Fixed a crash occurring when pressing the ESC key in the CREATE/ALTER tab/dialog. This bug was introduced in 9.6

New in SQLyog Community Edition 9.6.0 Beta 3 (Feb 16, 2012)

  • Features:
  • When performing CREATE/ALTER TABLE operation from inside the Schema Designer now a dialog with a tabbed interface similar to the CREATE/ALTER TABLE tab will open
  • It is now optional if Query Builder will create statements with ‘fully qualified tablenames’ or not
  • Bug Fixes:
  • In Data Sync a low setting of ’max_allowed_packet’ on source server could result in CONCAT_WS() used for checksums’ calculation returning NULL. We did not consider this and as a consequence rows could fail to sync without warning. We will now abort the job with an error message (if user has selected to ‘abort on error’) or print an error to the sja.log file and the console (if user has selected not to ‘abort on error’ ) informing that some rows may have been skippped in such cases
  • The fix for empty string defaults in 9.51 was not complete. It was (unlike 9.5) possible to create such default but it did not display as '' after creation in ALTER TABLE
  • If multiple databases with same name existed only differing in lettercase SQLyog would generate certain statements using the ‘mostly lowercased’ database name. This bug was introduced in 9.5
  • Autocomplete runs in a separate connection, but also when Autocompelte was disabled this connection was created for no reason
  • Small fixes - mostly GUI fixes to the new CREATE/ALTER TABLE interface

New in SQLyog Community Edition 9.51 (Feb 16, 2012)

  • Features:
  • The active database context is now highlighted in Object Browser using a bold font
  • Bug Fixes:
  • Drop-downs in the DATA and RESULT tab grid (used by SET and ENUM columns) could ‘drop down’ where they should ‘drop up’ instead
  • Specifying empty string defaults for strings columns was broken in 9.5
  • Fixed a rare crash caused by an undocumented behavior from the Windows API resulting in division by zero. Crash is now avoided by adding an additional condition check
  • Fixed a painting issue in the Foreign Key tab in the new (from 9.5) tabbed interface for CREATE/ALTER TABLE that could render the interface here unusable on some systems
  • Other minor fixes with CREATE/ALTER tabbed interface

New in SQLyog Community Edition 9.5 (Feb 16, 2012)

  • Features:
  • All CREATE TABLE and ALTER TABLE GUI functionalities will now open in a non-modal tabbed interface. The new tab appears in the SQL area (alongside Query tabs etc.)
  • HISTORY and INFO tabs will now also appear in the SQL Area. The rationale is that those are not related to a specific (set of) query(ies). We plan to move the DATA tab up there as well for same reason
  • When SQLyog opens, the SQL Area will now open the HISTORY tab, INFO tab, and a single QUERY tab. Other tabs belonging in this area can be opened on demand. HISTORY and INFO tab display are persisitent across session (ie. if one is closed when SQLyog closes down it will not diplay when SQLyog is opened next time – but may be opened by user, of course)
  • Search is now possible in INFO tab/text mode and in HISTORY tab. CTRL+F will open the 'Find' dialog
  • Foreign Key lookup now works across databases
  • Bug Fixes:
  • The BIT datataype was not supported properly in text-mode
  • On COMMUNITY if the SQL Area was increased to fill all vertical space, the divider could not be dragged back
  • In ‘Execute SQL-script’ it is now optional if the complete script should abort or not if an error was encountered. Before it always aborted. The fix does not apply to HTTP tunnel where we will still ‘abort on error’ always
  • Copying to clipboard could erroneously raise an ‘out of memory’ error. This was a miscalculation
  • Import External Data’ GUI now supports SHIFT+CLICK selection of objects
  • The connection manager GUI’s of the SJA wizards did not handle SSL certicates properly (the main program window did not suffer from this)
  • If an ENUM/SET column was returrned using an alias the drop-down combo in the RESULT GRID did not display
  • Underscores were not handled properly by Autocomplete
  • Syntax highlighting is now not used in INFO tab. It made sense for the CREATE statement only and was disturbing in other contexts
  • A default for a BIT datatype could not be specified properly. Now b'..' and x'..' notation may be used when specifying column defaults
  • Closing a query tab with multiple result sets could cause a memory peak and raise an out of memory error
  • When connected to pre-4.1 servers non-ASCII characters could garble
  • Duplicate table failed to copy spatial indexes

New in SQLyog Community Edition 9.33 (Nov 22, 2011)

  • Bug Fixes:
  • Fixed two regression bugs in Autocomplete introduced in 9.31:
  • A performance regression if the option to “Show suggestion as you type in SQL editor” was enabled.
  • Table alias support was broken.
  • The Autocomplete popup windows opened by Ctrl+Enter and Ctrl+Space could ‘pop down’ where it should ‘pop up’ resulting in the content being partly invisible. This bug was introduced in 9.31.

New in SQLyog Community Edition 9.32 (Nov 14, 2011)

  • Bug Fixes:
  • Typing using the numerical keypad typed nothing in the SQL editor. This bug was introduced in 9.31
  • With Japanese interface enabled some favorites items could fail to display

New in SQLyog Community Edition 9.31 (Nov 14, 2011)

  • Features:
  • Improved the handling of (built-in and stored) functions and stored procedures in Autocomplete. This involves 1) A stored program is now handled also if a ‘fully qualified routine name’ is not used. 2) Introduced a Ctrl+Shift+Space keyboard shortcut that will display the parameter-list of a routine when the cursor in positioned inside it. 3) While writing a routine call the parameter list will highlight the current parameter. Also note that we have also reversed the behavior of Ctrl+Space and Ctrl+Enter keyboard shortcuts for Autocomplete – this in order to comply with most IDE’s and advanced editors.
  • Bug Fixes:
  • Schema Sync could generate an incorrect ALTER TABLE statement with an A TIMESTAMP .. ON UPDATE CURRENT_TIMESTAMP column on source. This bug was introduced in 8.4.
  • On Wine the status line (at the button of the program window) did not display. This was introduced in 9.3.
  • The Keyboard CTRL+SPACE did nothing on Wine. Now CTRL+SPACE and CTRL+ENTER behave identically on Windows and Wine.
  • On Wine the autocomplete popup window painted with a frame hiding some details.
  • When Japanese language was selected for the program interface ‘Copy Database/table’ returned an error. Also this was introduced in 9.3.

New in SQLyog Community Edition 9.3 (Nov 14, 2011)

  • Features:
  • This release adds a Japanese translation of the User Interface.
  • Bug Fixes:
  • The data display area in Data Search tab did not handle text mode.
  • The Autocomplete popup windows did not allow 'rotation' from bottom to top (and vice versa) using arrow keys.
  • A user variable using a keyword after "@" (like "@SELECT") would be handled like a keyword by syntax highlighting. Now it is not.

New in SQLyog Community Edition 9.2 (Nov 14, 2011)

  • Features:
  • The ‘Foreign Key lookup’ introduced in 9.0 is now also available in RESULT tab. With HTTP-tunnel this is not possible however.
  • Added a calender control for managing DATE, DATETIME and TIMESTAMP columns.
  • Data Search enhancements: 1) Added an option to search on column level. 2) Added Google-style “+” and “-” operators meaning ‘exact match’ and ‘not matching’. ‘+’ and -’ may be combined with “double quotes” and the NULL keyword. 3) Added an option to use hexadecimal patterns for search using x’..’ notation (note that this feature requires MySQL 4.1 or higher). 4) Added a filtering option. You may select to search specific data types only and/or a subset of databases in a connection, a subset of tables in a database or a subset of columns in a table. 5) 'Data Searach' item was added to object (context) menus where it applies.
  • Added an option to clone a connection in the connection manager.
  • Bug Fixes:
  • After query execution from editor messages from one connection were always sent to the topmost connection window even though the active connection was not the topmost.
  • On Windows Vista and higher CSV-import of numerical data written in ‘scientific notation’ failed.
  • Fixed a crash with ‘stored programs’ if the ‘stored program’ definition was loaded from a file with a long name (too long to display fully in the tabbed interface). This bug was introduced in 9.1.
  • ALTER VIEW could fail to open the view definition in MySQL 5.1+ if an underlying table was ALTERed after creation. This is actually a server bug due to which SHOW CREATE TABLE failed. SQLyog now works around this bug by fetching the VIEW definition from information_schema if SHOW CREATE TABLE fails. One limitation of this is that the ALGORITHM clause will not necessarily be the exact one specified while creating the VIEW as Information_Schema has no record of the ALGORITHM clause.
  • Execute SQL Script will now show data transfered in percentage rather than the size. Once the execution/import is succesfull it will show the total size.
  • Removed extra whitespace in query when displayed in the message tab due to an error.
  • The execution time displayed for a query is now formatted for better readability. Note that English decimal notation (".") is always used.
  • Fixed a segmentation fault (crash) in the 'SQL Scheduler and reporting tool' of SJA for Linux.
  • Form View discarded the column alias while displaying the result.
  • Added *.ppk filter in SSH private key file open dialog.
  • F1 opened wrong help page when pressed from Table Data/Result Tab.
  • Fixed an issue were selecting the auto_increment option in 'Import External Data' wizard had no effect.

New in SQLyog Community Edition 9.1 (Nov 14, 2011)

  • Features:
  • Added an option to ‘Search Data’ in a database or a table. Just enter any string and click on search to find the string - using same logic as internet search engines. Also search using regular expressions for complex searches - and tables with all matches can be accessed – even for UPDATE – with a single click.
  • Quite a lot of dialogs have been made resizable. This includes ‘Reorder Columns’, ‘Copy Table’, ‘Add Favorites’, ‘Organize Favorites’, ‘Export as SQL Dump’, ‘Export As (CSV/html/…)’, ‘Table Diagnostics’, 'Schedule jobs' and ‘Copy Database’. Those left that are not resizable now are either those where it would not make sense and some that will very soon be replaced with another interface.
  • Redesigned the ‘advanced’ option in Import External Data tool.
  • When using the option to define a display color for a connection the background color and the foreground color can now be defined independently.
  • Bug Fixes:
  • The ‘Job manager’ could fail to add jobs from the SJA wizards. This bug was introduced in 8.8.
  • Import External Data could fail to display all columns of target table when importing from a source containing lesser columns than target.
  • In TEXT mode the last row of data could fail to display if it contained a NULL value.
  • Export (to various formats) could cause SQLyog to ‘hang’ with tables with 500+ columns.
  • In ‘export as Excel XML’ it was possible to enter alphabetics for numerical parameters and the result of the export was unpredictable.
  • In ‘Import External Data .. advanced’ the complete job would abort even if user had only specified an abort condition for a single table. Also when the table was not present in the target and abort option was selected only the table structure was created and no data were imported. These bugs were introduced in 9.0.
  • In ‘edit’ menu the shortcut to ‘execute query’ was always displayed as F5 irrespective of user setting. This is a regression introduced in 9.0.
  • The 'Format Current Query' option in tool bar has been replaced with 'Format Query'. Now If there is a selection it will format the selection, otherwise it will format the current query.
  • Miscellaneous:
  • When opening SQLyog will now display a Query tab and a Data Search tab (and no Query Builder or Schema Designer tab as before).

New in SQLyog Community Edition 9.02 (Nov 14, 2011)

  • Bug Fixes:
  • The option in 'preferences' to 'Keep focus on SQL editor after query execution' did not have any effect. This bug was introduced in 9.0.

New in SQLyog Community Edition 9.01 (Nov 14, 2011)

  • Bug Fixes:
  • Introduction of the option to TRUNCATE TABLE in the ‘Import External Data Tool’ introduced a bug. If user selected DROP+ (RE)CREATE TABLE only structure would be created but data would not be imported

New in SQLyog Community Edition 9.0 (Nov 14, 2011)

  • Features:
  • Added an option (in GRID and FORM view) to look up/search valid values for columns having Foreign Key CONSTRAINTS.
  • In CSV-exports NULL-values can be written as a user-specified string. “\N’ is default for compliance with MySQL (SELECT INTO OUTFILE and LOAD DATA), but for use with other programs (such as spreadsheets) other options may be relevant.
  • Added an option to automatically add ‘child’ tables to selected tables (before it was only possible to add ‘parent’ tables) in Schema Designer and Query builder.
  • Added a “Change Background Color” option in Edit menu
  • A foreground color for text display contrasting a defined background color is now automatically provided by SQLyog in Object Browser and Connection tab.
  • The visual effects of tabs have been improved with continued scrolling support. There is a + icon next to the last tab which provides options to add new tabs.
  • In ‘Import External Data’ there now is an option to TRUNCATE target tables. Before only DROP+CREATE was possible.
  • In 'Import External Data' added an option to discard/clear column DEFAULTs. Some ODBC-sources use default specification that will not work with MySQL.
  • Bug Fixes:
  • Data entered from the GUI to mange ENUM/SET types were not escaped properly what caused problems with the ” ‘ ” (single quote) and ” \ ” (backslash) character.
  • Focus in Object Browser was lost when creating a Stored Procedure.
  • There is now a button/link to open the log file in each dialog wherever it is referred.
  • Fixed an issue where non-binary data were displayed as “(Binary/Image)”.
  • Now TAB/SHIFT+TAB keys will rotate through buttons, check-boxes and tools in Result/Table Data tabs.
  • Fixed a crash occurring when running Schema Sync and a Query Builder or Schema Designer TAB was active in the program main window.
  • Fixed a truncation issue while importing binary data from PrimeBase server.
  • When repeatedly stepping forward and backwards in SJA wizards most recent data entered by user could be lost and replaced with previous values.
  • Deleting multiple rows af a table without a Primary Key could crash SQLyog. This bug was introduced in 8.8.
  • Fixed a crash occurring when connecting on some Windows 7 systems with Service Pack 1 installed.
  • While formatting multiple queries the SQL formatter now does not add a new line if a new line already exists between two queries. Formatting multiple times would insert new empty lines between queries for each cycle.
  • A few more Query Formatter ‘refinements’.
  • When closing a Query tab or a Query Builder Tab user was promted to save even if he/she had 'blanked' the content of the tab. Now it does not unless the tab was populated from a file. SQLyog will still prompt user to save in this case.
  • A small GUI fix with the ENUM/SET dialog.
  • After dropping a column from Object Browser context menu focus in Object browser would change randomly. Now focus will be retained on the parent COLUMNS folder.
  • SQLyog could crash when attempting to delete rows from the table having a foreign key constraint. This bug was introduced in 8.82 due to improvements made in scrolling.
  • SQLyog could crash while the table contents were being loaded in table data tab and the user tried altering the table at the same time.
  • If server had timed out the connection SQLyog could fail to reconnect when opening a 'stored program' definition.

New in SQLyog Community Edition 8.82 (Nov 14, 2011)

  • Bug Fixes:
  • Exporting could fail with the 'PAD_CHAR_TO_FULL_LENGTH" sql_mode (introduced in MySQL 5.1.20) set globally. This bug was introduced in 8.8. We now use the '' ('empty') sql_mode for the background thread where the export is running

New in SQLyog Community Edition 8.81 (Nov 14, 2011)

  • Bug Fixes:
  • Fixed a serious bug in User Management where assigning a new password to a user created a new user instead. This bug was introduced in 8.8.

New in SQLyog Community Edition 8.8 (Nov 14, 2011)

  • Features:
  • In Schema Sync and ‘copy database’ connections are now identified with their color code as defined in the connection manager.
  • In ‘Import External Data’ import of Foreign Keys/relationships are now disabled as default when importing from Access and the interface has been clarified in this respect. The reason is that unless Access security settings are changed for the database it is not possible to import Foreign Keys/relationships and an error would occur if not security settings allowing for exposing relationships were defined.
  • Implemented a tooltip on Query tabs (including Query Builder and Schema Designer tabs) displaying full path to file (if any).
  • With HTTP-tunnel there is now an option to specify a MySQL socket file for connection to MySQL. Note that in that case MySQL ‘host’ and ‘port’ settings are ignored (if any). Due to this added functionality the tunneler file for HTTP-tunneling has been updated with this release.
  • Hexadecimal and binary/base2 strings can now be entered for any datatype using ” x’..’ ” and ” b’..’ ” notation in GRIDs. SQLyog will now not ‘quote’ such values starting with “x’” and “b’” when performing DML operations from the GRIDs.
  • Implemented support for the BIT datatype. In DATA and RESULT tab BIT’s will now display using ” b’..’ ” notation what in combination with the point above ensures that BIT data are updateable. Note that with HTTP-tunnel this is not functional in RESULT tab as PHP does not provide sufficient meta-information for a result set to decide column-widths.
  • Drastically improved memory management in DATA and RESULT tabs. This allows for larger result sets in memory and improves scrolling. This also fixes a bug introduced in 8.7 where scrolling could render wrong values displayed in the GRID.
  • Added an option in GUI to specify a sql_mode for the connection as well as for using the GLOBAL mode for the SESSION.
  • Added CTRL+ALT+L keyboard shortcut for switching GRID and FORM mode.
  • Bug Fixes:
  • SQLyog will now never use TIMESTAMP(14) but only TIMESTAMP. TIMESTAMP(14) returns an error in MySQL 5.5.
  • Fixed a truncation when importing data from ‘standalone’ Primebase server (note: not MySQL with PBXT storage engine. This never was a problem).
  • When editing a very large ENUM-list SQLyog could crash.
  • Schema Designer did not properly keep track of names of renamed tables.
  • Fixed a truncation of display in Form View with specific character sequences.
  • Right-clicking a JOIN line/symbol in Query Builder could fail to bring up the JOIN properties dialog.
  • The SQLyog editor highlighted a keyword followed by a dot as a keyword instead of recognizing it as an identifier.
  • While ‘rebuilding tags’ autocomplete did not return database objects.
  • The option in ‘preferences’ to ‘generate queries using backticks’ did not have effect when double-clicking an identifier name into the editor. This is fixed and additionally now also autocomplete will ´backtick`objects if the preferences’ option is selected.
  • Modified the SQLyog installer to prevent installing on an unsupported platform.
  • Fixed a bug in automatic indentation introduced in 8.7. The cursor was not indented correctly following the previous line if indentation was more than one SPACE or TAB character.
  • An orphaned PLINK instance could be left running when closing a SSH connection. It would typically happen with rather slow servers or connections and when connection was closed very shortly after it was establishedr.
  • When formatting multiple SQL queries SQLyog removed empty lines between queries.
  • There was no option not to save connection details when connecting with new connection details. The Connection Manager fix in 8.7 missed that point.
  • In data sync wizard "all columns" option in the GUI drop down should be checked and displayed. But the "all columns" option was unchecked and it also truncated to "A".
  • The 'Scheduler and Reporting' Tool (formerly 'Notification Services') was sending a blank email for successful execution of insert and update queries.
  • When a Primary Key column contained negative values Data Sync could sometimes skip some rows.
  • Immediately updating a newly inserted row could fail because of using wrong value in WHERE clause. This also affected rows inserted with 'duplicate row'.
  • Lots of GUI fixes and lots of internal optimizations.
  • Miscellaneous:
  • Notifications Services’ was renamed to ‘SQL Scheduler and Reporting Tool’

New in SQLyog Community Edition 8.71 (Nov 14, 2011)

  • Bug Fixes:
  • In Form View if a BLOB/TEXT column contained specific sequences of non-ASCII characters the button to open the BLOB viewer would not display correctly.
  • When updating from the RESULT tab and when using HTTP-tunnel identifiers were not `backticked`. For same reason the update would fail with identifiers containing SPACE or other characters requiring `backticks` in the statement. This bug was introduced in 8.7.
  • Copy Database’ GUI did not display the connection name of the source database.
  • The fix in 8.7 that autocomplete could sometimes delete the character following cursor position was not complete.

New in SQLyog Community Edition 8.7 (Nov 14, 2011)

  • Features:
  • Added an option to reorder TABs using drag’n'drop in the GUI. The option is available for connection tabs as well as Query/Query Builder/Schema Designer tabs.
  • Added ‘FORM view’ option (in addition to ‘GRID view’ and ‘TEXT view’ already available) for managing data in DATA and RESULT tabs. ‘FORM view’ will display one row at a time and is in particular convenient when entering data from the keyboard. Auto_increment columns are handled. Other CONSTRAINTS must be handled by user. FORM view is an ENTERPRISE/ULTIMATE feature.
  • As a consequence of the above CTRL+L keyboard shortcut will now ‘toggle’ between TEXT mode and either GRID-mode or FORM-mode (which is active).
  • The Query Formatter is now completely rewritten. In principle all types of SQL statements are now supported and all limitations with the old implementation are lifted.
  • Inside ‘pseudo comments’ (like /*! .. this .. */) “paranthesis’es matching” is now enabled. Inside plain comments it is still disabled.
  • The Editor now has a ‘folding option’. Multi-line code and comment blocks between bracket-pairs, BEGIN-END pairs, C-style comment pairs (/* and */), WHILE-END WHILE pairs, LOOP-END LOOP pairs, REPEAT-END REPEAT pairs and CASE-END CASE pairs can now be ‘folded’ in/out (ie: hidden or unhidden).
  • Autocomplete will now backquote table name (+ routine name etc.) if databasename is backquoted when inserting first-mentioned after a “.” (dot).
  • There is now no size limit on files to be opened in the editor (except for available memory).
  • When inserting rows both GRID-view and FORM view will now indicate auto_increment columns as (Auto) for easy identification. Normally user should not enter those, but let the server handle.
  • The fix for slow initialization with large autocomplete databases that was introduced in 8.62 and reverted again in 8.63 is now included again. It has stabilized with this build.
  • When backing up 'all databases' with 'scheduled backup' the Performance_Schema database (as of MySQL 5.5) will now not be included in the backup. This is similar to how Information_Schema always was handled.
  • We have reverted back the automatic proxy detection in upgrade-check. We had a few reports that it could cause a crash when the machine was awakening from standby and hibernation. Only Win7 Professional edition seems affected.
  • When updating from RESULT tab we will now handle the database context automatically. The database context as selected by user is not used. Note that this applies to MySQL 4.1+ server and when not using HTTP-tunnel (as pre-4.1 MySQL and PHP do not expose the database in the result set)
  • The caption (in 'tools' menu) ‘Restore from SQLdump’ was changed to ‘Execute SQL script’.
  • Bug Fixes:
  • Fixed formatting issues with text-mode if multiple multi-line string columns were displayed.
  • The ‘persistence setting’ for ‘all rows’ in DATA tab would sometimes be forgotten.
  • If scrolling in GRIDs is done using Scroll Bar (including Scroll Bar context menu) focus will now not change and will remain on the previously selected row. However navigation between rows in GRID using Pageup/PageDown will still change the focus between rows.
  • If more than 9 Query etc. tabs were open it was not possible to navigate beyond the 9'th using keyboard shortcuts. Now ALT+9 will select the last tab (for connection tabs same was implemented in 8.5).
  • Improved vertical scrolling in GRIDs with a large number of rows displayed.
  • EVENT” was not recognized as a keyword by syntax highlighting and autocomplete. Also "ARIA" (the new name for the 'maria' Engine in mariaDB 5.2) is now recognized as a keyword.
  • Schema Sync will now show columns in the order they are defined in the table. Before they were alphabetically sorted.
  • Removed redundant COMMENT clause in the ALTER script generated by Schema Sync.
  • If 0 (zero) was given as the default value for a timestamp column CREATE/ALTER TABLE table would raise a syntax error, as SQLyog was quoting the default value as ’0'. Also specifying NULL as default (what is redundant for a NULLable column) would fail for similar reasons.
  • two hyphens) followed by TAB (not only SPACE) is a valid MySQL single-line comment. We did not handle TAB in this context.
  • Fixed a crash while copying to clipboard from table data/result tab.
  • Autocomplete could sometimes delete the character following cursor position.
  • CREATE/ALTER TABLE now ignores NULL entered as default for a NULLable column. It is redundant. Before invalid syntax was generated.
  • With specific user operations in Connections manager a connection could be saved even if user replied NO the the ‘save question’. Also the connection manager now does not prompt user to save changes if only password/passphrase is changed and it is selected not to save password/passphrase.
  • The FIND dialogue sometimes failed to keep focus on the FIND dialogue itself (recent fix was not complete).
  • The dialog for defining ENUM/SET values was not showing when the ENUM/SET cell got focus using keyboard(when using mouse it was working as expected). Also it could open when another cell in same row of GRID had focus.
  • When an existing jobfile for Data Sync was opened the order-of-tables in the jobfile was not honoured. It is now. This is in particular relevant for users using TRIGGERS as there is no way temporarily to disable TRIGGERS in MySQL.
  • SJA for Linux was exporting file size upto 2 GB only (a compiler flag allowing for 'large files' was missing in build script).
  • SJA for Linux did not show any error in mail or in console if it failed to connect to server. We will now notify both places (provided that 'send mail' option for the job is enabled).
  • With a large number of rows displayed GRID could display garbage and fail to identify properly BLOB/TEXT data belonging to the row.
  • When a new row had just been added from GRID it could be deleted even if user specfied another row to be deleted.
  • Horizontal scroll bar in Query Editor and History Tab was not proper with long lines.
  • Several small GUI fixes.

New in SQLyog Community Edition 8.63 (Nov 14, 2011)

  • Bug Fix:
  • The fix for slow initialization with large autocomplete databases in 8.62 has been reverted with this build. It introduced other issues like a possibility of SQLite database corruption and crashes. The fix will be added to 8.7 development tree when stable.

New in SQLyog Community Edition 8.62 (Nov 14, 2011)

  • Features:
  • INFO tab/HTML mode now displays a count of each type of database objects
  • SJA now supports an additional -r parameter that tells how big CHUNKS should be when copying to an empty table. The -r parameter has only effect with Data Sync jobs and is ignored with other types of jobs. This is a command line option only that is not supported from the GUI Wizard
  • GUI improvement in Data Sync Wizard clarifying the difference between syncing ‘All tables’ (existing at any time) and all tables existing at the time of building the job. It is now also much easier to select ‘almost all tables’ for a Data Sync job
  • Data Sync will now ignore differences as regards indexes on source and target tables except for the Primary Key/Unique Index used for sync. There is no need to require that all indexes are the same
  • SJA for Linux had a dependency on the ‘libstdc++.so.5' shared library that is not installed as default on some recent Linux distros. This and similar dependencies have been solved with this build. The download size has increased but it is necessary to ensure that SJA will run ‘out of the box’ on all Linux systems
  • Bug Fixes:
  • While Viewing Advanced Properties of table SQLyog executed SHOW TABLE STATUS with no LIKE clause. That could be slow
  • Fixed a crash when copying to clipboard from RESULT tab
  • If an external file was imported through BLOB-viewer the ‘dirty flag’ displaying a warning that data were not saved would not display in GRID
  • Changed the keyboard shortcut for Save Changes in User Manager for consistency with normal Windows practice
  • Fixed a crash when deleting a row from RESULT tab
  • Invoking specific keyboard shortcuts (Ctrl+TAB, Ctrl+F4) could cause a crash if a background connection thread (Schema Sync, Copy Database, Restore from SQL Dump, Back up database as SQL Dump) was running
  • Working with TRIGGERS could be very slow (in Schema Sync, backup etc.). This is due to an issue with Information_Schema. We now use a SHOW syntax that is not affected
  • Schema Sync prefixed a VIEW-name with the database name and thus it failed if source and target databases were not named identically
  • Schema Sync did not consider ALGORITHM and SQL SECURITY -clauses for a VIEW
  • When executing multiple queries the ‘execution time’ information displayed in status line was for a single query. Now we will aggregate for all queries
  • Removed result tab and profiler tab from a newly opened query tab. There is no information to display at that time
  • Find & Replace was setting the focus back to the editor whenever a match was found
  • SJA wizards were always opening up in the center of primary monitor even though SQLyog was running in another monitor
  • Right clicking on scroll bar of different windows was not popping up the scroll context menu
  • Data Sync was ignoring any table names with more than one leading SPACE character saved in job files
  • Data Sync was not allowing anonymous users to connect while reading the connection details from job files
  • Parenthesis’es highlighting inside ‘single quoted string’, “double quoted string” and `quoted identifier` is disabled now
  • Fixed a crash that could happen due to memory corruption while adding queries executed in Schema Designer to History tab
  • When updating a resultset from RESULT tab SQLyog failed to use the Primary Key alone in the WHERE clause if the SELECT query populating the RESULT tab used a table alias in the FROM clause. Updates could then fail if there were floating point columns in the resultset. Also when adding new row in such case defaults were not displayed in the GRID
  • Initialization of the program could be slow if user had very large SQLite databases used by autocomplete
  • Vertical scrolling in RESULT Tab or DATA Tab was saving the unsaved changes

New in SQLyog Community Edition 8.61 (Nov 14, 2011)

  • Features:
  • INFO tab/HTML mode now displays a count of each type of database objects
  • Bug Fixes:
  • Fixed a crash on Vista+ with ALTER TABLE. It happened due to changing compiler to Visual Studio 2010 in 8.6. The older Visual Studio version used handled this bug in our code without crashing
  • Fixed a buffer overrun issue with long column headers that also could cause SQLyog to crash. Also this was a similar issue due to upgrading the build environment in 8.6
  • SQL formatter inserted garbage value if query contained '%'
  • "Parenthesis'es highlighting" is now disabled inside MySQL-comments. Before an unmatched parenthesis in a comment would cause 'mis-matching' of parenthesis'es in the executable SQL outside comments
  • Fixed some incorrect MySQL API calls with HTTP tunneling. This issue was reported internally only
  • The RESULT tab in text mode was showing incomplete data with multi-line strings
  • Import external data now always uses UPPERCASE for keywords in queries sent to the ODBC-source as some ODBC-sources require this
  • Table Data tab was unable to perform custom filter when there was an escape character in the filter text
  • SQLyog was hanging while showing filter tooltip with more than 80 charecters in Table Data tab

New in SQLyog Community Edition 8.6 (Nov 14, 2011)

  • 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). Also MySQL ‘anonymous users’ are now fully supported. Now both username and hostname may be left as an empty string. A confirmation popup will appear, though
  • Added a ‘custom filter’ option in DATA and RESULT tab GRIDs. With this option, user can filter on any value from any cell
  • Added options to filter on ‘%value’ and ‘value%’ in both the ‘Filter’ menus and ‘Custom Filter’ dialogs
  • Added a tooltip to the 'filter' icon in DATA and RESULT tabs displaying current filter settings
  • CTRL+INS and SHIFT+INS keyboard shortcuts will now copy and paste (like CTRL+C and CTRL+V) in GRIDS
  • Added support for “parenthesis’es matching” in the editor TAB as well as the small query editors in 'Notifications Services' and 'Import External Data' wizards. You may find what parenthesis/bracket matches another one by simply positioning the cursor after a bracket. The actual bracket and its match will highlight. Note that this feature will work with any string – whether valid SQL or not. Both plain parenthesis’es, square brackets and curly braces are supported (independently of each others)
  • If “save password” is checked for a connection, then focus in Connection Manager will be on the connection name – else it will be on the password. Before focus was always on password when Connection Manager was opened
  • Improved performance by optimizing code when SQLyog was internally performing string comparisons (what it does a lot)
  • 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 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
  • When opening a ANSI-encoded file with non-ASCII characters the encoding would not be detected correctly, and the content would garble (no issue with UTF8 and (Windows) UTF16-encoded files). This bug was introduced in 8.3
  • SQL exports added redundant Unix-linebreaks, what would cause some editors to display an empty line. This bug was introduced in 8.4
  • SQLyog could crash when connecting from ‘import external data’ wizard to a source database with a huge number of tables in it
  • The Windows Explorer dialog for selecting files to be opened could display garbage characters at the beginning with non-English locales. The reason was SPACE characters incorrectly added by SQLyog
  • Fixed a GDI leak occurring when switching between TABS in the GUI (editor TABS or connection TABS)
  • Fixed a crash that could occur when closing the copy database dialog
  • Create Index dialog was not resizing/positioning the grid properly. Sometimes the issue could render the dialog unusable
  • Other small GUI fixes
  • Miscellaneous:
  • With this build we have changed our build environment from Visual Studio 2003 to 2010
  • Windows 2000 is no longer supported

New in SQLyog Community Edition 8.55 (Nov 14, 2011)

  • Bug Fixes:
  • If user edited data in RESULT-tab GRID and changed display mode from grid-mode to text-mode before saving changes, 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.
  • 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.

New in SQLyog Community Edition 8.54 (Nov 14, 2011)

  • 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

New in SQLyog Community Edition 8.53 (Nov 14, 2011)

  • 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.

New in SQLyog Community Edition 8.52 (Nov 14, 2011)

  • Bug Fixes:
  • Solved an issue with SSH connection when putty is present. PLINK was using the default settings of putty to connect, resulting error in connection (introduced in 8.5).
  • Solved an issue with SSH connection where SQLyog was reporting Error No. 2003 even if the MySQL port was correct (introduced in 8.5.1).
  • If MySQL connection used "anonymous user", SJA was throwing an error.
  • For create/alter database, collation drop-down list did not populate values correctly if TAB key was used to select the charset.
  • In Scheduled backup if the database name contains Non-ANSI characters, export was failing when 'ALL database' option was selected.
  • Fixed the way keyboard shortcuts Ctrl+Tab and Ctrl+Shift+Tab behave.
  • Miscellaneous:
  • Selecting a connection from the drop-down list of connection window is now faster.
  • Keyboard shortcut Ctrl+W now closes the current connection tab. Keyboard shortcut for the Database Synchronization tool has been changed to Ctrl+Alt+W.

New in SQLyog Community Edition 8.51 (Nov 14, 2011)

  • Bug Fixes:
  • The 'Export Table Data As...' option from the object browser menu was exporting just the column headers, this was introduced in 8.5 GA.
  • In the Notification Services wizard, if the field contained data with quotes, SJA was inserting extra slashes along with the field value.
  • The 'timeout' for establishing connection using SSH has been increased from 15 seconds to 30 seconds (15 seconds was too less to establish connection with slow SSH servers).

New in SQLyog Community Edition 8.5 (Nov 14, 2011)

  • Features:
  • This version introduces a tabbed interface for connections. Tabs will be colored (if chosen) like the Object Browser. Note that the meaning of shortcuts Ctrl+number have changed: they will now shift between connection tabs. The old Ctrl+number shortcuts have been changed to Ctrl+Shift+number.
  • In connection manager the color code for a connection is now indicated.
  • Added an option to 'duplicate row' from DATA tab GRID context menu. Tables with auto_increment columns are handled. Note that handling all other CONSTRAINTs is user's responsibility.
  • When a GRID operation returns a warning there is now a clickable link for SHOW WARNINGS. Note: this is not implemented for HTTP-tunneling.
  • In RESULT tab data can now be filtered client side as already possible in Table Data.
  • Menu option 'Paste SQL Statement' will format the query as per the SQL Formatter Preferences settings.
  • Tabs can now be closed with the click of middle mouse button (mouse wheel).
  • Keyboard shortcut F3 for 'Find Next' in Query Editor and Result/Table Data tab in Text mode. Note: Not implemented in BLOB-viewer.
  • Shift+click can be used to select/deselect multiple objects in tree-view control of Copy Database, Export, etc.
  • Added a menu option to 'Find Next'in 'edit' menu and query editor context menu.
  • Find/replace settings are now persistent within the session.
  • Improved the speed of (csv, html, xml, excelxml and sql) - exports from RESULT tab.
  • Files can now be drag'n'dropped into the program window and file will be opened in a new Query/Schema Designer/Query Buillder tab depending on file type (like 'file .. open' menu). Same is implemented in SJA wizards where a file can be opened.
  • Bug Fixes:
  • It was not possible to enter a value higher than 999,999 for OFFSET and LIMIT in DATA and RESULT tabs. Now up to 15 digits are allowed.
  • No Database Selected' error could occur with Data Sync after a reconnect. We are now prefixing table names with database name in Data Sync.
  • Shortcut for copying 'Ctrl+Insert' was not preserving the letter case.
  • Fixed a rare issue where the SQLyog configuration file (SQLyog.ini ) could be corrupted – and even deleted – if multiple program instances using same .ini instance were running simultaneously. Scenarios include the situation where user by mistake (double)clicked the program icon twice.
  • Autocomplete could fail to select the items from the listbox (popup window) display after typing "." if a '_' (underscore) character was present with list box items. Technically this was an incompability between sorting in SQLite, Scintilla and standard C functions. We have added our own code to handle this. But note that for performance reasons it is not handled perfectly with Ctrl+Space and Ctrl+Enter where it can be necessary to use arrow-keys for selection in such case.
  • Several small fixes with 'Find Next' in editor and Blob Viewer.
  • SJA wizards would sometimes fail to specify the correct jobfile path to the Windows Task Scheduler.
  • The grid control in Manage Index dialog did not resize properly with some monitor resolutions.
  • The upgrade check dialog popped up on top of other running applications.
  • Miscellaneous:
  • Use of 'compressed protocol' is now default for new connections. Our test tell that the positive effect of using it can be huge when it should be used and the negative effect when using it when it should not, is very small.
  • Added keyboard shortcut Ctrl+9 for selecting last connection tab.
  • In RESULT/DATA tab all Copy related options are grouped together.
  • Selecting this option 'Copy Selected Row(s) to Clipboard' we can now copy the selected row to the clipboard with out checking a row on the grid.
  • Minimized the number of pop-ups while creating a Table.
  • The PLINK shipped with SQLyog was updated. This solves rare connection problems with specific SSH configurations. Mostly connections to very recent Linux distributions were affected.
  • Also the SQLite library within SQLyog has been upgraded to the latest version. The new version of SQLite improves stability as compared to the previous version where a possible journal file corruption was not handled.
  • If user does not specify a file extension for the jobfile the wizard will add the standard extension '.xml'.
  • The option in 'preferences' to 'Add keywords in UPPERCASE' is removed. It was redundant since introduction of the 'auto-capitalization' feature.
  • Dialog fonts are now default system font.
  • In order to save space Query Builder and Schema Designer tabs will now show the filename without ('.queryxml' and '.schemaxml') extensions.
  • Installers will now have two numbers after the numbers identifying the version no. (identical to common naming conventions for RPM installers for Linux). This is done in order to ensure that every installer we build has a unique name. Various proxy systems would sometimes cache and provide the old file on download request.

New in SQLyog Community Edition 8.4 Beta 1 (Mar 29, 2010)

  • 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.

New in SQLyog Community Edition 8.32 (Mar 29, 2010)

  • 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.

New in SQLyog Community Edition 8.3 (Mar 11, 2010)

  • 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.

New in SQLyog Community Edition 8.22 (Jan 30, 2010)

  • Bug Fixes:
  • ‘Test connection’ would succeed even if a non-existing database was specified in the database field. Connection would next fail.
  • Database name (if any) would erase on clicking OK in error dialog in connection window.
  • HTML exports could drop the first character of string output.
  • With multimonitor setup and SQLyog on the right screen some rarely used dialogues would pop up on left screen.
  • Copy database/table will now display ‘connecting to source/target server’ while connecting. If establishing connection took more than a few seconds users could have the impression that nothing was happening.
  • An extra RESULT tab could appear when executing a query. This bug was introduced in 8.2. Professional and Enterprise editions were affected.
  • In notification wizard sending mail would fail if there was no semicolon after the query and “include original query” option was checked.
  • With more than 65 536 (2^16) rows displayed in GRID, the GRID scrollbar would expose strange behavior. We were using a scroll control using 16 bit integers internally. New scroll control handles +4 billion rows.
  • In Wine when displaying very wide tables and result sets (like 500+ columns) the column header could disappear. The underlying reason was that Wine failed to render a gradient as transparent but rendered it as opaque instead.
  • Horizontal scrollbar in GRID would sometime not appear when executing a query returning a large number of columns if not scrollbar was required for previous query.
  • With larger than ‘normal’ DPI setting the BLOB Viewer header would not display properly.
  • ‘Export as SQL-dump’ dialogue was redesigned to allow for longer files paths.

New in SQLyog Community Edition 8.21 Beta 2 (Dec 23, 2009)

  • Bug Fixes:
  • Auto-complete and syntax highlighting did not recognize keywords archive, blackhole, federated, example, maria, pbxt, federatedx, falcon and mrg_myisam.
  • Notifications Services/’Send Query to Email address’ option did not send a mail if an error occurred. Now a mail listing the error will be sent.
  • We did not validate client-side if user specified a default value for an auto-increment column.
  • The automatic selection of local port to be used with SSH-tunnelling (as introduced with beta 1) did not work properly on Wine.
  • In DATA and RESULT tab the context menu was only working from GRID-cells. Now it also does from GRID headers and ‘whitespace’ in the tabs.
  • Other small GUI fixes.
  • Miscellaneous:
  • Note that this beta 2 ships with the 8.2 documentation/help file unchanged (and thus a few screenshots are not up to date).
  • The ‘Objects’ menu was renamed to ‘Others’

New in SQLyog Community Edition 8.21 Beta 1 (Dec 18, 2009)

  • Features:
  • Now SJA will also send mail alert if job aborted due to MySQL error. Before it was only internal SJA error.
  • The local port used by SSH-tunneling will now be selected automatically. This will avoid conflicts in case multiple programs use SSH. Also with Data Sync from command-line/scheduler it was possible to use same port for both connections what would effectively sync a server with itself.
  • Caption for ‘Parse’ button in Notification Services Wizard was changed to make it clear that it will actually execute the statement(s) entered. There is no way to let the server parse a statement except for executing it.
  • Connection windows for SSH connections will now list SSH host details in the title bar.
  • Tooltips for an icon will now list the keyboard shortcut performing same action.
  • Bug Fixes:
  • Continously clicking the ‘Calculate’ button in Schema Optimizer in a fast manner could crash SQLyog.
  • The keyword.db file (used by auto-complete and syntax highlighting) is now read only. Various validators for Windows7-compatibility would report that SQLyog wrote to “Program Files” folder at runtime (what it did not).
  • When copying to clipboard an out of memory error could occur also when there was enough memory.
  • The table menu will now indicate what storage engine is currently used for the table.
  • Other small GUI fixes
  • Miscellaneous:
  • Note that this beta1 ships with the 8.2 documentation/help file unchanged (and thus a few screenshots are not up to date).

New in SQLyog Community Edition 8.2 RC (Nov 18, 2009)

  • A calculation error could cause export tools to create BULK INSERT statements larger than specified by user.
  • Import External Data Tool will now always map any autoincrement type from ODBC sources to a MySQL autoincrement integer. Before this datatypes that could autoincrement on source but not in MySQL (example: a SQL Server ‘decimal autoincrement’) failed to import.
  • Now Import External Data Tool will convert SQL Server ‘GETDATE()’ to MySQL ‘now()’. Before this an error occurred at import with GETDATE()’s.
  • Structure Sync will now query Information_Schema for a VIEW definition. MySQL sometimes returns ‘databasename.viewname’ and not just ‘viewname’ when using SHOW CREATE.
  • Fixed a Object Browser flickering issue when refreshing.
  • The fix in 8.15 for the issue that Windows Vista and higher could warn that SQLyog was not properly installed was not complete. It could still happen.

New in SQLyog Community Edition 8.2 Beta 1 (Nov 10, 2009)

  • Features:
  • Added a ‘Schema Optimizer’ feature. Based on “procedure analyse()” it will propose alterations to data types for a table based on analysis on what data are stored in the table. The feature is available from INFO tab/HTML mode. Refer to documentation for details.
  • A table can now be added to Query Builder canvas multiple times. A table alias is automatically generated for second and higher instance of the table. This is required for special queries like self-JOINs (note: table alias support in Query Builder is an ongoing process).
  • In the ‘Import External Data’ wizard same import settings can now be applied to all tables in one operation.
  • In MESSAGES tab we are now displaying the query if error occurs during execution in order to make it easier to identify what query raised an error when executing multiple statements.
  • Bug Fixes:
  • ‘Import External Data Tool’ -TRIGGERS did not use the Primary Key for the WHERE-clause if a PK existed on source (all columns were used with the WHERE instead). This could cause problems with tables having Floating Point data.
  • A malformed XML-string could cause failure to connect with HTTP tunneling. This was a rare issue only.
  • After DROP a ’stored program’ followed by CREATE same, autocomplete would not recognize the ’stored program’ unless after a program restart.
  • ‘duplicate table’ has an option to duplicate triggers defined ON that table, but the way we named the new trigger could cause inconsistencies. Now the new trigger will be named ‘oldtriggername_newtablename’.
  • Autocomplete was not functional with names of Triggers and Events.
  • In MESSAGES tab font could change if non-ASCII characters were displayed.
  • The display of the optimized query from EXPLAIN EXTENDED is now truncated to 2 KB. With long BLOB/TEXT data there will need to be some limit.
  • ALTER TABLE failed to rename a column when old and new column name only differed by letter-case. Actually the dialogue just shut down.

New in SQLyog Community Edition 8.17 (Oct 28, 2009)

  • Bug Fixes:
  • When connected to a 5.0 server compiled without PROFILING option and with Query Profiler/SHOW PROFILE feature enabled SQLyog would still send PROFILING-related queries. It was not properly detected that the server did not support this. MySQL versions from 5.1 and up (also when compiled without PROFILING option) were not affected.
  • In DATA and RESULT tabs/text mode unicode/non-ASCII characters could cause a change of the font that was used for displaying data. This was an old bug from when introducing full unicode support in 6.0.
  • In RESULT tab BLOB/TEXT data would sometimes not display beginning of data in GRID. This bug was introduced in 8.15.
  • Miscellaneous:
  • EXPLAIN EXTENDED option is now disabled as default in Query Profiler

New in SQLyog Community Edition 8.16 (Oct 21, 2009)

  • Bug Fixes:
  • Exports as Excel-XML was broken in 8.15 . Empty strings and ZERO’s occurred instead of data.
  • ‘Search and replace’ could truncate the result. Also this bug was introduced in 8.15.
  • Miscellaneous:
  • SQLyog Application Manifest was updated to return version information.

New in SQLyog Community Edition 8.15 (Oct 17, 2009)

  • Features:
  • Added an option to execute SHOW WARNINGS automatically if the ‘warning-count’ is not 0. The output will appear in MESSAGES tab. Note: this is not implemented for HTTP-tunneling.
  • * Improved the memory handling in GRIDS with BLOB/TEXT columns. This fixes some slugginess when scrolling a GRID containing such data.
  • Bug Fixes::
  • A dump containing VIEWs created on an early 5.0-server could fail to restore on recent servers. The underlying reason is a bug with the ‘default’ column in the output of SHOW FULL FIELDS on the early 5.0 servers. But we can avoid using this information and this is what we did now.
  • Copy database/table from a 3.x or 4.0 server to a more recent server failed with column names containing special characters.
  • If a sqlyog.ini files exists in installation folder it should be copied to ‘AppData’ folder. This is required for upgrading from versions before 6.06. However with latest releases an empty file was created in ‘AppData’.
  • The ‘Import External Data Tool’ could truncate strings when importing data from a 4D database. It is actually a bug in the 4D ODBC driver but we found a workaround.
  • SSL-connections failed if authentication keys were created with cipher option.
  • SQL-exports generated INSERTS for MERGE and FEDERATED tables.
  • In INFO-tab/text-mode we will now not highlight ’string literals’. A comment with an odd number of quotes would make following lines display with ’string literal’ highlighting/coloring.
  • * When connected with SSH-tunneling to a Windows machine with Cygwin SSHD the bash.exe process created for each connection did not close again.
  • CREATE TABLE .. advanced options did not set some create-options to ‘default’.
  • Execution of some queries would be slow with Query profiler/EXPLAIN extended selected. Most important queries with a UNION were affected. Technically it was an issue with the Query Formatter code and how it ‘hooked’ into the program. This bug was introduced in 8.0.
  • Windows Vista and higher could warn that SQLyog was not properly installed due to lack of an Application Manifest. It was false alarm but now such Manifest is included with the installer.

New in SQLyog Community Edition 8.15 RC2 (Oct 10, 2009)

  • Bug Fixes:
  • Execution of some queries would be slow with Query profiler/EXPLAIN extended selected. Most important queries with a UNION were affected. Technically it was an issue with the Query Formatter code and how it ‘hooked’ into the program. This bug was introduced in 8.0.
  • Copy database/table could be slow if BULK INSERTS option was selected in ‘preferences’. This bug was introduced in 8.15 beta 1.
  • 8.15 RC could crash when executing a LOAD DATA statement. This first RC was build with a recent 5.1 client library. Before 8.15 RC we used a 5.0 library. We have now reverted back to 5.0 (5.0.86 client library is used with this release). Issue with the 5.1 client library is not fully understood but it may be related to known memory issues reported with it.
  • Miscellaneous:
  • Functionality change: Before this release we stripped out the database name from Stored Program and View SQL-code when generating SQL-dumps and and when copying a database to another host. Also Schema Sync did with VIEWs. This was in order to make it easy to import/copy to another database. However with tables named identical to the database and when database names was a substring of a table name it failed sometimes. We realize now that SQL code inside Stored Programs and Views may be so complex that parsing for the database name and stripping it is not safe. With this release we have stopped this ’stripping’ and Stored Programs and Views will be dumped by SQLyog identically to what ‘mysqldump’ does.

New in SQLyog Community Edition 8.15 RC (Oct 1, 2009)

  • Bug Fixes:
  • Copy database/table from a 3.x or 4.0 server to a more recent server failed with column names containing special characters.
  • If a sqlyog.ini files exists in installation folder it should be copied to ‘AppData’ folder. This is required for upgrading from versions before 6.06. However with latest releases an empty file was created in ‘AppData’.
  • The ‘Import External Data Tool’ could truncate strings when importing data from a 4D database. It is actually a bug in the 4D ODBC driver but we found a workaround.
  • SSL-connections failed if authentication keys were created with cipher option.
  • SQL-exports generated INSERTS for MERGE and FEDERATED tables.
  • In INFO-tab/text-mode we will now not highlight ’string literals’. A comment with an odd number of quotes would make following lines display with ’string literal’ highlighting/coloring.
  • When connected with SSH-tunelling to a Windows machine with Cygwin SSHD the bash.exe process created for each connection did not close again.
  • CREATE TABLE .. advanced options did not set some create-options to ‘default’

New in SQLyog Community Edition 8.15 Beta 1 (Sep 1, 2009)

  • Features:
  • Added an option to execute SHOW WARNINGS automatically if the ‘warning-count’ is not 0. The output will appear in MESSAGES tab. Note: this is not implemented for HTTP-tunnelling.
  • Improved the memory handling in GRIDS with BLOB/TEXT columns. This fixes some slugginess when scrolling a GRID containing such data.
  • Bug Fixes:
  • A dump containing VIEWs created on an early 5.0-server could fail to restore on recent servers. The underlying reason is a bug with the ‘default’ column in the output of SHOW FULL FIELDS on the early 5.0 servers. But we can aviod using this information and this is what we did now.

New in SQLyog Community Edition 8.14 (Aug 20, 2009)

  • Bug Fixes:
  • When backing up a VIEW a temporary table was created on . That could fail if user did not have TMP_TABLE privilege or if the table violated server or storage engine restrictions for tables (but note that we still write statements that create and later drop a ‘dummy’ table when restoring, as this is the only safe way to backup/restore VIEWS defined on VIEWS). We hope to be able to find a better solution soon, but the issue is a server issue that affects all clients - refer to http://bugs.mysql.com/?id=46779.
  • When updating from GRID’s SQLyog sends a SHOW CREATE TABLE to ensure that table definition has not changed. But incomplete syntax was used (”SHOW CREATE TABLE `table`” - not “SHOW CREATE TABLE `database`.`table`”). With the new reconnect implementation in 8.13 that could raise the error ‘no database selected’ after a reconnect.

New in SQLyog Community Edition 8.13 RC (Jul 31, 2009)

  • Bug Fixes:
  • ‘reorder columns’ threw away ” (empty string) DEFAULTs for string columns.
  • When data were changed in GRIDs and the GRID-curser was moved to another row of the GRID by right-clicking in a cell of another row of the GRID, no UPDATE statement was sent (left-click and arrow-down key worked as expected).
  • With low wait_timeout setting on it could happen that Data Sync took more time than this setting to prepare a BULK INSERT statement. Connection to would be lost and sync not completed. We now SET wait_timeout = 28800 in Data Sync. Also ‘restore from SQL dump’ will now do the same.
  • Mails sent by SJA could truncate a HTML tag for background color. ‘white’ would become ‘hite’. The display with specific email clients was unpredictable.

New in SQLyog Community Edition 8.13 Beta 3 (Jul 18, 2009)

  • Bug Fixes:
  • The fix in beta 2 with TIMESTAMP ON UPDATE and Data Sync introduced a new issue. An additional `backquote` could be generated in statements for tables having a TIMESTAMP column - what would cause failure to sync affected table.
  • If user did not have SELECT privilege to the `mysql`.`proc` table ALTER STORED PROCEDURE/FUNCTION failed silently. Actually nothing happened. Now we return an error. Please read this FAQ to understand the privilege issue with ALTER STORED PROCEDURE/FUNCTION in SQLyog.

New in SQLyog Community Edition 8.13 Beta 2 (Jul 15, 2009)

  • Changes (as compared to 8.13 beta 1) include:
  • Features:
  • When updating from DATA or RESULT grid the UPDATE statement will now only list columns that were changed. That results in more readable statements and may also improve performance with ‘wide’ tables and tables with large BLOB/TEXT columns.
  • As a consequence of the above the restriction, that a grid containing spatial or binary data could not be updated, has been lifted (but such columns themselves still cannot be updated from the grid).
  • Added an option to perform backups in a single transaction (similar to ‘mysqldump’ “–single-transaction” option).
  • The connection manager has been redesigned to allow for longer connection names. Also the ‘…’ button was renamed to ‘rename’ (what was what it always did).
  • Added support for MySQL compressed protocol in both SQLyog GUI and SJA. Please see detailed note below.
  • Added an option for user to specify the timeout setting for the session (note: it will work with MySQL 5.0 and up only as earlier versions do not support SESSION variables). Please see detailed note below.
  • Now SQLyog logs to the sqlyog.err file if memory allocation fails with string manipulation (for example when handling blob/text data where a single value may be larger than available memory).
  • Version parameter was added to SJA. You can now execute “sja –version” or “sja -v” and version will be returned. Before only the file size could be used to detect the SJA version.
  • Now full GUI support for all charsets added to MySQL after 5.1. Everwhere SQLyog presents user for a list of available charsets and collations the server will be queried about this information. Before it was not like that everywhere!
  • Emptying a database rendered Autocomplete non-functional for the session.
  • If the custom size for bulk insert in ‘preferences’ is greater than server default, then SQLyog will use the server default for generating BULK INSERT statements. Users overlooked/forgot that they had specified a setting. As a result backups that would not restore on same server could occur. Also now user specification is restricted to 5 digits (what means it will have to be less than 100 MB).
  • The various options available for backups have been reorganised in GUI to make it more clear what options have effect on the source server while backup job is running and what options are options that are written to the file.
  • A new query tab can now be opened by double-clicking in the unused space to the right of existing open tabs.
  • Bug Fixes:
  • SQLyog could fail to save properly from RESULT tab if PK-column(s) were not displayed in GRID (an incorrect WHERE-clause was generated). This bug was introduced in 8.1.
  • Data Sync could throw an incorrect ‘AUTO INCREMENT definition mismatch’ error for data types (like TIMESTAMP type) where auto-increment does not apply with specific schemas. Also this bug affected Schema Sync.
  • Fixed a crash in Scheduled Backup.
  • Fixed an issue with Schema Sync if the same ’stored program’ was formatted differently on source and target. Target was not always synced properly and SS would detect differences forever.
  • On Wine Data Sync could pop up a message that SJA had crashed. But actually it only crashed after user clicked OK in the dialogue.
  • Miscellaneous:
  • SQLyog reconnects are now coded differently. The new code means that with SSH-tunnel it will now not be necessary to re-instantiate PLINK (the running PLINK instance will be used).
  • Additional comments:
  • DO NOT take for granted that use of compressed protocol will always increase performance, because the truth is that most often it will make things slower. Use of compressed protocol will decrease the amount of data to be transferrred over the network, but it will result in additional load on both the server and the client (due to compressing and uncompressing). You should never use the option when connecting to MySQL on local machine, on local network or over a fast Internet connection. With slower connections however using this option may improve overall performance. It is impossible to be more specific as most Internet connections have asymmetric properties that differ across Internet providers and telecom companies.
  • The option to define timeout for the session (different from the global setting) is possible with MySQL servers from 5.0 and up. However most users will not need to care about it - not even if server (global) timeout setting is low. SQLyog will reconnect if connection was lost since last query was run. Most often user does not even notice. However we have reports of situations where the network takes very long time to process such reconnect requests. In this situation setting the timeout from the client will prevent the situation to occur. Also SSH-users connecting to SSH servers/daemons that are slow to establish connection and where MySQL has a low timeout setting can use this option with advantage.

New in SQLyog Community Edition 8.13 Beta 1 (Jun 20, 2009)

  • Features:
  • SQLyog can be started with a ‘-dir’ switch like “SQLyogENT -dir somefolder”. This -dir switch specifies where SQLyog will look for the sqlyog.ini file and where all writeable files will be saved. This was mainly implemented for users that want to have all SQLyog-related files on a removeable drive or some kind of encrypted storage. Note that if you use the setting in ‘preferences’ to store TAGS file some specific place the ‘preferences’ setting will still have effect, also if the -dir switch is used.
  • Improved/rearranged the GRIDS in Data Sync and Import External Data wizards .
  • SJA mail functionality now supports SSL/TLS encryption.
  • ALTER VIEW will now format the SELECT-part of the VIEW definition.
  • Now all batch jobs will not generate BULK INSERTS larger than 16MB (like already implemented in Import External Data in 8.11).
  • In CREATE/ALTER TABLE the charset and collation columns can now be hidden for better overview (most users never use it).
  • Bug Fixes:
  • Edit menu showed F5 for both Refresh and Execute Query.
  • Autocapitalisation settings had effect where they should not. It has now been disabled in MESSAGES tab and in the error dialogue.
  • Non-column results (like functions, expressions etc.) were affected by column-width persistence feature what they should not (it had weird effects sometimes).
  • Various places a horizontal scrollbar displayed where it was not requiered.
  • Fixed wrong behaviour with GRID scrollbar after resize.
  • ALTER TABLE dialogue executed SHOW TABLE STATUS with no LIKE-clause. That could be slow with a large number of big InnoDB tables in a database.
  • PROFILER tab sometimes did not show after executing multiple queries.
  • After doing FILTER in DATA tab, LIMIT would be reset to previous value.
  • A ‘duplicate key’ error would occur with batch jobs (including Data Sync) if an autoincrement column had a ‘0′ value. We now set ‘NO_AUTO_VALUE_ON_ZERO’ sql_mode for batch jobs.
  • On Wine F8 keyboard shortcut was only functional after executing a query.
  • When copy database/table from a MySQL server 5.1 or higher to a 3.x or 4.0 server timestamps with ON UPDATE-clause caused a syntax error as ON UPDATE is not valid on such target. There was no issue when source was 5.0 as we transform the CREATE statement. But the condition had a bug so it did not work with 5.1+ .
  • It was not possible to enter an empty string in the GUI for ENUM/SET management.
  • When queries were inserted from ‘edit .. paste SQL statements’ menu the tokenizer editor component could fail to identify exactly where a statement started and stopped. Reason was that the tokenizer expects Windows linebreaks (
  • ) but templates contained Unix linebreaks (

New in SQLyog Community Edition 8.12 (Jun 9, 2009)

  • Bug Fixes:
  • Backups did not `backquote` identifiers inside the columns-list of an INSERT statement (ie. “INSERT .. (col1, col2) VALUES ..” instead of “INSERT .. (`col1`, `col2`) VALUES..”). If specific (but not all) keywords were used for naming a column, backups would not restore. This bug was introduced in 8.1.
  • A sync script generated with Data Sync had INSERT statements duplicated. Also this bug was introduced in 8.1.
  • Fixed a painting issue when switching between DATA tab and RESULT tab.

New in SQLyog Community Edition 8.11 (Jun 8, 2009)

  • Bug Fixes:
  • A memory corruption could occur when saving a file using ’save as’ (’save’ was not affected) from the editor. Various issues like painting issues and even a crash could then occur.
  • Scrolling with mouse scroll-button was not functional in the new GUI for SET/ENUM management.
  • ‘duplicate table’ did not duplicate all ‘table options’ defined for a table - like MAX_ROWS etc. (Also note that Foreign Key CONSTRAINTS are not duplicated either, but that is intentional and not a bug).
  • Bulk INSERTS generated by Import External Data Tool will now be restricted to 16 MB in size if max_allowed_packet in server configuration is larger than 16 MB. On specific systems/configurations memory issues were reported .

New in SQLyog Community Edition 8.1 (Jun 3, 2009)

  • One of most loved feature of SQLyog is the snappy and responsive user interface. Many of our users and customers prefer SQLyog over other tools because of this particular reason.
  • One reason for the zippy interface could be that SQLyog is entirely developed in C/C++, which tends to be faster than other languages when it comes to raw speed. I don’t want to start a flame war here, but our customers seem to like this fact. Using C/C++ allows us to use the native MySQL C client libraries that gives the best performance as compared to other ways of communicating with MySQL. Using C/C++ also ensures that there are no external dependencies on any bulky frameworks and the download file is relatively small.
  • Although using a language that complies directly to machine instructions helps a lot, but true speed comes from better algorithms. A similar analogy in the MySQL context would be that you might get some benefits from tuning your mysql.cnf/mysql.ini file, but real benefits come only when you find problematic queries in your application and rewrite them and/or create better indexes.
  • SQLyog uses a set of smart algorithms for its data synchronization tools. These algorithms ensure that we only transfer checksums using multiple threads and do full row transfer only when required. We have an old blog post with some benchmarking results here.
  • Although our data sync speeds are quite impressive, we were not happy with the results in certain scenarios. This led us to improve the data sync speeds even further with 8.1. We will publish some new benchmarking results soon in our blog.
  • With 8.1, we have been able to introduce massive speed improvements in the following areas:
  • Data synchronization
  • Auto complete
  • Export as SQL (including Scheduled Backups), CSV and XML
  • Wait, we are not finished yet with the improvements in 8.1. This release introduces the following major features:
  • Completely revamped Objects tab. The tab has been renamed to “Info”. The contents are now available in nicely formatted HTML in addition to the old text format
  • Direct import of Access, Excel and CSV files. Now you don’t need to create ODBC DSN to import these file types. Just point to the files and SQLyog does the rest
  • Last but not the least, we continue to improve the usability with every release of SQLyog. With 8.1 we have made the following GUI changes:
  • Added an option to ‘preview SQL’ in CREATE/ALTER TABLE
  • Column width in all GRIDs (not only DATA and RESULT tabs) are now persistent
  • New GUI for defining ENUM and SET columns in Create/Alter GUI
  • Some reorganisations of menus, improved captions and explanations in dialogues and wizards etc
  • Needless to say, this release contains many bug fixes, UI improvements and minor features.
  • We are very excited about this release, and hope that you will like it. We would love to hear from you.

New in SQLyog Community Edition 8.1 RC3 (May 29, 2009)

  • Features:
  • Improved speed of ‘backup’ (including ’scheduled backup’) similar to the improvements in RC2 for ‘export’.
  • Bug Fixes:
  • If a file named ’sja’ or ’sja.exe’ existed in SQLyog ‘AppData’ folder, SJA failed to connect with SSH tunnel. A user reported that such ’shadow copy’ was created periodically. Issue is not fully understood (except that Windows looked for PLINK too in ‘AppData’) but the fix works!
  • Fixed a scrolling issue in Data Sync GRID.

New in SQLyog Community Edition 8.1 RC2 (May 26, 2009)

  • Features:
  • INFO tab/HTML option had added more information.
  • The SELECT-part of a CREATE VIEW statement in INFO tab will now be formatted. Also the ‘SQL-preview’ in CREATE/ALTER TABLE dialogue will now be formatted.
  • Drastically improved the speed of exports (typically 3-4 times faster). This refer to exports as CSV, XML ,HTML, Excel XML and SQL. But note: no change with ‘export as SQL-dump’ and ’scheduled backup’.
  • Added ’scheduled backup’ option to Object Browser context menu.
  • Some reorganisations of menus, improved captions and explanations in dialogues and wizards etc.
  • Bug Fixes:
  • The dialogue for defining SET/ENUM types introduced in beta1 did not prevent duplicate entries.
  • Removed redundant SPACES in CREATE statements. These SPACES could cause formatting to garble when copying (to a web form for instance).
  • Lots of fixes for small (mostly GUI-related) issues reported internally.

New in SQLyog Community Edition 8.1 RC (May 22, 2009)

  • Features:
  • The caption ‘Migration Toolkit’ was changed to ‘Import External Data’ in menus etc.
  • The session.xml file (used by SJA internally) is now not exposed to users in Wizards. The file is created in user’s ‘AppData’ folder when job is invoked from a Wizard. If invoked from command-line files will be created in the folder where the SJA executable is, if not specified differently from command line. The reason for this change is that the two XML files (jobfile and sessionfile) have frequently been confused by users.
  • The changes in beta1 were ‘polished’.

New in SQLyog Community Edition 8.1 Beta 1 (May 15, 2009)

  • Features:
  • Added an option to import text/.csv, .xls (Excel) and .mdb (Access) files without without using a preconfigured DSN setting (user only need to specify the file and ODBC driver details are passed transparently for user). When using this option also detailed column mapping is possible. Also Office2007 formats (.xlsx, .accdb) are supported like this provided that this Microsoft driver set is installed (it is not per default on any Windows version).
  • Added an option to ‘preview SQL’ in CREATE/ALTER TABLE.
  • OBJECTS tab was renamed to INFO tab. There is now a choice between the (old) text-based display and a new tabular/HTML-based view.
  • New GUI for defining ENUM and SET columns in Create/Alter GUI.
  • Autocomplete had a complete ‘overhaul’ resulting in better performance.
  • Column width in all GRIDs (not only DATA and RESULT tabs) are now persistent.
  • Bug Fixes:
  • Query Profiler would sometimes fail to display the total time in SHOW PROFILE.
  • Fixed a painting issue in Schema Designer.
  • Fixed a program crash in copy database/table.
  • On Win2K and Wine icons will now be 8 bit color depth, as those environments do not support 32 bit color depth icons properly.
  • Autocomplete would sometimes erroneously insert a linebreak.
  • Query Builder could generate SQL with an ambiguous column (not prefixing columnname with tablename for a PK-column) if the same column name existed in joined tables. This bug was introduced in 8.03.
  • When connected to MySQL before 4.1 a string containing special (non-ASCII) characters could be identified as a binary string. Also this bug was introduced in 8.03.
  • Autocomplete was not functional within the argument-list of a function.
  • ‘empty database’ (from the database menu/context menu) caused Autocomplete to become non-functional for the session.
  • Scheduled backup did not handle the “&” character in file and folder names.

New in SQLyog Community Edition 8.05 (Apr 8, 2009)

  • Features:
  • User Management icon was re-introduced in the Icon Bar.
  • In DATA and RESULT tab you can now open the BLOB VIEWER for BLOB and TEXT types with any keyboard keystroke (like SPACEBAR). The ‘NOT NULL’ checkbox will then automatically uncheck (if checked) and BLOB VIEWER window is ready for input from the keyboard without any mouse action.
  • Bug Fixes:
  • SQLyog could crash when retrieving binary data over a HTTP-connection.
  • Fixed a crash when updating from the RESULT tab (details: a pointer used internally could contain an invalid value).
  • When multiple reconnects took place in ‘copy database/table’ with short intervals various issues could occur - including a program crash.
  • When Schema Sync CREATED a table having a string column with default ” (empty string) the default was not created for that column (it was no problem if the table on existed in advance and was ALTERED)..
  • On MySQL 4.1 and 5.0 SHOW FULL FIELDS does not expose an ON UPDATE CURRENT_TIMESTAMP clause for a TIMESTAMP column . We will now get this information from SHOW CREATE TABLE . The most serious problem before this was that when syncing from 4.1/5.0 to 5.1/6.0 an ON UPDATE CURRENT_TIMESTAMP clause could erroneously be dropped on target.
  • Also this release contains a large number of GUI-releated fixes including fixes for painting issues and Object Browser issues related fixes. Also the Object Browser fixes in 8.04 introduced new issues that were now also fixed.

New in SQLyog Community Edition 8.05 RC (Apr 4, 2009)

  • When Schema Sync CREATED a table having a string column with default ” (empty string) the default was not created for that column (it was no problem if the table on existed in advance and was ALTERED) .
  • On MySQL 4.1 and 5.0 SHOW FULL FIELDS does not expose an ON UPDATE CURRENT_TIMESTAMP clause for a TIMESTAMP column . We will now get this information from SHOW CREATE TABLE . The most serious problem before this was that when syncing from 4.1/5.0 to 5.1/6.0 an ON UPDATE CURRENT_TIMESTAMP clause could erroneously be dropped on target.

New in SQLyog Community Edition 8.05 Beta 2 (Apr 2, 2009)

  • Bug Fixes:
  • Fixed a critical bug in Beta 1: BLOB and TEXT types would not update from the RESULT tab. The ‘red alert’ that data were changed but not saved would disappear, but no SQL was sent to the server.
  • Miscellaneous:
  • Beta 1 release notes reading:
  • The SET NULL checkbox in BLOB VIEWER will now uncheck automatically when user types into the BLOB VIEWER window.
  • .. were incorrect. Correct documentation for this new implementation is
  • In DATA and RESULT tab you can now open the BLOB VIEWER for BLOB and TEXT types with any keyboard keystroke (like SPACEBAR). The ‘NOT NULL’ checkbox will then automatically uncheck (if checked) and BLOB VIEWER window is ready for input from the keyboard without any mouse action.

New in SQLyog Community Edition 8.05 Beta 1 (Apr 1, 2009)

  • Features:
  • User Management icon was re-introduced in the Icon Bar.
  • The SET NULL checkbox in BLOB VIEWER will now uncheck automatically when user types into the BLOB VIEWER window.
  • Bug Fixes:
  • SQLyog could crash when retrieving binary data over a HTTP-connection.
  • Fixed a crash when updating from the RESULT tab (details: a pointer used internally could contain an invalid value).
  • When multiple reconnects took place in ‘copy database/table’ with short intervals various issues could occur - including a program crash.
  • Also this release contains a large number of GUI-releated fixes including fixes for painting issues and Object Browser issues related fixes. Also the Object Browser fixes in 8.04 introduced new issues that were now also fixed.

New in SQLyog Community Edition 8.04 (Mar 24, 2009)

  • Features:
  • Crash dumps with no information (zero-size) will now be deleted automatically.
  • When saving/copying from the editor the LETTERCASE modfications for keywords and functions will now be preserved.
  • Selecting a ‘child’ object for a table (columns and indexes) will now refresh the DATA tab if DATA tab is open. Before only selecting the table object itself did. Also the table information is now available in OBJECTS tab when a column or index is selected.
  • Now also a ‘key’ icon is used for identifying the Primary Key in an Object Browser ‘Indexes’ folder,
  • When a GRID cell is only partly visible, doubleclicking it will move the grid position so that cell/row will become visible (before it worked like that with singleclick - we changed to doubleclick as this is a de facto standard in such grids - in Excel for instance).
  • The copy database/table dialogue will now expose detailed information about objects copied.
  • In ‘empty database’ added a ‘SELECT ALL’ option in order to avoid multiple confirmation popups.
  • Bug Fixes:
  • An index defined on more than one column displayed as many time in the Object Browser as the number of columns used for defining the index.
  • Fixed scrolling issues with the GRIDs.
  • The GRID of CREATE/ALTER TABLE dialogue required double-click in a cell before pasting into that cell was possible.
  • Query Builder ‘copy query to same query tab’ was broken.
  • Query formatter would insert Unix linebreaks (
  • ) instead of Windows linebreaks (
  • ) between multiple queries what in turn could result in that the tokenizer/editor would fail to recognize exactly where a statement started and ended.
  • In the Schema Sync dialogue the ‘compare’ button could grey out. This bug was introduced with the ‘refresh’ option added in 8.03.
  • The ‘include column names’ option in CSV-export dialogue (including ’save to clipboard’) was not persistent.
  • Fixed some flickering and repainting issues in Schema Designer in particular as well as other similar small issues elsewhere in the program.
  • A floating point value displayed in the form “.1234? (no ZERO before the decimal sign) would be exported as integer “1234? with “export as Excel XML”. Also NULL values for numerical types could result in a XML file that Excel would not open.
  • Adding/dropping an index would collapse the ‘columns’ folder for the table in Object Browser and vice versa.
  • F6 keyboard shortcut was disabled if focus was on a ‘columns’ folder in Object Browser.
  • When using “copy database” and an error occurred while copying a ’stored program’ the copy proces would not abort on error. Instead next object was copied or attempted copied. This has been changed so that behaviour with ’stored programs’ is the same as with tables.
  • When clicking the database dropdown in the connection manager of SJA wizards the mouse pointer did not change to an ‘wait state’ pointer while list of databases was fetched from the server, what could give user an impression of SQLyog ‘hanging’ .
  • Progress bar improvement with “Export as SQL dump” and “Restore from SQL dump”. Also progress information with files larger than 4 GB displayed wrong due to 32 bit integer overflow. Now a 64 bit integer is used.
  • Lots of small GUI fixes reported internally and by users.
  • Functionality changed:
  • We will now not UPDATE a row of data from DATA or RESULT tab if any of the columns displayed for the actual row contains data identified as binary data by containing a NULL byte (’' in C-notation) no matter whether this occurs for binary, varbinary, char or varchar types. Instead an error message will print (reason for this: the UPDATE operation would store what was displayed - not the underlying binary data causing the display).
  • The arrow icons displaying in column headers of the DATA grid indicating sorting state have been replaced/reverted to conform with de-facto standards.

New in SQLyog Community Edition 8.04 Beta 2 (Mar 17, 2009)

  • Features:
  • When a GRID cell is only partly visible, doubleclicking it will move the grid position so that cell/row will become visible (before it worked like that with singleclick - we changed to doubleclick as this is a de facto standard in such grids - in Excel for instance).
  • The copy database/table dialogue will now display detailed information about number of objects copied.
  • Bug Fixes:
  • Fixed some flickering issues and other small issues in Schema Designer.
  • When clicking the database dropdown in the connection manager of SJA wizards the mouse pointer did not change to an ‘wait state’ pointer while list of databases was fetched from the server, what could give user an impression of SQLyog ‘hanging’ .
  • Progress bar improvement with “Export as SQL dump” (similar to “Restore from SQL dump” as of beta 1).
  • The prevention to UPDATE binary data introduced in beta 1 was not functional for TEXT types. Also a correction/clarification: for BLOB types there is currently no such prevention (in order to support images).

New in SQLyog Community Edition 8.04 Beta 1 (Mar 13, 2009)

  • Features:
  • Crash dumps with no information (zero-size) will now be deleted automatically.
  • When saving/copying from the editor the LETTERCASE modfications for keywords and functions will now be preserved.
  • Selecting a ‘child’ object for a table (columns and indexes) will now refresh the DATA tab if DATA tab is open. Before only selecting the table object itself did. Also the table information is now available in OBJECTS tab when a column or index is selected.
  • Now also a ‘key’ icon is used for identifying the Primary Key in an Object Browser ‘Indexes’ folder.
  • Bug Fixes:
  • An index defined on more than one column dislayed as many time in the Object Browser as the number of columns used for defining the index.
  • Fixed scrolling issues with the GRIDs.
  • The GRID of CREATE/ALTER TABLE dialogue required double-click in a cell before pasting into that cell was possible.
  • Query Builder ‘copy query to same query tab’ was broken.
  • Query formatter would insert Unix linebreaks (
  • ) instead of windows linebreaks (
  • ) between multiple queries what in turn could result in that the tokenizer/editor would would fail to recognize exactly where a statement started and ended.
  • Fixes with “Restore From SQL dump” 1) progress bar improvement 2) progress information with files larger than 4 GB displayed wrong due to 32 bit integer overflow. Now a 64 bit integer is used.
  • In the Schema Sync dialogue the ‘compare’ button could grey out. This bug was introduced with the ‘refresh’ option added in 8.03.
  • The ‘include column names’ option in CSV-export dialogue (including ’save to clipboard’) was not persistent.
  • Lots (around 20) of small fixes reported internally and by users.
  • Functionality changed:
  • We will now not UPDATE a row of data from DATA or RESULT tab if any of the columns displayed for the actual row contains data identified as binary data by containing a NULL byte (’' in C-notation) no matter whether this occurs for binary types (binary, varbinary, BLOB) or string types (char, varchar, TEXT). Instead an error message will print (reason for this: the UPDATE operation would store what was displayed - not the underlying binary data causing the display).
  • The arrow icons displaying in column headers of the DATA grid indicating sorting state have been replaced

New in SQLyog Community Edition 8.03 (Mar 6, 2009)

  • Features:
  • New major feature: column width persistence in GRIDs. Once you have defined a column width for a combination of database/table/column the defined column width will always be used. Note that connection details are not used for identifying columns with this new functionality so with replicated and identically named synchronized databases it is sufficient to define in one place. Alias’ed columns in results are handled by the column name and not the alias. Non-column results (like constants, results of expressions/functions, returns of SHOW etc.) are not supported currently. The feature can be turned on/off. Note that if both this new option and the old ”Truncate column headers … ” is checked in program ‘preferences’ the “Truncate ..” option will be ‘overridden’ by the new column width persistence feature.
  • Resizing columns in GRID was made easier. A ‘zone’ around the column splitter and not only the splitter line itself will now accept the mouse event.
  • ‘Find’ dialogue will now remember last used values.
  • Added an option to open a file in a new tab (Editor tab and Schema Designer tab).
  • Added an option to use ‘hard SPACES’ for tabulation in the editor (with this checked the code will display identically when copied to other programs).
  • In editor you can now start typing a query in any position and will position cursor in same position of the next line.
  • Added ‘view data’ option to the context menu of a VIEW.
  • In Query Builder PK-columns are now marked with a (beginning) ‘*’ .
  • In Object Browser introduced a new ‘key’ icon for PK-columns.
  • ‘Find’ was implemented in BLOB viewer. Currently there is only the Ctrl+F shortcut to do this and no other GUI option (no button or whatever).
  • In Schema Sync added a ‘refresh’ option in the dropdowns for and databases.
  • The program dialogues for SHOW variables/processlist/status, SHOW warnings with CSV-import and Table advanced properties are now resizable.
  • Fixed a bug with detection of encoded strings stored in BLOBs (This bug was introduced in 8.0 - and it is still recommended to use TEXTs for encoded strings).
  • Doubleclicking in the GRID could cause the GRID position to move.
  • Bug Fixes:
  • Fixed an issue where SQLyog failed to SET NAMES when reconnecting.
  • Exporting floating point data as Excel XML could truncate data.
  • Quite a lot of fixes for (mostly cosmetical) GUI issues.
  • Fixed some ‘flickering’ issues.
  • Double clicking in the GRID could cause the GRID position to move. .
  • Fixed a bug with detection of encoded strings stored in BLOBs (This was introduced in 8.0 - and it is still recommended to use TEXT types for encoded strings).
  • Miscellaneous:
  • For 16×16 icons we now use the icons from before 8.0. The new icons had too many details for this resolution. Also now users that prefer the old icons can have them!
  • A restriction on the file size to be loaded into the editor introduced in 7.12 was enlarged from 2 MB to 20 MB. A warning will now print if size is exceeded (but also note that there is no such restriction when importing external files (from tools .. restore ..)).

New in SQLyog Community Edition 8.03 Beta 2 (Mar 4, 2009)

  • Bug Fixes.
  • Further improvements in the fixes for flickering issues. Also the fixes in beta1 had introduced some painting issues that were now solved.
  • Doubleclicking in the grid could cause the GRID position to move.
  • Fixed a bug with detection of encoded strings stored in BLOBs (This bug was introduced in 8.0 - and it is still recommended to use TEXTs for encoded strings).
  • Miscellaneous.
  • A restriction on the file size to be loaded into the editor introduced in 7.12 was enlarged from 2 MB to 20 MB. A warning will now print if size is exceeded (but also note that there is no such restriction when importing external files (from tools .. restore ..))..

New in SQLyog Community Edition 8.03 Beta (Feb 27, 2009)

  • Features:
  • New major feature: column width persistence in GRIDs. Once you have defined a column width for a combination of database/table/column the defined column width will always be used. Note that connection details are not used for identifying columns with this new functionality so with replicated and identically named synchronized databases it is sufficient to define in one place. Alias’ed columns in results are handled by the column name and not the alias. Non-column results (like constants, results of expressions/functions, returns of SHOW etc.) are not supported currently. The feature can be turned on/off. Note that if both this new option and the old ”Truncate column headers … ” is checked in program ‘preferences’ the “Truncate ..” option will be ‘overridden’ by the new column width persistence feature.
  • ‘Find’ dialogue will now remember last used values.
  • Added an option to open a file in a new tab (Editor tab and Schema Designer tab).
  • Added an option to use ‘hard SPACES’ for tabulation in the editor (with this checked the code will display identically when copied to other programs).
  • In editor you can now start typing a query in any position and will position cursor in same position of the next line.
  • Added ‘view data’ option to the context menu of a VIEW.
  • In Query Builder PK-columns are now marked with a (beginning) ‘*’ .
  • In Object Browser introduced a new ‘key’ icon for PK-columns.
  • ‘Find’ was implemented in BLOB viewer. Currently there is only the Ctrl+F shortcut to do this and no other GUI option (no button or whatever).
  • In Schema Sync added a ‘refresh’ option in the dropdowns for and databases.
  • The program dialogues for SHOW values/processlist/status, SHOW warnings with CSV-import and Table advanced properties are now resizable.
  • Bug Fixes:
  • Fixed an issue where SQLyog failed to SET NAMES when reconnecting.
  • Exporting floating point data as Excel XML could truncate data.
  • Quite a lot of fixes for (mostly cosmetical) GUI issues.
  • Fixed some ‘flickering’ issues.
  • Miscellaneous:
  • For 16×16 icons we now use the icons from before 8.0. The new icons had too many details for this resolution. Also now users that prefer the old icons can have them!

New in SQLyog Community Edition 8.02 (Feb 24, 2009)

  • Features:
  • Both SQLyog and SJA will now detect if Base64 encoding is required for HTTP-tunnel.
  • Bug Fixes:
  • Importing external scripts with a large number of DDL-statements was slow with Auto Complete turned on (due to redundant updations of the Auto Complete database).
  • Deseleting a single object (like a single table) in the export dialogue also deselected all objects in other categories (like all non-table objects).
  • Funtionality changed:
  • CHUNK setting (for exports) now also has effect for non-HTTP-tunneled connections. Using this option is required if it takes more time to retrieve data from a table than server ‘net_write_timeout’ setting.
  • SQLyog will now not reconnect if connection is lost during imports. Instead an error message will prompt (the reason for this is that session variables defined on top of the script would be reset to server defaults with reconnection. As a result (and most important) special characters could garble and other errors could occur as well).
  • When trying to INSERT or UPDATE spatial data types from the DATA/RESULT tab SQLyog will now throw an error. Spatial data must be handled from the editor (but a result set from a table with spatial columns can be updated from RESULT tab if there are no spatial columns in the result).

New in SQLyog Community Edition 8.02 RC (Feb 20, 2009)

  • Features:
  • Both SQLyog and SJA will now detect if Base64 encoding is required for HTTP-tunnel.
  • Funtionality changed:
  • CHUNK setting (for exports) now also has effect for non-HTTP-tunneled connections. Using this option is required if it takes more time to retrieve data from a table than server ‘net_write_timeout’ setting.
  • SQLyog will now not reconnect if connection is lost during imports. Instead an error message will prompt (the reason for this is that session variables defined on top of the script would be reset to server defaults with reconnection. As a result (and most important) special characters could garble and other errors could occur as well)..
  • When trying to INSERT or UPDATE spatial data types from the DATA/RESULT tab SQLyog will now throw an error. Spatial data must be handled from the editor (but a result set from a table with spatial columns can be updated from RESULT tab if there are no spatial columns in the result).

New in SQLyog Community Edition 7.5 Beta 2 (Jan 17, 2009)

  • Features:
  • Added option for user to choose between different icon sizes in the icon toolbar.
  • Added option for user to select/deselect the ‘info-line’ displaying at the bottom of DATA, RESULT and PROFILER tabs.
  • Bug Fixes:
  • Fixed a crash with PROFILING in beta1. Crash could occur even when executing rather simple queries.
  • Fixed a crash with ALTER TABLE in beta1 when the contents of a cell in the ALTER TABLE GRID was deleted.
  • Formatter failed with strings specified with ”_charset” specifier and/or hexadecimal (’x') or binary (’b') modifier (like “_utf8 x’AAA00F99′” or “_latin1 b’01010111”’). Also COLLATE clause for a literal string was not supported by Formatter.
  • Miscellaneous:
  • The ENTERPRISE uninstaller will now remove registration info from the system. This is a request by users who misspelled the registration name or by mistake registered to themselves as a person and not to their company/organisation. Note that as a consequence you now should have your registration details available if you uninstall and reinstall!

New in SQLyog Community Edition 7.5 Beta 1 (Jan 12, 2009)

  • Features:
  • New major feature: Query Formatter. Any SELECT, UPDATE, INSERT or DELETE statement can be formatted with a single click. Various formatting options/styles are available in ‘preferences’.
  • New major feature: Query Profiler. With this feature enabled every SELECT statement will trigger execution of EXPLAIN (EXTENDED) and SHOW PROFLE (if supported by server) for the query and will detect changed SESSION STATUS VARIABLES (with some additional explanation of the meaning of those) due to execution of the query. The feature is highly configurable. The information will display in an ‘Analyzer’ tab opening in the DATA/RESULT area. With this new feature there is no longer an excuse not to profile queries continously in the application development process - simply because whether you do it or not the effort will be practically the same! Refer to documentation for full details and for limitations of current implementation. This beta contains first step (only) planned for this feature.
  • New improved icon theme with larger icons (in progress). The old icon theme originated back from a time where monitor resolutions were lower than what is mostly the case today.
  • Added an option to force LETTERCASE (Uppercase/Lowercase) for display of keywords and functions in the editor. Note that only the display in editor is affected. When copying or saving, the LETTERCASE will be copied be as it was entered.
  • A VIEW can now be generated directly from the Query Builder.
  • Status bar will now display information like “showing x rows of total y”.
  • Some minor GUI usability improvements and fixes in Data Grid and in Object Browser.
  • Bug Fixes:
  • If BLOB-viewer was closed by clicking the upper-left corner ‘x’ symbol, changes were lost without warning.
  • A SQL script with a user´defined DELIMITER using semicolon failed in editor as well as when importing an external script. Most important “DELIMITER ;;” (double semicolon) did not work - but other DELIMITER strings using semicolon (like triple semicolon etc.) did not either (however note that with HTTP tunnelling and when importing external files this is not yet completed ).

New in SQLyog Community Edition 7.15 (Jan 6, 2009)

  • Features:
  • Added an option to use Base64 encoding for communicating XML data stream with the HTTP tunneller. Using this option can be required to work around this XML-related bug in PHP.
  • Improved editor performance with large scripts if Wordwrap was enabled.
  • Bug fixes:
  • On Windows Vista Business edition, SQLyog could crash while closing down. No other Windows OS (and also not any other Vista edition) was affected.
  • Also a ‘hang’ could occur when closing down. It could happen with all systems, but Windows Vista was mostly affected.
  • Schema Sync failed with identically named Foreign Key CONSTRAINTs on identically named colums of basically same type (that could still differ in LENGTH, SIGNED/UNSIGNED specification etc.)
  • Miscellaneous:
  • When a PK is built on a string column using a case insensitive collation, SJA could try to insert a row where the PK was identical to an existing one as compared “COLLATION-wise” (ie. when only LETTERCASE differed). That would result in ‘duplicate key’ error and the sync job would abort. We have now reverted back to case insensitive camparison with string-based PK’s as before 7.0, but (to avoid data loss/overwriting) we will abort sync of tables when a string-based PK uses a binary or case sensitive collation.

New in SQLyog Community Edition 7.14 (Dec 4, 2008)

  • Bug fixes:
  • Schema Sync did not distinguish “default NULL” and “default ” (empty string)” for string types.
  • When multiple connections were open in one program instance and one connection was in wait-state (for instance due to a TABLE LOCK), the whole program could become non-responding.
  • If a server thread running a query sent by SQLyog was killed, SQLyog would not always detect it. The connection window associated with that thread would then stay in wait-state forever. Due to the ‘multiple connections issue’ as described just above also the whole program could be affected.
  • With MySQL servers 4.0 and before and when connecting with HTTP-tunnel, SQLyog could send an invalid SET SQL_MODE statement when copying large amounts of data. The copy operation would then abort. This bug was introduced in 7.12.
  • Reconnecting while populating Object Browser could crash SQLyog.
  • Fixed 2 rare crashes in Schema Sync and DATA tab (reported internally).
  • Fixed a bug with ‘replace’ in editor. ‘replace’ took effect *after* cursor position not *from* cursor position, so if cursor was positioned inside the string to be replaced that particular instance would not replace.
  • Refreshing the GRID moved the cursor to ‘home’ position.
  • Fixed a bug in Autocomplete transaction handling (introduced in 7.13) that could cause a crash at statup.
  • Migration Tool could fail to find rows when migrating from SQL server 2008.

New in SQLyog Community Edition 7.14 Beta 1 (Nov 27, 2008)

  • Schema Sync did not distinguish “default NULL” and “default ” (empty string)” for string types.
  • When multiple connections were open in one program instance and one connection was in wait-state (for instance due to a TABLE LOCK), the whole program could become non-responding.
  • If a server thread running a query sent by SQLyog was killed, SQLyog would not always detect it. The connection window associated with that thread would then stay in wait-state forever. Due to the ‘multiple connections issue’ as described just above also the whole program could be affected.
  • With MySQL servers 4.0 and before and when connecting with HTTP-tunnel, SQLyog could send an invalid SET SQL_MODE statement when copying large amounts of data. The copy operation would then abort. This bug was introduced in 7.12.
  • Reconnecting while populating Object Browser could crash SQLyog.
  • Fixed 2 rare crashes in Schema Sync and DATA tab (reported internally).
  • Fixed a bug with ‘replace’ in editor. ‘replace’ took effect *after* cursor position not *from* cursor position, so if cursor was positioned inside the string to be replaced that particular instance would not replace.
  • Refreshing the GRID moved the cursor to ‘home’ position.
  • Fixed a bug in Autocomplete transaction handling (introduced in 7.13) that could cause a crash at statup.