Also read about plans for future versions of SQLyog

SQLyog 7.01 (July 2008)

Bug Fixes

• When SQLyog tried to reconnect while exporting a crash could occur. This bug was introduced in 7.0 with the speed optimization of the export dialogue.

SQLyog 7.0 (July 2008)

Features

• New GRID design (’zebra’ Office 2007 style) for easier navigation.
• Multiple selection in GRIDs with SHIFT+CLICK.
• Improved Data Synchronization. Now typically 2-8 times faster than before depending on data. Option to generate a SQL sync script was added.
• Drastically improved the speed of exports.
• New more user friendly design for the Schema Synchronisation (renamed from Structure Synchonisation). Various filter (’hide and ignore’) options were added. Also a long-running Schema Sync compare task can now be stopped.
• Added automatic and manual update check.

Bug Fixes

• A backup script backing up all databases could fail to restore VIEWs referencing another database than the one where the VIEW was.
• Around 50 other small (mostly GUI-related) fixes for issues reported by users.

SQLyog 6.56 (May 2008)

Bug Fixes

• Structure Sync could miss the concluding quote around column comments. This bug was introduced in 6.5.
• Migration from SQL Server could fail with empty tables.
• Migration (UPDATE and DELETE) triggers could fail with specific schemas on source (afffected were small tables with short column types only - like integers and very short string types). This bug was introduced early in 6.x with the full Unicode support added here.
• Migration could generate non-matching columns-count with specific schemas. This was also introduced early in 6.x.
• Message about “Successful rows” could display twice in Migration (sja.log). Note: This was a cosmetical issue with the message only. Rows were only migrated once!

SQLyog 6.55 (May 2008)

Bug Fixes

• With specific export settings, CSV-export could add an erroneous NULL byte (hexadecimal 00) before the field seperator (if no escape character was specifed and if string data contained the chosen seperator character).
• With specific content of an editor tab, SQLyog could enter an infinite loop and become irresponsible. It was a bug in the code for column alias'es with Autocomplete introduced in 6.52.
• When SQLyog was closed from a secondary monitor and started again when secondary monitor was not attached, SQLyog program window would not open on the primary monitor.
• With specific multimonitor configuration context menu of the Processlist dialogue would open on primary monitor also when program was running on secondary monitor.
• After stopping a running query, SQLyog could fail to initialize sql_mode for the new connection created.

SQLyog 6.54 (April 2008)

Bug Fixes

• When executing Structure Sync between a 5.1.x server and an earlier version, Structure Sync could try to access a non-existing Information_Schema.Events table, what returned an error (it depended on the exact 5.1 version).

SQLyog 6.53 (April 2008)

Bug Fixes

• When defining parameters for export, database selection had no effect if the database was selected after the output file was specified. This bug was introduced in 6.5.
• SQL-dumps created with SQLyog 'export' and 'scheduled backup' did not specify default charset and collation in CREATE DATABASE statement when dumping from MySQL versions where it applies (MySQL >= 4.1).
• The size of the SQLyog program window would grow a little everytime it was opened. This is due to a change introduced in 6.5. This has been reverted.
• The various fixes for BIGINT PK's in Data Sync in the 6.1x tree had slowed down data sync with BIGINT PK's.
• Alias support in Auto-Complete could fail if there were comments close to the actual statement. This bug was introduced in 6.52 (with the support for column alias'es introduced here).
• In RESULTS tab in text-mode the string "(NULL)" could be truncated to "(NUL"

SQLyog 6.52 (April 2008)

Features

• Data Sync now has SMTP (mail) functionalities similar to other SJA modules
• Autocomplete now supports column alias'es.
• Zooming in Schema Designer can be done with 'Ctrl +' and 'Ctrl -'.
• Added an option to specify (in preferences .. powertools) storage position for TAGS files (used by Autocomplete). On networks where 'roaming profiles' are stored on a domain server specifying a local folder will reduce network traffic and save storage on the server.

Bug Fixes

• ALTER TRIGGER template did not display DEFINER.
• Create/Alter table .. advanced properties generated the string '[default]' where it should be 'default' only.
• Fixed an issue with 'abort on error' in Scheduled Backup. The job was always aborted on error. Now if set to NO it will proceed to next statement.
• Notifications Service could crash if query was not SELECT. In particular HTTP tunnelled connections were affected by this.
• Migration from an Access database could leave a .ldb file behind (that should be deleted after the migration process was over).
• On Vista a graphical artifact could occur on right side of screen when program was maximized.
• Some other small GUI fixes.

SQLyog 6.51 (April 2008)

Bug Fixes

• The template for ALTER TRIGGER mismatched the trigger name and the database name.
• The OBJECTS tab displayed incomplete information for the server/connection. This only affected COMMUNITY edition.

SQLyog 6.5 (March 2008)

Features

• Export and copy dialogues were re-designed. Individual Stored Procedures, Views etc. can now be selected.
• Added a ZOOM option for a Schema Designer LAYOUT. The ZOOM setting is stored in the LAYOUT itself. Note: Zooming is possible using Ctrl+mouse scroll button (may not be functional on Laptop touchpads and other non-mouse pointing devices).
• A Schema Designer LAYOUT can now be saved as graphics (currently .bmp format is supported).
• A Schema Designer LAYOUT can now be printed. For saving graphics from Schema Designer to formats not supported consider printing to a 'virtual printer'. Such software exist with support for .pdf, .xps, .png and more. There is a preview option to see how the print will split into more pages (using the settings of current default printer).
• Transactions are now supported for copy operations (but of course the Storage Engine must support too!). This is configurable from 'preferences'. Data Sync and Migration will use transactions if ENGINE supports it.
• Copy operations can use BULK inserts (optionally). This can increase speed of those operation up to ~10 times. Migration and Data Sync will now also use BULK inserts if target is empty.
• Query Builder can now use a VIEW for generating queries.
• Full support for MySQL EVENTS (in GUI, exports, copy, structure sync) with MySQL >= 5.1.
• Added an option to export 'all databases' and 'all user data' with 'scheduled backup'. Note the difference: 1st option will export `mysql` database - 2nd will not. None of them will export Information_Schema (it cannot be restored as I_S is a readonly database). However you can select I_S individually for export .
• Support for alias in autocomplete. This is in continued development. Currently table alias's are supported (not column alias'es).
• Tables are now organized in a folder in the Object Browser.
• OBJECTS tab now populate with data for the connection/server, VIEWs and 'stored programs'.
• With SSH tunnel reconnection is now functional for the complete connection chain: SQLyog..PLINK..SSHD..MySQL.
• For HTTP-tunnel added an option to specify 'urlencode' HTTP header format on a per-connection basis (default is 'text/xml' header format). Using this option can be required if Apache 'mod_security' (as well as some largely undocumented filters and 'hacks') is enabled.
• Context help added. Every dialogue of the program has been associated with a page in the help file (CHM), that will open when pressing F1.
• MESSAGES tab will now report warnings for queries executed from the SQL editor.
• Lots of small requests and issues fixed.

