Changes (as compared to 8.22) include:

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.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(0)

Changes (as compared to beta 1) include:

Features:
* Added a context menu to Query Builder canvas.

Bug Fixes:
* 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’.
* GUI fixes – mostly related to new features added in beta1.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(0)

Changes (as compared to 8.22) include:

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.

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

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(0)

Changes (as compared to 8.21) include:

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.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(4)

Changes (as compared to 8.2) include:

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.
* The option to display ‘all’ versus a ‘LIMIT’ed set of rows in DATA tab is now table-specific and saved across sessions (note that – similar to the ‘column width persistence’ feature – connection parameters are not using for identifying a table; only the database name and the table name are).
* Objects in an Object Browser node is now sorted case-insensitive.

Bug Fixes:
* Continuously 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.
* Autocomplete 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 (what is invalid with MySQL).
* 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.
* Updating a ’TIMESTAMP on update CURRENT_TIMESTAMP’ had no effect (the particular column was not listed in the UPDATE-statement sent by SQLyog). This was a necessary restriction before 8.13 but since we – from 8.13 – only list columns that have actually been edited by user, we can now lift this restriction.
* Import External Data – TRIGGERS could fail to update a SQL Server (n)varchar if it contained an empty string.
* If user had selected to save SSH-password locally and later changed the password, the new password was not saved – unless clicking ’save’ button in connection manager interface.
* When importing an external script with no explicit SET NAMES on top, SET NAMES latin1 was executed by SQLyog. Now we won’t do this – and server default charset will have effect for the import in such case.
* Autocomplete did not handle identifiers with the ‘_’ character correctly what could result in too many matches when matching the database with a pattern in editor containing such character.
* Other small GUI fixes.

Miscellaneous:
* This release ships with an updated tunneler file for HTTP-tunneling. In the old tunneler file functions were used that are depreciated in PHP 5.3x.
* The ‘Objects’ menu was renamed to ‘Others’.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(0)

Change (as compared to 8.2) include:

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.
* The option to display ‘all’ versus a ‘LIMIT’ed set of rows in DATA tab is now table-specific and saved across sessions (note that – similar to the ‘column width persistence’ feature -  connection parameters are not  using for identifying a table; only the database name and the table name are).

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.
* 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 (what is invalid with MySQL).
* 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.
* Updating a  ’TIMESTAMP on update CURRENT_TIMESTAMP’ had no effect (the particular column was not listed in the UPDATE-statement sent by SQLyog). This was a necessary restriction before 8.13 but since we – from 8.13 – only list columns that have actually been edited by user, we can now lift this restriction.
* Import External Data – TRIGGERS could fail to update a SQL Server (n)varchar if it contained an empty string.
* If user had selected to save SSH-password locally and later changed the password, the new password was not saved – unless clicking ’save’ button in connection manager interface.
* When importing an external script with no explicit SET NAMES on top, SET NAMES latin1 was executed by SQLyog.  Now we won’t do this – and server default charset will have effect for the import in such case.
* Other small GUI fixes.

Miscellaneous:
* This release ships with an updated tunneler file for HTTP-tunneling. In the old tunneler file functions were used that are depreciated in PHP 5.3x.
* The ‘Objects’ menu was renamed to ‘Others’.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(0)

Changes (as compared to beta 1) include:

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).
* This release ships with an updated tunneler file for HTTP-tunneling. In the old tunneler file functions were used that are depreciated in PHP 5.3x.
* The ‘Objects’ menu was renamed to ‘Others’

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(0)

Change  (as compared to 8.2) include:

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

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Comments(0)

Happy Holidays from Webyog!

It’s been a great year. We have shipped major versions of our products, had record number of downloads and acquired thousands of customers. We wouldn’t be where we are without your support.

As as small token of our appreciation, we will be giving away 2 Kindles to our supporters. To take part in this giveaway all you need to do is:

1. Follow @webyog on Twitter.
2. Tweet on how some specific feature of our products has been useful to you. The two most original and feature-specific entries will win a Kindle.

   For example, rather than Tweeting: “SQLyog rocks!” you should Tweet:
   “The autocomplete feature of SQLyog saves me countless hours of typing everyday”
   OR
   “MONyog has made MySQL replication monitoring less painful”

We’ll choose the winners by searching Twitter for “SQLyog” and “MONyog” among followers. Please send in your entries by 31st Dec 09, 23:59 PST. We will announce the winners in our blog in 1st week of Jan, 2010.

You can also avail a flat 20% Christmas discount on all Webyog products till 31st Dec 09, 23:59 PST. Use coupon code “xmas09″ to avail this discount from our webshop.

Cheers and best of luck!
Team Webyog

Comments(0)

I had one of those situations today that I think every person working with IT experiences from time to time.  I had a problem that took 4 hours to resolve.  Once resolved I realized that doing the right things in the right order (and also memorizing a little better) could have saved me 3 hours and 55 minutes.

The problem was related to SQLyog HTTP-tunneling. When new PHP versions are released it is most often me that verifies that our HTTP tunneling is not broken.  Thus I have followed the PHP 5.3 release cycle from early betas to RC and GA and experienced that very early  PHP 5.3.0 beta  releases did not work with our HTTP-tunnel. However as both 5.3.0 RC and 5.3.0 GA worked fine (as every 5.2.x always did) I executed “SET panic = OFF” against my most important system (old but still a little functional!).

However the panic reoccurred when PHP 5.3.1 was released.  Nothing worked from PHP. I sat for a couple of  hours with a colleague. Small and very simple PHP test applications  did not work with PHP 5.3.1 either on my environment (but worked fine on my PHP 5.2.11 and 5.3.0 configurations). Not a single comma was added to the MySQL general log or error when trying to connect from PHP 5.3.1. The client application hang for considerable time and finally came out with an error that the URL to the PHP script could not be found. Even more frustrating: the test applications and SQLyog/HTTP-tunnel worked fine on another machine with a(should be) identical configuration in Webyog office as well. Needless to say any connection not using PHP also worked fine.

We are aware that some functions in PHP are depreciated in  5.3.x (and will be removed in PHP 6 according to plans).  This may cause problems with our current tunneler on some systems with PHP 5.3.1.  But we have the fix ready to be released with next SQLyog release (and anybody experiencing such problems can contact us for an updated tunneler).  But as 5.3.0 was not affected this was obviously not the problem occurring on my system. It was something else.

We agreed that I should try reinstalling MySQL and Apache from scratch on my system. However before doing so I ran the queries:

SELECT VERSION(); — returned ‘5.1.36-log’
SHOW ENGINES; — returned PBXT as one engine available in addition to the engines from MySQL … hhmmmm …
Now I got it! I remember now that this particular server on this particular system of mine was a forked build with the PBXT engine downloaded from Primebase website.  Installing the standard/official MySQL 5.1.41 solved the problem immediately. PHP 5.3.1 (and thus SQLyog/HTTP-tunnel) connect like a charm.

I am not able to tell what the problem with this server and PHP version is in technical terms.  And probably this server is also now historical so it is probably not very important either now.  But I think Primebase, the MariaDB people, the XAMPP distributors (and everybody building MySQL with PBXT) as well as the PHP developer team should know this issue and try to figure it out (as well as test with their recent builds and PHP 5.3.1), so that it will not happen again.  A forked build should not only work with the (command line) clients shipped with the server but the tools and connectors used by people already.

… (and besides the version string ‘5.1.36-log’ is definitely not good enough for a forked server build).

Comments(4)