Post navigation

SQLyog 8.03 beta1 Has Been released

Features:
* New major feature: column width persistencein 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 <ENTER> 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 <source> and <target> databases.
* The program dialogues for SHOW variables/processlist/status, SHOW warnings with CSV-import and Table advanced properties are now resizable.

I updated my Vista last night actually and it does not crash for me! Please do not assume that everybody experiences what you do. As told by Navay we need to exchange information to find the reason. This Blog is not the proper place!