Miscellaneous

• Note that the SJA jobfile format has needed to be changed/expanded due to some of the changes above. The GUI wizards will generate a version string like 'version="6.5"' in the tag . But old (version="4.2") format can still be executed. If there is no version string in the tag (as was the case up to 4.1), 'version="4.2"' will be assumed implicitly.
• Note that for copy operations reconnect will be disabled if you use transactions. This is required for data security. If a reconnect took place when still non-committed statements had been executed they would not be committed ever (because with a new connection the transaction log for the old connection is not available) and user would not be aware of this. For Data Sync and Migration transactions are always enabled if ENGINE supports it, because this does not result in any conflict as SJA does not reconnect automatically.

Bug Fixes

• Opening a .schemaxml file (to Schema Designer) failed if path contained unicode characters (save not affected and no other save/open operations of the program either).
• It could occur that a connection thread started for the purpose of export did not correctly use the same connection parameters as the 'parent thread'. That might result in a 'Error 0' (actually this includes two different fixes).

SQLyog 6.16 (February 2008)

Features

• Added an option to specify CHARSET parameter for CSV-import. Unicode (UTF8 and UCS2/UTF16) will be detected automatically. For files encoded with a non-unicode encoding, user must select the MySQL charset used for the import. Alternatively there is a option that will not use the CHARSET parameter at all (= old program behavior).
• SJA SMTP (mail) code will now use ESMTP if available and fall back on ('ordinary') SMTP if not (before only ESMTP was supported what failed with some specific routers).

Bug Fixes

