Version History - 2007

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 when selecting a table could occur.
  -- Exports could generate duplicate rows if there was activity on the screen while exporting. Windows XP was afffected - 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 definiton of a multi-column Primary Key the Schema Designer could display a "1" and (not a "infinity" symbol as it should be) at the 'parent'.
  -- Horisontal 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

  -- Structure Sync could generate DROP statements where the name of the object to be dropped was empty.
  -- SQLyog could crash when trying to connect to a server when the thread used for establishing the previous connection had not stopped executing ( code for creating connection wasn't thread-safe).
  -- 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 a pointer corruption when importing from a file. This corruption could result in a crash.

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 SchemaDesigner.
  -- 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.
  -- Structure Sync now supports column level charset/collations.
  -- Page wise (using the current LIMIT setting) display in table data with '<' (prev) and '>' (next) buttons.

• Bug Fixes

  -- 'change table type' 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.
  -- Lots of minor bug fixes.
  -- With a large ('wide') table specific repeated operations 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 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.
  -- When reading stored export formatting settings (for 'escaped by', 'enclosed by' etc.) from sqlyog.ini those values would display wrong due to an encoding issue (details: only 6.1 betas 3 and 4 were affected. It was a bug with the fix for special characters in user's AppData path introduced with beta3).
  -- Fixed a crash while opening an ODBC job file.

• Miscellaneous

  -- The default meaning of F5 and F9 shortcuts has been reversed (since beta 4). F5 now means 'refresh' and F9 'execute'. You can change this default from 'preferences' if you want to keep the old shortcuts.

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 single quotes) 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 single quotes) 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 synced 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 database with a Stored Procedure/Function - the leading character of the routine name could be substituted with another character.
  -- With text data greater than 5120 bytes Migration Tool could truncate data. This bug was introduced in 6.0.
  -- Closing a connection on Wine/LINUX could cause a program crash.
  -- Solved a highlighting issue with 'quoted strings' and `backquoted identifiers`containing a singlequote ('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 job file 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' wore not affected.
  -- 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 job file in the Migration Wizard the column mapping in that job file 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.
  -- An issue while exporting 'Data Only' from a database containing view.
  -- Some minor bug fixes.

SQLyog 5.30 (May 2007)

• Bug Fixes

  -- Ampersand (&) is showing as underscore(_) in blob viewer.
  -- Flickering issue in vista.
  -- Migration issue with some specific data.
  -- Stored procedure / Function crash with limited privileges.
  -- An issue with duplicating table.
  -- Several small (mostly GUI-related) fixes.

• Miscellaneous

  -- Removed the preferences option to log queries in history tab during batch jobs.

SQLyog 5.29 (April 2007)

• Bug Fixes

  -- Fixed an issue which caused SQLyog to consume high CPU even in idle mode.

SQLyog 5.28 (April 2007)

• Bug Fixes

  -- Fixed an issue with Migration Wizard.
  -- Fixed an issue with Database Synchronization.

SQLyog 5.27 (March 2007)

• Security

  -- Norton Antivirus 2007 (starting 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'!!

• 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

  -- copy to clipboard with LONGBLOBs could cause a crash.

SQLyog 5.26 (March 2007)

• Bug Fixes

  -- 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.
  -- Fixed some rare GUI issues.

SQLyog 5.25 (March 2007)

• Bug Fixes

  -- When installing 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.

• Miscellaneous

  -- When user is 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).

SQLyog 5.24 (March 2007)

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

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 supports 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).
  -- The drop-down showing the alternative values for ENUM and SET type columns would display NULL as an option even when the column was declared NOT NULL. Both DATA and RESULT tab were affected.
  -- 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 synced.
  -- 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 character 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 our user Ray Anderson, Sacramento, California. 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 form 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 ...*/)).
  -- When connected to MySQL version 5.x we do not any more query Information_Schema when displaying objects in the Objects Browser when other and faster options ("SHOW ...", "SHOW ... STATUS ... ") are there - and they are executable for even unprivileged users, of course!.

• Bug Fixes

  -- Fixed an issue with the editor, where a lot of empty lines would case 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 Stored 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.