• A crash could occur when backing up (using 'export' as well as 'scheduled backup') an object having a DEFINER different than the current user. This further depends on the MySQL version and whether user had SELECT privilege to the `mysql `database or not. Now a message will appear (on the screen or in the sja.log file) that this object was skipped due to lack of privileges when it is not possible to back up.
• When exporting to HTML, XML or CSV -formats from the RESULT tab one row could be missing if the RESULT tab dropdown was in edit-mode. EXCEL and SQL formats were not affected.
• When data were inserted or updated from RESULT tab, SQL and EXCEL export options would not export the new/changed rows unless after a reconnect.
• When connected to MySQL 3.x and 4.0 the ALTER TABLE GUI would generate invalid SQL if existing column(s) were edited and new column(s) added in one operation (a comma was missing).
• Assigning privileges (from 'manage permissions) for a specific user to a specific Stored Function and Stored Procedure was buggy (wrong string identifying the ROUTINE type was inserted). Also a problem with VIEW-related privileges was fixed.
• A jobfile for 'scheduled backup' created with versions before 6.1 contains a tag (with the values "yes" or "no") that indicates if the backup shall be utf8-encoded. When set to "no" it could occur (with versions 6.1 and higher) that SJA tried to use a non-existent charset for the backup and the job would abort.
• The HTTP-tunneler was updated to 'work around' an issue with 'foreach' loops on PHP 4.3.10. HTTP-tunneling to a server with that specific PHP version could cause a program crash.
• Data Sync would not identify that rows containing data like ('data',NULL) and (NULL,'data') are different, as NULL-values did not 'contribute' to the checksums calculated. No update would take place.
• If SSH tunnel was used for both connections in DATA SYNC the plink process for the target connection was not getting terminated properly.
• Display in the CREATE/ALTER TABLE grid would be truncated if an ENUM or SET type was defined with a value containing the ")" character.
• The fix in Data Sync for BIGINT Primary Keys containing very large numbers in 6.11 was not complete. Internal data could be truncated what again could result in wrong identification of rows to be inserted, updated or deleted.
• Certain queries (when performing GRID operations) were not 'piped through' the reconnection wrapper module. This could with low 'wait_timeout' server setting result in the 'server has gone away' error message if affected operations were executed with longer intervals between.
• Structure Sync failed to sync a specified index length.

SQLyog 6.15 (January 2008)

Bug Fixes

• ALTER TABLE would generate invalid SQL with column-level comments.
• When the content of an editor tab was changed using 'search and replace' the tab was not properly 'flagged' internally as changed. As a consequence the (*) indicator for this 'change-status' would not display and program would not prompt user if changes should be saved.
• Fixed a bug in validating the SP/VIEW/... name while creating. A symptom was that an empty name could be used.
• With a TINYINT having (-1) as default Structure Sync would use COLLATE specification and thus generate an invalid statement when connected to a MySQL 4.1.x server.
• When expanding/collapsing the folder tree in the Object Browser by clicking the "+" and "-" in a very fast manner, data could be copied to the editor when it should not.
• When connected to MySQL 3.23 and 4.0.x < 4.0.18 'reorder columns' could generate invalid SQL with a Primary Key definition.
• Improper message was returned when invalid or non-existing path was used for exporting a dump.
• After an unsuccessful import (because of syntax error in the file for instance) the file handler was not properly free'd. As a result next attempt would fail with 'Error saving... ' message. Only HTTP-connections were affected.

Miscellaneous

• "SET FOREIGN_KEY_CHECKS = 0" is now default where it applies (exports, data sync.
• The display for F5/F9 shortcut settings in 'preferences' was changed. 'Reverse' setting now means that F5 executes! It is 'reversed' as compared to what help... keyboard shortcut tells.
• This build does not use 'urlencode' in HTTP header. This is not the final solution but we realize that it is more rare that it is needed compared to the situations where it won't work.

SQLyog 6.14 (November 2007)

Bug Fixes

• ALTER TABLE would generate invalid SQL with column-level comments.
• COMMUNITY version (not ENTERPRISE) could crash when editing connection details.
• On Wine a meaningless error message could occur when selecting a table.
• Exports could generate duplicate rows if there was activity on the screen while exporting. Windows XP was affected - not Vista.
• With specific data 'export as Excel XML' could mistake text data for binary data.
• When a Foreign Key referenced a column used for the definition of a multi-column Primary Key the Schema Designer could display a "1" symbol and (not an "infinity" symbol as it should be) at the 'parent'.
• Horizontal scrollbars were added where missing.
• Fixed a display issue in DATA tab with large DPI monitor setting.

SQLyog 6.13 (November 2007)

Bug Fixes

• Empty or incomplete lines in sqlyog.ini would cause stop reading from the file. As a consequence details that could not be read would not be written. Those details that could not be read were lost.
• Reading from sqlyog.ini was slow with huge number of connections.

SQLyog 6.12 (November 2007)

Bug Fixes

• SQLyog could crash when trying to connect to a server when the thread used for establishing the previous connection had not stopped executing (connection code wasn't thread-safe).
• Structure Sync could generate DROP statements where the name of the object to be dropped was empty.
• Scheduled Backup threw the error "incorrect table name" when backing up all tables from MySQL 4.0 and before ('export' had no such issue).
• Fixed an issue with Migration Tool where importing Foreign Keys could fail when migrating from Microsoft Access.
• Fixed an encoding issue with special characters and Data Sync when syncing between MySQL versions where one supports SET NAMES and the other one does not.
• Fixed an issue that could cause SMTP authentication to fail.
• Fixed an encoding issue with special characters and Data Sync when syncing between MySQL versions where one supports SET NAMES and the other one does not.

SQLyog 6.11 (October 2007)

Bug Fixes

• The fix for BIGINT based PK's greater than 2147483647 in 6.1 introduced another problem with data sync. Symptom was that updates could fail with MySQL error 1064 (syntax error).

SQLyog 6.1 (October 2007)

Features

• Visual Schema Designer. Refer to the help file shipped with the program for details.
• Common Error Dialogue: when a GUI operation returns an error the error message is 'wrapped' in a dialogue explaining the meaning and origin of the error message (note that this is not implemented when manually executing queries from the editor).
• Added an option to specify DEFAULT charset/collation for databases and tables different from 'upper-level' default (server/database).
• Cleaned up CREATE/ALTER TABLE... advanced dialogue (removed largely depreciated 'RAID' and 'PASSWORD' options).
• In CREATE/ALTER TABLE we now perform client-side validation for the most common user errors (such as failure to specify the length of a data type where it is required).
• Functionalities of F5 and F9 can be switched. Defaults are now: F5 updates/refreshes, F9 executes.
• Structure Sync supports column level charset/collations.
• Pagewise display of table data with << (prev) and >> (next) keys/buttons.

Bug Fixes

• 'change tabletype' was disabled when connected to the most recent MySQL 5.1 releases (due to a recent change in the Information_Schema content with those MySQL versions).
• Fixed an issue with DATA SYNC when the Primary Key was based on a BIGINT and value for this PK field was greater than 2147483647
• With a large ('wide') table specific repeated operation with the SCROLL BARs, SCROLL BUTTONs and arrow keys could cause a crash in the DATA tab.
• If user's 'AppData' path used special characters (due to a localized 'AppData' folder or a user name with special characters) program was not able to access sqlyog.ini for read and write operations.
• Solved the problem reported by a fraction of users that the sqlyog.ini file was not copied when upgrading from 6.05 and earlier versions.
• Fixed a crash with the FIND dialogue.
• Fixed a bug with Stored Procedures and Structure Sync. After executing the sync script from the editor it still could occur that the sync tool reported differences.
• Importing a dump could add redundant spaces in the definition of SPs, triggers etc. This was not critical for the content/meaning but would affect Structure Sync and other comparison tools.
• Fixed a crash that could occur in Migration Tool when opening a saved jobfile.
• Lots of small bugfixes, usability improvements and small requests implemented.

SQLyog 6.07 (September 2007)

Bug Fixes

• In 6.06 we re-enabled reconnect in Structure Sync (it was accidentally disabled since 6.0). However after a reconnect the program could enter an infinite loop. A crash could result from this.

SQLyog 6.06 (August 2007)

Features

• Files used by SQLyog that are not read-only (.ini, .log, .err) are now no longer created in 'program files' files tree (or what localized name it has). The storage follows Microsoft recommendations for the various Windows versions. Existing files will be moved when program is started first time and a backup created in the original position. Windows Vista has actualized this.
• CREATE/ALTER TABLE GUI now supports '' (two singlequotes) in the DEFAULT column of the grid for defining an empty string as column default. If column type is not char, varchar, varbinary, set or enum a warning will display (that is also true for binary and bit types, where MySQL accepts '' as default - but with strange results!). To use the literal string '' (two singlequotes) as column default enclose it in backquotes like `''`.

Bug Fixes

• Fixed an issue with 'auto-complete' introduced in version 6.05 where autocomplete windows did not show if cursor was in last position of the editor.
• Fixed an issue with empty strings when migrating data from the Sage accounting software on Win2K.
• Structure Sync truncated default charsets one character at the end ('utf8' became 'utf' etc). This bug was introduced in 6.05.
• Fixed issues with comments inside Stored Procedures, Triggers etc. Structure Sync and exports were affected in various ways.
• Fixed a bug with "copy database to diff host/db" and data sync if both the connections are SSH. Symptoms included 'access denied' error and a database being sync'ed to itself.
• Reconnection in Structure Sync (introduced in version 5.22) was accidentally disabled since 6.0.
• If program was closed in a state where DATA/RESULT pane was hidden, it could not be displayed again after program restart unless 'resetting' sqlyog.ini.

SQLyog 6.05 (July 2007)

Bug Fixes

• The fix in 6.04 for UTF8-encoded files introduced new problems with UTF16-encoded files.
• BLOB viewer was not functional in Wine/LINUX. This bug was introduced in 6.0.
• Font settings in 'preferences' had no effect on RESULT tab in text-mode.
• Fixed a rare issue where - when exporting a stored procedure/function - the first character in the routine name could be substituted with another character.
• When importing data greater than 5120 bytes Migration Tool could truncate data. This bug was introduced in 6.0.
• On Wine/LINUX closing a connection could cause a program crash.
• Solved a highlighting issue with 'quoted strings' and `backquoted identifiers`containing a single qoute ('quoted\'strings' and `backquoted'identifiers`).

SQLyog 6.04 (June 2007)

Bug Fixes

• Fixed a rare crash that could occur when executing a script returning multiple results and an error occurred with the last one.
• HTTP credentials (username and password) were not saving properly in job file.
• 'duplicate table' failed to copy a specified index length.
• The encoding of utf8-encoded files could be detected wrong when reading into the SQL-editor. (note: this is really a bug in Windows utf8 implementation that we 'worked around')
• Fixed a focus issue when two or more connections were open
• Structure Sync could fail with identically named (but different) Stored Procedures on either host

SQLyog 6.03 (June 2007)

Bug Fixes

• Program could crash when opening a migration jobfile containing a query.
• Importing with the Migration Tool using a 'file-DSN' was broken since version 6.0. Various errors could result when trying to use such DSN. 'user-DSN' and 'system-DSN' worked as expected.
• The special PLINK build shipped with SQLyog ENTERPRISE failed to authenticate if there were spaces in the password/passphrase
• When connected to MySQL 3.23/4.0 there were problems when editing data in RESULT TAB with certain special characters. The fix for this in version 6.02 was not complete.
• Fixed an issue where SQLyog threw a 'meaningless' error message.

SQLyog 6.02 (June 2007)

Bug Fixes

• Binary data (such as images) would sometimes not import correctly with the migration tool.
• Migration of UNICODE data is now functional with the MyODBC driver version 3.51 (MyODBC 5.0 (beta) still not supported).
• Cursor focus would be lost when switching between applications with ALT+TAB.
• Fixed a display issue in the RESULT tab with certain special characters when connected to MySQL servers where 'SET NAMES' does not apply (MySQL 3.23 and 4.0).

SQLyog 6.01 (June 2007)

Bug Fixes

• Fixed some issues when migrating from MS SQL Server.
• When opening an existing jobfile in the Migration Wizard the column mapping in that jobfile was not honored.

SQLyog 6.0 (June 2007)

Features

• SQLyog is now fully UNICODE-compliant.
• Advanced GUI Query Builder.
• Filtering of data from the context menu of a cell in the GRID of DATA tab.
• Sorting on multiple columns in DATA tab.

SQLyog 5.32 (May 2007)

Bug Fixes

• Fixed an issue in HTTP Tunneler that could cause a crash.
• Fixed some GUI issues...

SQLyog 5.31 (May 2007)

Bug Fixes

• Fixed an issue in data Sync when TIME type field is used as a primary key.
• When exporting a view without a 'Drop View' option errors could occur while importing.
• Fixed an issue while exporting 'Data Only' from a database containing view.
• Some minor bug fixes.

SQLyog 5.24 - 5.30 (March-May 2007)

Security

• Norton Antivirus 2007 with virus detections from 25th March reported that the SQLyog installers were virus. The files would be quarantined. It was an issue with the NSIS installer-builder. This software was updated. Note: this NAV alert was/is a 'false positive' and with detections 1-2 days later there was no alert!!

Features

• Full support for the SolidDB storage engine - including Foreign Key support. SolidDB from version 5.0.27-0064 is supported.
• A small improvement to the Migration wizard: when importing to an existing table the wizards now displays the columns of that table in the 'map' dialogue.

Bug Fixes

• Fixed a crash occurring with copy operations ('copy database/table', 'duplicate table) with HTTP-connection and php_mysql() extension at the target. HTTP with php_mysqli() extension was not affected.
• When installing version 5.23 or 5.24 over 5.22 (or earlier) the option not to save passwords to the sqlyog.ini file was disabled for existing connections.
• Fixed an issue with ALTER TABLE and UNSIGNED decimal, float and double types.
• Fixed a port forwarding issue with Scheduled Backup and SSH tunnel
• A buffer overrun could occur in datasync (as SQLyog internal string class was not properly used).
• When a string was displayed in the GRIDs and this string was too long to 'fit' the width of the cell the program could enter an infinite loop and become irresponsive.
• When SQLyog was installed to a folder where the path contained a SPACE character and there was a file in the path 'matching' the path-before-the-space (example: in C:\ there was a file named 'program' and SQLyog was installed to 'C:\program files\...') a Windows error message would occur on some Windows versions (including XP) telling that SQLyog was not a valid Win32 program.
• Copy to clipboard with LONGBLOBs could cause a crash.
• Fixed two issues which caused SQLyog to flicker and consume high CPU even in idle mode n Windows Vista.
• Fixed a migration issue with the specific text string 'ignore'.
• Fixed a Stored procedure / Function crash with limited privileges.
• Ampersand (&) was showing as underscore(_) in grids, headers, Object browser and BLOB Viewer..
• Fixed an issue with ALTER TABLE and UNSIGNED decimal, float and double types.
• Several small (mostly GUI-related) fixes.

Miscellaneous

• When doing a 'export as SQL' from a TABLE SQLyog now displays a warning that this export option is not giving a full backup and user should consider using the 'backup as SQL dump' option instead (the 'export as SQL' option introduced with SQLyog 5.22 was intended mainly for use with RESULTs and not TABLEs).
• Removed the preferences option to log queries in history tab during batch jobs. This could consume excessive memory.

SQLyog 5.23 (February 2007)

Security

• Added a 'save password/passphrase' option for the SSH password/passphrase.

New features

• Each QUERY tab now has is own 'child' (set of) RESULT tab(s). Issuing a query from one QUERY tab will not destroy or overwrite the results from a query issued from another QUERY tab. To display a RESULT tab just click its 'parent' QUERY tab. Also MESSAGES, DATA and OBJECT tabs are now 'children' of a specific QUERY tab 'parent'. HISTORY however is shared between all QUERY tabs.
• HTTP-tunneling now supports both the php_mysql() and the php_mysqli() PHP<=>MySQL connection methods. The tunneler will detect which extension is available and use it. If both are available php_mysqli() will be used. One important aspect is that with php_mysqli() the results from a SELECT statements inside of a Stored Procedure will be returned to the CLIENT - and SQLyog will display a RESULT tab for each such query.
• SSH-tunneling now supports public/private key authentication.
• Added support for SSL-encrypted connections.
• As a consequence of the above the Connections Manager design has been reorganized.
• SQLyog now support the PBXT (PrimeBase XT) storage engine for MySQL 5.1 and 5.2 (PBXT version 0.98 and higher). Also Foreign Keys are supported with PBXT.

Bug Fixes

• Fixed a crash (occurring in table menu and context-menu) on Windows 98. This occurred in COMMUNITY version only - not ENTERPRISE. This bug was introduced in 5.22.
• If a connection (only HTTP connections effected) was deleted from Connections Manager details shown for other connections could 'mess up'.
• The drop-down showing the alternative values for a ENUM type column would display empty from RESULT tab (but not from DATA tab and SET types were not affected either).
• It was not possible to specify UNSIGNED for FLOAT and DOUBLE types from 'CREATE TABLE' and 'ALTER TABLE'.
• Fixed some small issues with ALTER TABLE and table level comments (an InnoDB specific issue, an issue with the " ' " character).
• If more connections were open and one of those was a HTTP-connection, then HISTORY data from this HTTP-connection would be written to the HISTORY of another connection, when that other connection window was made active.
• Fixed some rare issues occurring if the connection to the server was lost (a rare crash, a repainting issue).
• DATA SYNC now perform operation on tables in the order DELETE > INSERT > UPDATE. This solves a problem (rows could be deleted on target) occurring with certain type of applications (including Forums) that had some sort of 'trigger code' updating a 'counter' row in a table while that table was sync'ed.
• If a query was running in one connection window, the "STOP running query" functionality would not work in that window if another database was selected in another connection window in between..
• Fixed a multithreading issue that in rare situations could prevent HTTP connections to be successful.
• Fixed a flickering/CPU-utilization issue on Windows Vista.
• On multimonitor systems when the Primary Monitor was the right monitor and program window was moved to the Secondary (left) Monitor and then closed, it would open again on the right/Primary Monitor next time. This is now fixed - it will open where it was last closed (see next note too, however!)
• On Windows 98 when program was closed from a minimized state it would open minimized next time. After that only 'minimized' and 'maximized' (and not 'normalized') states were available. Now it will always open in a 600*600 pixel program window on upper left corner of the (primary) screen when it has been closed from a minimized state.
• In SQLyog 5.13 we implemented 'transparent escaping of the escape character' in CSV export. No matter if the user entered '\' or '\\' as the escape character '\' would be the escape character (and the SQL would be like "... ESCAPED BY '\\' ...". But it was never implemented in CSV-import like this. It is now!
• 'copy to other ... ' would garble utf8 characters if one or more connections were HTTP connections.
• In the XML-schema used by SJA the '&' character (ampersand) was not properly encoded as '&'. As a consequence most SJA jobs would fail when user names, database names etc. used this character.
• Fixed an issue with 'favorites' in Windows Vista.
• Executing a query of the form "SELECT ... from databasename.tablename" would print an error if another database was selected in Object Browser and if one or more query tab was in 'edit' mode. In this situation the QUERY tab will be 'reset' to 'non-edit' mode in such situation.
• 'reorder columns' did not use escaping for column-level comments.
• 'duplicate table' failed to duplicate column-level comments for autoincrement-fields.
• several small (mostly GUI-related) fixes.

SQLyog 5.22 (January 2007)

Contributions/Credits

• With this release we have finished integrating the contribution donated by user Ray Anderson, Sacramento, California. His contributions include quite a lot of small fixes for font and grid -related issues.

New features

• Added direct export to Microsoft Excel XML-format.
• Added 'export data as SQL' as an option. Note: this feature is NOT intended for backup purposes as only INSERT (DATA) statements and a very simple CREATE statement will be created.
• All available export options are now available from RESULT tab and DATA tab as well.
• Redesigned menus and dialogues related to DATA export for better clarity.
• SQLyog Backups are now 'backwards compatible' (they import on earlier MySQL versions due to the use of 'version-dependent conditional comments' (like /*!40101 Engine ...*/)).

Bug Fixes

• Fixed an issue with the editor, where a lot of empty lines would cause SQLyog to fail to recognize where a statement started and stopped.
• Fixed an issue with copy database to different host (it was copying only one stored procedure and one function). This bug was introduced in v5.20.
• 'ALTER TABLE... advanced properties' did not show the non-default options that were already set (except for Storage Engine setting).
• STRUCTURE SYNC did not use the connection code (a function) that the rest of the program does, and would not reconnect if a connection was lost while retrieving the database structure.
• Fixed an issue with DATA SYNC when there were TEXTs and/or BLOBs in a table, but no Primary Key.
• 'reorder columns' raised an error with numerical fields. This bug was introduced in v5.20.
• 'reorder columns' failed on MySQL 3.23. This bug was introduced in v5.20.

SQLyog 5.21 (December 2006)

New features

• Autocomplete speed improvements (about 10 times faster than version 5.20).
• SJA for Windows now has integrated debug facilities like introduced with SQLyog 5.20.

Bug Fixes

• Wrong connections details would cause Notifications Services to crash.
• Backing up an empty database would cause would cause a crash.
• It was not possible to create more than one table with an autoincrement field, unless closing the CREATE TABLE dialogue.
• A few cosmetically issues were fixed.

SQLyog 5.20 (November 2006)

Naming and Licensing

• The free SQLyog version is now named 'SQLyog Community Edition' and is released as Open Source under the GPL license

New features

• User Management fully up-to-date with MySQL 5.1.
• SQLyog now dynamically retrieves the list of available Storage Engines from MySQL.
• Support for SQL-server/Access 'money'/'currency' type with the Migration Tool.
• Added option to name a Foreign Key CONSTRAINT.
• Added an option to 'BLANK' a user's password.
• It is now possible to use the auto_increment attribute with an INTEGER column that is not defined as PK. CREATE TABLE will create the UNIQUE KEY needed for you. Also the Migration Tool now supports such autoincrement field.
• The 'smart' KEYWORDS/FUNCTIONS/DEFAULTS handling introduced with SQLyog 5.1 is now configurable from 'preferences'.
• HTTPS tunneling now supports certificates.
• Font settings enhanced. There are now settings for BLOB-viewer, HISTORY/OBJECTS, Editor and 'everything else' (basically GRIDs). As of 5.2 the last one covers DATA tab, RESULT tab, and CREATE/ALTER TABLE panes. It will be completed in coming versions.
• Added an option to STOP 'copy table/database'.
• DATA SYNC will now show 'signs of activity' when syncing BIG tables.
• Migration Tool can now import data from a VIEW on an ODBC-source to a TABLE in MySQL - provided of course that the ODBC-driver exposes the VIEW and the data in it.
• SQLyog now has built-in debugging capabilities. The implementation of this does not involve additional code or processes running, and does not affect the efficiency of the program.

Bug Fixes

• Fixed issues with import of Foreign Keys and the " ' " character in comments in the Migration Tool.
• (scheduled) backup did encode as utf8 even if you deselected the option in the Wizard. Only the SET NAMES statement was omitted.
• 'copy to other ...' used excessive memory when copying big tables. This is now fixed.
• The import dialogue displayed twice as many SQL-statements as there actually was.
• The warning that more rows would be updated did not display with some special Schemas (schemas without a PK and extensive use of TEXT/BLOBs)
• Conditional comments (like /*! ... */) raised an error with the import tool.
• Fixed an issue with import of indexes from PostgreSQL.
• When two tables named identically except for the LETTERCASE existed in a database 'copy to other ...' would always copy the 'most LOWERCASED' of them.
• When UPDATING SQLyog does generally not include BLOBs/TEXTs in the WHERE clause that it sends. However it should when that column is used for a Primary Key. This is now fixed.
• Migration will now map a TEXT type from SQL Server or MySQL to a TEXT and not VARCHAR
• The display of the total time passed for the query as displayed in MESSAGES tab was wrong (information in status line was correct).
• Several small bug fixes - most of them GUI-related.

SQLyog 5.19 (September 2006)

Bug Fixes

• Fixed a crash when editing data from RESULT-pane.
• Fixed a bug with the Migration Tool that could cause negative values to become 0 (zero).

SQLyog 5.18 (September 2006)

New features

• We have removed the NAG-screen in 5.18 and future versions. It will now only display a discrete link to webyog.com.

Bug Fixes

• Migration Tool TRIGGER functionality was broken.
• Context menu for 5.x Objects was disabled if Connection Window was not maximized.

SQLyog 5.17 (August 2006)

New features

• This release introduces the 'short' DELIMITER format (like the 'mysql' command line client and other programs from MySQL AB) with SQLyog. The old/long format is still supported.

Bug Fixes

• Fixed a port forwarding issue with SSH tunneling when SSH-host and MySQL-host were different. This bug was introduced in 5.15
• Fixed a memory allocation issue with 'autocomplete', that in rare situations could cause SQLyog to crash
• Fixed some other small issues - mostly GUI-related

SQLyog 5.16 (July 2006)

New features

• Editor TAB width is now configurable
• Easier use of keyboard shortcuts to copy and paste data in the grids
• Migration tool has improved error logging and supports import of Unicode data
• Support for Far Eastern character sets in the connections manager ('CJK languages')

Bug Fixes

• It was not possible to switch between connections windows while a long-running query was running
• Several small bug fixes with the Migration Tool
• Small GUI bugs fixed with the Grids
• Fixes to the Structure Sync Tool (GUI issues and an issue with triggers)
• Fixed some issues with the Data Sync Tool when PK was based on a TIMESTAMP or a DATETIME
• A fix with User management (user lost non-GLOBAL privileges if his name or host-descriptor was changed).
• A new connections window would sometimes not show up 'on top' of existing connections windows
• Autocomplete did not update the TAGS-db-files 'on the fly' when an object was created/dropped/changed

SQLyog 5.15 (June 2006)

Miscellaneous

• SQLyog Enterprise will return specific error messages if SSH Tunneling fails for any reason. Previous versions of SQLyog used to return a generic error message

Bug Fixes

• Fixed a bug in HTTP Tunneling when magic_quotes_runtime had the value on in php.ini
• Fixed a minor bug in “Reorder columns” while connected to MySQL 4.1.

SQLyog 5.14 (June 2006)

Miscellaneous

• Major speed improvements

Bug Fixes

• Fixed some small bugs with HTTP-tunneling

SQLyog 5.1/5.11/5.12/5.13 (April-June 2006)

New Features
• Smart 'autocomplete'.
• Smart KEYWORDS and DEFAULTs handling.
• Important enhancements to the STRUCTURE SYNC tool.
• Important improvements for handling of character set (with the data structures and for the connection).
• Favorites feature support file and file-links as well.
• Fully configurable CHUNK and BULK settings.

Miscellaneous

• Dozens (or more) usability improvements and enhancements

Bug Fixes

• Too numerous to mention!

SQLyog 5.02 (January 2006)

Bug Fixes

• Fixed some rare issues where SQLyog could crash.
• Fixed two issues where the amount of memory used by SQLyog would 'build up'. One affected the Migration Tool, another occurred when resizing or moving program window.
• Fixed an issue with escape characters in column comments.

SQLyog 5.01 (December 2005)

New Features

• Support for MySQL 5.1. Fixed some minor issues with previous SQLyog versions related to the freshly released MySQL 5.1 (alpha).

Bug Fixes

• Fixed a bug where SQLyog was not starting in Win98 and Win NT.
• Fixed a critical bug in SQLyog Query tokenizer.
• Fixed couple of bugs in Alter Table option.
• Fixed a bug in BLOB Insert/Update window.
• Fixed a screen repainting issue.
• Fixed an issue in SQLyog Migration Toolkit while importing data from a Fox Pro database.

SQLyog 5.0 (November 2005)

New Features

MySQL 5 Support

• Complete support for all MySQL 5.x features like Stored Procedures, Functions, Triggers & Views
• SQL editors now supports configurable delimiter using the DELIMITER command
• Compatibility with all strict-modes introduced in MySQL v5.x

Data Synchronization

• Data sync tool now supports sync between tables having NO indexes

Scheduled backups

• Support for adding timestamp in the backup file name
• Support for exporting individual tables in a timestamp named folder

SQLyog Job Agent

• Support for providing session xml file path for SJA through a command line argument. Now you can execute: sja -ssession.xml job.xml to provide your own session XML file path

SQL Editor

• Multitabbed SQL editor interface
• Option to generate SELECT and INSERT statements for table with a click of a mouse (or shortcut key)
• SQLyog will now prompt you to save SQL statements before closing the tab. This is configurable through Tools -> Preferences
• Colors used for syntax highlighting are now configurable
• SQL editors now support Goto Line option
• Double-clicking on an object name in the Object Browser copies the name to the Query Editor. This option is configurable from Tools -> Preferences
• Display of object information on node selection in the Object Browser is now configurable through Tools->Preferences

Security

• Added an option where user can specify to save connection details password or not.

Miscellaneous

• Support for SET NAMES in SQLyogTunnel.php
• Support for BLOB columns in WHERE clause while updating a row in Data tab
• Option to fill Excel friendly values while exporting to CSV format. This feature is also available while copying resultset to the clipboard. Now copying & pasting resultsets to Excel for further processing is very straight-forward
• Support for field level comments in Create/Alter Table window
• Support for FK names while creating foreign keys
• HTTP Tunneling now supports importing of SQL batch files containing DELIMITER command
• SQLyog will now display an error message while importing CSV data on a HTTP tunnel
• SQLyog will now create all log and .ini files in the "Application Data" folder if the installation directory is read-only

Bug Fixes

• Fixed a crashing bug in SQLyog Migration Toolkit

SQLyog 4.1 (August 2005)

New Features

• Scheduled ODBC Import - Painless migration to MySQL including the ability to create jobs to transfer external data at regular intervals.

• PHP Tunneler now checks for MAGIC_QUOTES flags. You will need to update SQLyogTunnel.php from the latest build of v4.1.

SQLyog 4.07 (July 2005)

New Features

• Reconnect and re-execute a query if timeout occurs.
• Connection names are now alphabetically sorted in the connection window.
• Support for more images in BLOB viewer.

Bug Fixes

• Fixed a critical bug in Data Sync Tool.
• Fixed a bug where shortcut for hiding ObjectBrowser was not working.
• Fixed a syntax coloring bug in SQL editor.
• Fixed a bug in Alter Table window.
• Fixed a bug with respect to scrolling in result and data grid.
• Fixed a bug related to selection of database in "Export As Batch Script" option window.
• Fixed a bug with export as CSV option.

SQLyog 4.06 (May 2005)

New Features

• Option to select the window that you want to put focus on after execution of a query.

SQLyog 4.05 (April 2005)

New Features

• Powerful scheduled backup with email notification.
• Dialogless result editor with option to update multiple tables.
• Multithreaded query execution with option to allow multiple query execution simultaneously.
• Optimized SQL import, upto 1000% faster then previous versions.

SQLyog 4.03/04 (February 2005)

New Features

• HTTP Tunneling now supports Proxy/HTTP Authentication.

Bug Fixes

• Fixed a non-critical bug in Data Sync Tool.

SQLyog 4.02 (February 2005)

Bug Fixes

• Fixed a critical bug affecting user administration.

SQLyog 4.01 (January 2005)

Bug Fixes

• Fixed a system crashing bug while using multi monitor setup.
• Fixed a system crashing bug in data synchronization when using HTTP Tunneling.
• Fixed a bug where '&' character was handled incorrectly when using HTTP Tunneling.
• Fixed a SQL syntax coloring bug in SQL Editor.
• Fixed bugs while exporting data as CSV.

SQLyog 4.0 (November 2004)

New Features

• SQLyog is now FREE.
• SSH and HTTP Tunneling - smartly manage your MySQL server even if the MySQL port is blocked or remote access to MySQL is disallowed!
• New and improved SQL editor
• Optimized SQLyog Job Agent for data synchronization.
• Fully compatible with MySQL versions 3.22.x to 5.x.
• Passwords are now kept in an encrypted format in sqlyog.ini.
• Improved HELP file.

SQLyog 3.7 (April 2004)

New Features

• SQLyog Notification Services
• SQLyog Database Synchronization Tool now supports 2-way synchronization.
• Now you can execute SJA jobs through SQLyog using Tools -> Job Manager.
• Fully compatible with MySQL versions 3.23.x to 4.1.1.

SQLyog 3.64 (February 2004)

Bug Fixes

• Minor bug-fix in SQLyog Job Agent
• Fixed a bug involving FULLTEXT index in Column Reorder/Drop FK option.

SQLyog 3.63 (November 2003)

Bug Fixes

• Minor bug-fix in SQLyog Job Agent
• Fixed a bug with column width in Insert/Update window.
• Fixed a minor UI bug.
• Fixed a bug in Structure Sync Tool.

SQLyog 3.62 (October 2003)

Bug Fixes

• Minor bug-fix in SQLyog Job Agent

SQLyog 3.61 (October 2003)

• Minor bug-fix in SQLyog Job Agent

SQLyog 3.6 (October 2003)

New Features

• Database synchronization tool.
• Schedule database synchronization.
• Ability to set various preferences like Font, columns width, etc.

Improvements

• Improved keyword and function list for syntax highlighting.
• Improved persistence of Dialog settings.
• Improved column width algorithm in ResultWindow and Insert/Update window.
• Numeric data are right aligned in ResultWindow.
• Bulk insert option breaks scripts into multiple lines, making it more readable.
• Improved user interface. WinXP style icons and toolbars.
• Lot of minor improvements....

Bug Fixes

• Fixed a bug in Copy Table... option where auto_increment were not copied correctly.
• Fixed a bug where edit menu was popping up at wrong coordinates.
• Fixed a bug with repainting of editor window.
• Fixed a bug in Insert/Update wherein you could not specify blank limits.
• Fixed a data display bug in Insert/Update window.
• Lot of minor bug fixes...

SQLyog 3.52 (July 2003)

Improvements

• Improved SQL Editor.
• Fixed a bug wherein Find/Replace dialog was not working.
• Fixed a bug wherein opening of any Modal window resulted in SQLyog being removed from Alt+Tab list.
• Fixed a bug where wrong column numbers were getting shown in the status bar.

SQLyog 3.51 (June 2003)

Improvements

• Improved Execute Batch Option.
• Improved support for MySQL 4.1.
• Improved SQL Editor.
• Allows to select UNSIGNED option for DECIMAL datatype in Create/Alter Table dialog

SQLyog 3.5 (June 2003)

Improvements

• Complete support for MySQL 4.1.
• Vastly improved ODBC Import.
• Restores the app Window Location on StartUp.
• BLOB data does not require double click for viewing if the data is < 255 bytes.
• More compact and optimized executable (480 KB).
• Lots of minor improvements...

Bug Fixes

• Fixed a bug where auto_increment information was not getting copied using Copy Table... option.
• Fixed a bug where TIMESTAMP values were not getting enclosed with ' using Export As Batch Script Option...
• Lots of minor bug fixes...

SQLyog 3.11 (March 2003)

Bug Fixes

• Fixed a system crashing bug in Alter Table option when working with MySQL v4.1
• Fixed a bug in Copy Database To Another Host/DB option, which prevented Structure Only option from getting selected.
• Fixed a bug in Foreign Key Management option, where ON UPDATE [values] was not executed properly.
• Fixed a bug with Bulk Insert option in Export Database As Batch Script.
• Fixed a bug in Diff Tool where a ` character was missing in the generated script.
• Added option to Select/Unselect all tables in Backup/Restore Table option.
• Fixed a resize bug in ResultWindow.

SQLyog 3.1 (March 2003)

Bug Fixes

• Fixed a system crashing bug while altering table structure for tables meeting both of the following attributes :

• - having a column of SET or ENUM type.
  - value list of SET or ENUM exceeds beyond 256 bytes.

• Fixed a bug which effected width of columns in Grid.
• Fixed a system crashing bug in Update For Query Window.

Improvements

• You can now choose individual tables to be copied to another Host/dB
• You can make foreign key relationships within same table.
• Improved SQL Editor to support HUGE SQL Scripts.
• You can filter databases to be added in the the ObjectBrowser.
• Option to select your own Font.
• QueryWindow shows the connection name in its Title.
• Option to truncate database (it will empty all the tables).
• Option to generate Single Insert Statement in Export As Batch Script feature.
• Option to export data of a table in HTML/XML.
• Improved Installer

SQLyog 3.03 (February 2003)

Bug Fixes

• Fixed a system crashing bug while Synchronizing Databases.

Improvements

• You can choose BDB Table Handler while Creating/Altering Tables.

SQLyog 3.02 (February 2003)

Bug Fixes

• Fixed a bug while Updating BLOB data in Insert/Update dialog box.
• Fixed a bug while creating relationship between columns having different names.

SQLyog 3.01 (February 2003)

Bug Fixes

• Fixed a system crashing bug while Synchronizing Databases.

SQLyog 3.0 (February 2003)

New Features

• ODBC Import. The simplest and the most powerful tool to import data from any ODBC compliant database to MySQL.
• Database Synchronization Tool. Bring your remote databases in Sync with a single mouse click.
• Connection Manager.
• Manage relationships on InnoDB tables. All other options fully InnoDB compliant.
• Column Reordering.
• Copy databases between two MySQL hosts.
• Insert/Update on a Resultset of a query.
• Fully updated keyword list for syntax highlighting.

Improvements

• Pick list for Enum/Set values in Insert/Update Dialog.
• Improved data grid. Allows multiple row deletion.
• Option to add column name while exporting data in CSV.
• Multi selection of tables in export as SQL Scripts dialog.
• Empty a database with a single click of mouse.
• Show/Hide edit window.
• Improved error messages.

Bug Fixes

• Primary key values are escaped in Insert/Update dialog.
• Fixed a bug with # commenting style.
• Fixed a bug while saving a BLOB data.
• Fixed a bug in Alter Table dialog for BINARY attribute.
• Fixed a memory leak problem while creating a database.
• Fixed a bug where FULLTEXT was not getting copied in Copy Table option.
• Fixed a bug while trying to delete a row when no Primary Key defined on the table.

SQLyog 2.51 (November 2002)

Improvements

• When a resultset is returned with a BLOB field, the text now gives information to DblClk on the field to view data.
• Now supports dB/Table names with spaces, -, # etc.

Bug Fixes

• Fixed a system crashing bug while altering table structure for tables meeting both of the following attributes :

• - having a column of SET or ENUM type.
  - value list of SET or ENUM exceeds beyond 128 bytes.

• Fixed a bug with current row focus in Insert/Update dialog.

SQLyog 2.5 (November 2002)

New Features

• Alter Table structure in an easy to use Grid mode.
• Insert / Update data in a table.
• Save your BLOB data in a file.
• Client side sorting
• Create / Edit Users.
• Manager permissions for Database / Table / Column.
• View information for Database / Table.
• Export database schema in HTML.
• Execute very big SQL batch files.
• Export data in Fixed Width.
• View all the queries executed in history log.
• Various operations on Tables.

Improvements

• Improved Export functionality.
• Improved Import functionality.
  Improved SQL Editor.
• Show / Hide Result Pane.
• Lot of keyboard shortcuts for "mouse-less" experience.
• And many more...

Bug Fixes

• Lot of bug fixes.

SQLyog 1.71 (August 2002)

New Features

• A very easy to use Table Maker through which you can create tables quickly and easily.
• Support for BLOB fields.
• Option for Table Diagnostics.
• HIDE / SHOW object browser.
• Supports binary data while exporting.
• Flush Host/Logs/Privileges/Tables.
• View results in Text mode as well as in Grid Mode.
• Copy results (all record as well as particular record) from a query in Clipboard in CSV format.
• Option of XML, CSV and HTML export are clubbed in one dialog box. Just give the name and select the type of file from the File Type dropdown.
• mySQLyog has been renamed to SQLyog.

Improvements

• SQL Editor supports more data.
• Lot of keyboard shortcuts for "mouse-less" experience.
• Auto-search facility in the Export Data dialog box.
• Import data dialog box has Select / Unselect All Field option.
• Focus is set on the password field if the connection to mySQL fails.
• Execute current query, selected query or all the query(s) .
• Smarter column width in the Result window when result is in Grid Mode.
• Fills the Connection Dialog Box with the default value for the first time.
• Object Browser does not hold all the data about the server in one instance. Whenever you want the data, it is retrieved at that time. Helps in better memory use and increases the speed to connect to MySQL server.

Bug Fixes

• Fixed bugs while exporting large table structure to a file.
• Fixed bugs while selecting table with long name while exporting data.
• Fixed bugs in exporting long table names and fieldnames while importing data.
• Fixed a system crashing bug when a user gives big name for a personal key.
• Now formatting is done to text if text is pasted from non-text source.
• Fixed a system crashing bug while executing procedure analyse().

mySQLyog 0.9 (May 2002)

• First release of the software.
• Added most of the common features of a query analyzer.
• Supports multiple queries, they have to be separated by ; (C like separation).
• Adding SQL to personal folder added. This relieves you from the burden of saving and opening of the most common and frequently used SQL commands.