Changes (as compared to 7.13) include:

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

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

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

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

Update: Thank you all for making this campaign a stupendous success. We are extending this offer till 5th Dec 08, 23:00 PST succumbing to users demand. Many corporate users requested us to extend the offer as they require time to get official approval. Pick your copy right now! Use coupon code blkfrdy08 to get 50% off.

Happy Holidays!

Digest this before you dig in to that turkey. A never before offer, 50% flat discount on all Webyog products. Hurry up, this offer is valid only till 1st Dec 08, 23:00PST 5th Dec 08, 23:00 PST.

Still using SQLyog Community Edition? Held off buying SQLyog Enterprise Edition? This offer is literally too good to pass up. Its time to own your copy of SQLyog Enterprise with all the PowerTools. Check out what Enterprise Edition has to offer.

Worried about your MySQL server’s health? Monitor it like a PRO. Get MONyog - MySQL Monitor & Advisor. Your MySQL DBA in a box! Check what it has to offer.

Want to extend your maintenance period? Don’t think twice, head right away to Customer Area. On extension, you get free access to all future release of the respective products & unlimited ticket based support for one year.

Use coupon code blkfrdy08 to avail 50% discount on all your purchases. Please note that this offer is valid only till 1st Dec 08, 23:00PST 5th Dec 08, 23:00 PST.

Changes (as compared to 7.12) include:

Bug fixes:
* Fixed a rare crash in Schema Sync. This issue was discovered when testing internally. No user had reported this.
* Management of column-level privileges was not functional.
* It was only possible to select a single group of objects in GRIDS with the shift+click modifier.

Miscellaneous:
* Autocomplete now uses secure atomic transactions when writing to SQLite databases (’Tags files’). We had a few reports of random program crashes that could be traced down to corrupt SQLite databases. This corruption will now not happen any more.

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

Features:
*  This release adds a ‘basetime’ setting in MONyog. This setting (if defined by user) will be used for calculation of uptime-base counters.  The reason for this implementation is that if FLUSH STATUS is executed with a MySQL server, the server status variables will be reset to the same value as would be after a server restart. There is one important exception however and that is the ‘uptime’ status variable itself. This single status variable is not affected by FLUSH STATUS.  So to get true uptime-based counters in MONyog with servers that do not support the ‘uptime_since_flush_status’ variable (and currently only 5.0 COMMUNITY servers from 5.0.37 do - not ENTERPRISE servers and not any other major branch than 5.0 and also not 5.0 before 5.0.37) you will need to define a ‘basetime’ in MONyog greater than or equal to the time where FLUSH STATUS was executed last time. Refer to documentation for full details.
* Improved the purging logic with the MONyog embedded database.  Now also system CPU load is considered and purging operations will be skipped if CPU is high.  This is a further improvement to the change in purging logic introduced in version 2.5.

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

Changes include:

Bug fixes:
* Fixed a rare crash in Schema Sync.  This issue was discovered when testing internally.  No user had reported this.
* Management of column-level privileges was not functional.
* It was only possible to select a single group of objects in GRIDS with the shift+click modifier.

Miscellaneous:
* Autocomplete now uses secure atomic transactions when writing to SQLite databases (’Tags files’). We had a few reports of random program crashes that could be traced down to corrupt SQLite databases. This corruption will now not happen any more.

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

Bug fixes:
* SFTP log downloads used excessive memory on Linux.
* Version 2.82 introduced a unresolved dependency with a libcrypt library on some Linux distros (including some CentOS and OpenSuSE distros).
* Installation on Windows 2000 could fail due to a dependency on a .dll not standard on this Windows version. Also this was introduced in 2.82.
* The status indicator for log downloads could display wrong for large files (> 2 GB).

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

Changes (as compared to 7.11) include:

Features:
* This release improves the handling of Foreign Keys with HTTP-tunnelling. In Data Sync, Migration, ‘copy to other’, ‘empty database’ and ‘truncate database’ statements are now processed in batches and “SET FOREIGN_KEY_CHECKS = 0″ statement (if selected by user) will be reinstantiated for every batch. This is a 100% solution to problems with FK’s normally occuring with PHP applications/connections due to the non-persistent nature of PHP<>MySQL connections:
* In preferences added an option to ‘force disable FK check throughout HTTP import batch process’. Selecting this will have same effect as above when importing external files with SQLyog (from tools .. restore from SQL-dump) over an HTTP-connection. It is selected as default.

Bug Fixes:
* On Wine selecting individual objects (like a single table) for export/copy could export/copy all. This was yet another issue with the tree-view control in Wine.
* Autocomplete with table alias failed if “FROM” in FROM-clause was written UPPERCASE.
* It was not possible to create the Primary Key on <target> with the Migration tool if using option to import using a user-specified query.
* Dropping a table ON which a TRIGGER was defined did not refresh the TRIGGERs folder for the database in the Object Browser. Also ‘reorder columns’ did not automatically refresh the COLUMNs folder for a table.
* The display in Object Browser could garble if program was minimized/maximized while a query was running.
* Right-clicking a only partially visible cell in DATA/RESULT tab would not select properly.
* The CREATE USER privilege (introduced in MySQL 5.03) was not handled by SQLyog user management.
* Fixed a painting issue in ‘manage privileges’ dialogue introduced with resizability in 7.11.
* Fixed an issue with the CSV import dialogue that could result in a ‘hang’ or ‘crash’.
* When nothing was selected for SQL export an empty file was generated.  Now an error pops up.
* Fixed a crash in data sync. This issue affected only empty tables (or empty WHERE results) without a PK.
* CSV-export escaped wrong inside enclosed/quoted strings. Only the enclose character itself should be escaped, but also field seperator character and linebreaks were.

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

Also SJA for Linux was updated with the fix for the data sync issue.

Bug fix:
* SFTP log downloads failed with the Bitvise ‘WinSSHD’ SSH implementation for Windows.

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

Changes (as compared to first RC) include:

Bug fixes:
* It was not possible to create the Primary Key on <target> with the Migration tool if using option to import using a user-specified query.
* Dropping a table ON which a TRIGGER was defined did not refresh the TRIGGERs folder for the database in the Object Browser.
* The display in Object Browser could garble if program was minimized/maximized while a query was running.
* Right-clicking a only partially visible cell in DATA/RESULT tab would not select properly.
* The CREATE USER privilege (introduced in MySQL 5.03) was not handled by SQLyog user management.

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

Bug fix:
* Fixed an issue where data collection would continue to fail with ‘database locked’ error message in the MONyog.log. We now roll back the query generating the lock and collection can continue (this was reported happening by a single user (only) after an MONyog upgrade).

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

Features:
* This release improves the handling of Foreign Keys with HTTP-tunnelling. In Data Sync, Migration, ‘copy to other’, ‘empty database’ and ‘truncate database’ statements are now processed in batches and “SET FOREIGN_KEY_CHECKS = 0″ statement (if selected by user) will be reinstantiated for every batch.  This is a 100% solution to problems with FK’s normally occuring with PHP applications/connections due to the non-persistent nature of PHP<>MySQL connections:
* In preferences added an option to ‘force disable FK check throughout HTTP import batch process’.  Selecting this will have same effect as above when importing external files with SQLyog (from tools .. restore from SQL-dump) over an HTTP-connection.  It is selected as default.

Bug Fixes:
* On Wine selecting individual objects (like a single table) for export/copy could export/copy all.  This was yet another issue with the tree-view control in Wine.
* Autocomplete with table alias failed if “FROM” in FROM-clause was written UPPERCASE.

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

		Dashboard view of the Top 5 tables being used by this blog. Current release of MONyog shows the disk usage even at table level.

Changes (as compared to 2.72) include:

Features:
* Added new monitoring module displaying disk usage information for databases and tables.
* Display of slow log data in Log Analyser had added more information (about when query occured, information about number of rows examined and sent)

Bug fixes:
* When a multibyte character was used in a connection name the display would garble and also the connection could not be deleted from GUI.
* When connection was not available the caption for counters should display “n/a”. Since 2.71 it would instead display a string exposing an internal value (example: “NumCounterWithSeconds”)

As compared to 2.8 beta1 this also includes:

Feature:
* Disk usage (table level view) now displays the ENGINE for every table.

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

Introduction

If you are hosting your website with Yahoo Small Business Hosting, you will be forced to use a web based admin tool to manage your MySQL database. In fact, the help page on managing MySQL categorically mentions that “You will not be able to access your database using a desktop client or other tools run outside of Yahoo!”(I bet they don’t read our blog). In this article, I will show you how you can use all the cool and powerful features of SQLyog Enterprise with Yahoo Small Business Hosting. The same concepts can be applied to connect to other hosting providers like Godaddy, Network Solutions etc. which don’t provide direct access to MySQL database.

Step by Step Setup Guide

1. Login to your Yahoo web-hosting and you will land in home page of “Web Hosting Control Panel”.

2. Select “Create and Update Tab” in the Web Hosting Control panel.

3. (Optional) Click “MySQL Database” under “Other Site Building and Editing Tools” to create/alter your MySQL username/password. If you already know your MySQL user name and password, skip this step.

4. Now you need to upload the Tunnel Page (shipped with SQLyog Enterprise) to the Yahoo Web Server.

5. Select “Easy Upload” option under “File Management Tools”.

6. Type in the path to SQLyogTunnel.php (available in the SQLyog Enterprise installation folder) and click on the “Upload Files”  button.

7. Verify the uploaded file by accessing it with a browser.

8. Start SQLyog Enterprise and configure the Connection tabs as specified in the screenshots. Change the User Name and Password to your Username/Password specified in Step 4. Make sure that the MySQL Host Address is set to “mysql” and not  “localhost”.

Click “HTTP” tab, Check “Use HTTP Tunneling” & in the URL field, provide the URL to SQLyogTunnel.php under your domain and click on “Connect”.

9. You are now connected to your hosted MySQL Server. Enjoy the power of SQLyog Enterprise!

Download trial version of SQLyog Enterprise here.

Bug fixes:
* Pressing Crtl+end in GRID did not show the last row. This bug was introduced in 7.1.
* Fixed a flickering issue in Data tab. It was a threading issue related to the STOP button introduced in 7.1.
* When executing a query not returning a result set, focus would leave editor (unless the ‘keep focus on editor’ option was set).  This made no sense.  Now focus will be kept on editor if there is no result set.
* Data sync could fail with column names containg a SPACE character and if specific keywords was used for column names.

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

Also SJA for Linux was updated with the fix for the Data Sync issue.

Features:
* Added new monitoring module displaying disk usage information for databases and tables.
* Display of slow log data in Log Analyser had added more information (about when query occured, information about number of rows examined and sent)

Bug fixes:
* When a multibyte character was used in a connection name the display would garble and also the connection could not be deleted from GUI.

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

Changes (as compared to 7.02) include:

Features:
* Added keyboard shortcut (F6) for Edit Index.
* The behaviour of Ctrl+R shortcut was slightly changed. It will now position cursor inside the active tab in Result pane. Before it was functional only with DATA tab and RESULT tabs.
* Added tab-navigation (for query tabs) entries in Edit-menu. Also the active Query tab can now be closed from menu.
* In certain situations Schema Sync would generate CHANGE-clauses for a column that basically did nothing (changing column to what it was). This is now ‘cleaned up’.
* A tab in the Query pane (a Query tab, a Schema Designer tab and a Query Builder tab) can now be closed with Alt+L keyboard shortcut and can now be navigated with Ctrl+pgup and Ctrl+pgdn keyboard shortcuts.
* Favorites are now displayed using Scintilla editor component. For statements with complex formatting this makes the preview more readable.
* Autocomplete now supports alias in UPDATE and DELETE statements.
* BLOB viewer and the program dialogues for schema sync, create/alter table, manage indexes (including sub-dialogues) manage foreign keys (including sub-dialogues) and manage privileges are now resizable. From now resizable dialogues have a ‘gripper’ icon in right bottom corner.
* Added a movable ’splitter’ between the object area and the script area in schema sync dialogue.
* Preferences dialogue was redesigned.
* Added an option in Preferences to ‘Automatically refresh DATA tab on focus’. This was the program behavior before 7.0. In 7.0 to 7.02 it was not. Now it is optional.
* Shift+click is now functional for multiple selection everywhere in GRIDS (before it was only in Result/Table Data tabs).
* ’show in text’ (Ctrl+L) is now functional for both DATA tab and RESULT tab. Also ‘Find’ (Ctrl+F) now works with DATA tab in text mode.
* Stop option implemented in data tab. This is in particular useful if accidentially the ’show all’ option was selected for a huge table.
* Added an icon in data tab tool bar indicating if current display is filtered. Also from this icon ‘reset filter’ can be applied directly.
* Added option in Schema Sync to compare all objects or compare only tables.
* Now the result tab displays the query as a ribbon at the bottom. This is useful where more queries are executed from the same editor tab.
* Refresh option included for show variables, show processlist and show status.
* Changed functionality for shortcut F3; now it pops up ‘Find’ dialog (before it was for keyboard shortcut dialog - F12 is used for this now).
* The sync script generated by Schema Sync could fail when a change in columns used for Foreign Key(s) or a change with the Foreign Key itself was attempted.
* The display of execution time etc. for queries (in MESSAGES tab, HISTORY tab and statur bar) was reorganised for better clarity.

Bug Fixes:
* The GRID would truncate the display of strings longer than 511 characters.
* When a user-defined DELIMITER and a comment occured close to another in the program editor, the editor tokenizer component could fail to identify exactly where a statement began and ended.
* Data Sync could fail with a table having no Primary Key, but more Unique Keys, if the same column was used for defining more than one of the Unique Keys of the table. This was introduced with the new Data Sync code of 7.0 (before 7.0 Unique Keys were not used by Data Sync at all - only Primary Keys were).
* Fixed an escaping bug in Data Sync.
* Fixed an issue with WHERE clause in Data Sync.
* Proxy authentication details were not written correctly to jobfile by SJA wizards.
* Since 7.0 the WHERE clause defined by user in migration wizard was not written to jobfile.
* In Wine Schema Sync could generate an erroneous sync script (specific functions on Wine functioned slightly different than the original Win32 API).
* Fixed a number of GUI related issues.
Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Bug fixes:
* On 64 bit Linux systems running MONyog 64 bit builds queries could be considered identical by Log Analyzer even if they were not.
* Authentication failed if the “#”character was used in password.

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

Changes as compared to 7.1 beta2 include:

Features:
* Stop option implemented in data tab. This is in particular useful if accidentially the ’show all’ option was selected for a huge table.
* Added an icon in data tab tool bar indicating if current display is filtered. Also from this icon ‘reset filter’ can be applied directly.
* Added option in Schema Sync to compare all objects or compare only tables.
* Now the result tab displays the query as a ribbon at the bottom.  This is useful where more queries are executed from the same editor tab.
* Refresh option included for show variables, show processlist and show status.
* Changed functionality for shortcut F3; now it pops up ‘Find’ dialog (before it was for keyboard shortcut dialog - F12 is used for this now).
* Now also ‘manage privileges’ dialogue is resizable.  From now resizable dialogues have a ‘gripper’ icon in right bottom corner.

Bug Fixes:
* Fixed an escaping bug in Data Sync.
* Fixed an issue with WHERE clause in Data Sync.
* Proxy authentication details were not written correctly to jobfile by SJA wizards.
* Since 7.0 the WHERE clause defined by user in migration wizard was not written to jobfile.
* In Wine Schema Sync could generate an erroneous sync script (specific functions on Wine functioned slightly different than the original Win32 API).
* The sync script generated by Schema Sync could fail when a change in columns used for Foreign Key(s) (or a change with the Foreign Key itself) was attempted.

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

Bug fix:
* Fixed some issues with JSON strings that could prevent objects in the MONyog browser interface to populate with data.  Most important ‘Monitors/Advisors’ page would fail to display if a username contained a doublequote character.

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

Features:
* CPU optimisations in both MONyog (server) process (in particular when ‘Monitors/Advisors’ page was being viewed) and browser processes (viewing Dashboard could cause high CPU usage in Firefox browser in particular).

Bug fix:
* Fixed a dependency with the SSH library that could cause failure to install in Win2K. This was an issue with the updated SSH library introduced with version 2.5.

Miscellaneous:
* The RPM installer scripts for Linux were updated in various ways. This solves issues on specific distributions including: 1) uninstall with the SuSE/YaST ’software management’ GUI was not possisble. 2) It was not always possible to install on top of a running MONyog service - sometimes it was necessary to stop service manually before upgrading. Also note: when updating from trial to single/multi server or from single server to multi server it is still necessary to uninstall the old version first. And when installing this version (applies only when using the RPM build) any older version will have to be removed with the “rpm -e ..” (rpm -e MONyog-trial/rpm -e MONyog-single/rpm -e MONyog-multi) command in advance (distribution-specific GUI tools may not work with versions before this one, so please use the RPM console command). We apologize for this but there is no other way.

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

Changes (as compared to 2.51) include:

Features:
* Log Analyzer code has been completely refactored resulting in better performance and stability and more maintainable code.
* The progress indicator for downloads in Log Analyzer page is now a true quantitative progress bar.
* Error messages in Log Analyzer were rewritten. Every single possible error is now differentiated by a specific message providing help for the situation.

Bug fixes:
* “Group by” option in history/trends page could deliver incorrect results if MySQL and MONyog were using different timezones.
* With SFTP connection to the log file selecting “ALL” for log size to be downloaded in Log Analyzer page could have the result that the log file download would last forever.
* Analyzing log chunks containing BULK INSERT statements could in special situations cause a program crash.
* Fixed a bug with resolvement of time in log analyzer that could result that no queries or less queries than what should be were returned. The most recent queries would sometimes not be shown. Issue was only if log was retrieved with SFTP.
* When retrieving logs stored in tables the substitution of literals would fail for binary data.
* When downloading a log MONyog would continue to download in the background until end of file even after STOP button was clicked.
* In the display of queries from the Processlist page special characters could garble.
* Also in Log Analyzer page special characters would not always be indentified correctly. This bug also affected records with binary data. Both display and grouping was affected (depending on where those occurred - in plain strings or in identifiers).
* Repeatedly switching between sorting and show details for a slow query log in log analyzer could in certain situations crash MONyog.
* Installing a RPM multi/single server build on top of a trial build (and vice versa) resulted in that they were installed in parallel. Also on SuSE MONyog was not registered with the correct runlevel. The RPM has been updated to fix this.

Miscellaneous:
* Display of servers is now sorted in the order of the server/connection name. Earlier the internal ID was used for sorting. Also note that now no MONyog restart is required for changing sort order. A connection rename alone will do.

As compared to the 2.6x betas this also includes:

Bug fix.
* Reporting the execution time of a query in ‘query sniffer’ was inaccurate. This was an issue with the 2.6 betas only. 2.5x were not affected.

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

Changes as compared to beta1 include:

Features:
* Also BLOB-viewer is now resizable.
* Added keyboard shortcut (F6) for Edit Index.
* The behaviour of Ctrl+R shourtcut was slightly changed. It will now position cursor inside the active tab in Result pane. Before it was functional only with DATA tab and RESULT tabs.
* A tab in the Query pane (a Query tab, a Schema Designer tab and a Query Buider tab) can now be closed with Alt+L keyboard shortcut.
* In certain situations Schema Sync would generate CHANGE-clauses for a column that basically did nothing (changing column to what it was). This is now ‘cleaned up’.
* Favorites are now displayed using Scintilla editor component. For statements with complex formatting this makes the preview more readable.
* Added tab-navigation (for query tabs) entries in Edit-menu.  Also the active Query tab can now be closed from menu.
* ‘Find’ is now possible in DATA  tab in text-mode (just like it was in RESULT tab).

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

Changes (as compared to 2.6 Beta 1) include:

Bug fixes:
* repeatedly switching between sorting and show details for a slow query log in log analyzer could in certain situations crash MONyog.

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

Changes (as compared to 2.52 RC) include:

Features:
* Log Analyzer code has been completely refactored resulting in better performance and stability and more maintainable code.
* The progress indicator for downloads in Log Analyzer page is now a true quantitative progress bar.
* Error messages in Log Analyzer were rewritten.  Every single possible error is now differentiated by a specific message providing help for the situation.

Bug fixes:
* When downloading a log MONyog would continue to download in the background until end of file even after STOP button was clicked.
* In the display of queries from the Processlist page special characters could garble.
* Also in Log Analyzer page special characters would not always be indentified correctly. This bug also affected records with binary data. Both display and grouping was affected (depending on where those occurred - in plain strings or in identifiers)

Miscellaneous:
* Display of servers is now sorted in the order of the server/connection name.  Earlier the internal ID was used for sorting.  Also note that now no MONyog restart is required for changing sort order.  A connection rename alone will do.

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

Features:
* Query tabs can now be navigated with Ctrl+pgup and Ctrl+pgdn keyboard shortcuts.
* A query tab can now be closed with Alt+L keyboard shortcut.
* Autocomplete now supports alias in UPDATE and DELETE statements.
* Program dialogues for schema sync, create/alter table, manage indexes (including sub-dialogues) and manage foreign keys (including sub-dialogues) are now resizable.
* Added a movable ’splitter’ between the object area and the script area in schema sync dialogue.
* Preferences dialogue was redesigned.
* Added an option to ‘Automatically refresh DATA tab on focus’. This was the program behavior before 7.0. In 7.0 to 7.02 it was not. Now it is optional.
* Shift+click is now functional for multiple selection everywhere in GRIDS (before it was only in result/table data tabs).
* ’show in text’ (Ctrl+L) is now functional for both DATA tab and RESULT tab.

Bug Fixes:
* The GRID would truncate the display of strings longer than 511 characters.
* When a user-defined DELIMITER and a comment occured close to another in the program editor, the editor tokenizer component could fail to identify exactly where a statement began and ended.
* Data Sync could fail with a table having no Primary Key, but more Unique Keys, if the same column was used for defining more than one of the Unique Keys of the table.  This was introduced with the new Data Sync code of 7.0 (before 7.0 Unique Keys were not used by data Sync at all - only Primary Keys were).
* Fixed a number of GUI related issues.

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

Changes (as compared to version 7.01) include:

Bug fix:
* If a reconnect took place shortly after ‘Compare’ button in Schema Sync was clicked, the ‘MySQL server has gone away’ error could occur  (details: data from a not updated internal buffer was used - in reality it was before the reconnect that the server ‘went away’!).

Miscellaneous:
*  Reconnects are now written to HISTORY (as a comment)

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

Bug fixes:
* With SFTP connection to the log file selecting “ALL” for log size to be downloaded in Log Analyzer page could have the result that the log file download would last forever.
* Analyzing log chunks containing BULK INSERT statements could in special situations cause a program crash.
* “Group by” option in history/trends page could deliver incorrect results if MySQL and MONyog were using different timezones.

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

I recently came across this article listing SourceForge Community Choice Awards Winners 2008:

http://weblog.infoworld.com/openresource/archives/2008/07/sourceforge_com.html

“Most Likely to Be the Next $1B Acquisition” is phpMyAdmin? Now I am not sure if phpMyAdmin actually is something that can be acquired and if there is any revenue (directly or indirectly) generated from it at all, but in my opinion phpMyAdmin has reached a point close to the end of its life-cycle, and I can hardly imagine there is anything to pay for. Except for very small additions to support new MySQL versions there has - to my best knowledge - been nothing but bug fixes for around 3 years. No new developments. phpMyAdmin basically provides an interface for viewing the content of tables, to execute statements and scripts and view the result. And that’s it.

And don’t miss it - that is useful in lots of situations. If phpMyAdmin is installed on a *AMP server you can access the database from any computer connected to the Internet without having anything installed locally. But the interface is somewhere in between *just usable* and *horrible* (depending on how it is configured and how it integrates in control panel applications etc.)

As time goes by it becomes obvious that
* phpMyAdmin has missed opportunity to provide ‘power tools’ - like synchronization tools, proper migration/import and export tools, GUI environments for schema design and query design, tools for query analysis and optimization etc.
* The simple HTML interface provided by phpMyAdmin is far away from today’s standard of web applications.

I believe there would be a market for a high-quality web based MySQL database administration tool (no matter the license model) if it adopted modern AJAX based web interfaces. The current phpMyAdmin ‘plain HTML interface’ requires that everything (data, images, stylesheets) of the complete page will have to be reloaded or even resent from the server for every page refresh. That results in huge communication overhead, annoying page refreshes and time waste - even in situations where only a small detail on that page needs to be updated. Today’s web users (whether gamers or just gmail users) expect a web interface very close to that of a compiled binary. Because they are used to it like that, and because they know (and see every day) it is possible.

One of the most common remarks from  SQLyog users, that have replied to our recent user surveys, is “What a relief to get rid of phpMyAdmin”.

At Webyog we cannot honestly regret this situation as we benefit from it and do increasingly much for every day. From a more ‘ideal’ point of view one can say it is a shame (and phpMyAdmin indeed should be credited for its huge contribution to the popularity of MySQL in the early days of MySQL). But my guess is the situation is that ‘the train has left the station. No more trains leaving for the foreseeable future. Sorry for you if you did not catch it!’. In other words: I don’t believe the phpMyAdmin community can mobilize the resources to ‘catch the train’ again - also because they (as a community) do not seem to realize how the gap between their application and the best available other options widens for every day.

Also I do not think this situation is special for phpMyAdmin and the phpMyAdmin community actually - on the opposite I think a large percentage of Open Source Community developers simply got out of touch with how the Web has developed over the last 2-3 years. Another good example is the Linux/KDE Konqueror program. I love it because of the many access/connectivity options it provides in one interface, and should I ever shift from Windows to Linux as my primary platform Konqueror would be one of the main reasons .. but (regretfully) it is hardly usable as a webbrowser any more as it did not adopt modern web standards.

Further it is interesting to see how the relationship between PHP and MySQL in general has also changed over the last years. 3-4 years ago they were mostly so closely related that lots of users did not realize the difference and were not able to think of MySQL in other contexts than a PHP-context. We had several complaints at that time from users, that were simply not able to realize that PHP statements and syntax could not be used in the SQLyog SQL editor - and lots of users thought that PHP was a prerequisite for accessing MySQL (and also lots of ISP supporters and even sysadmins told their users so, because even they did not know better!).

But ‘used-to-be patterns’ are breaking up! Examples:
* Since first version 5 release PHP has shipped with the SQLite database. I have seen quite a lot of standard PHP web applications shifting in direction from MySQL to SQLite as their primary/default database option. Also ‘RUBY on the Rails’ project is in that process, I believe. And in particular with ’shared hosting’ that makes good sense in my opinion as everthing - also databases - are stored  in user’s own space on the server (the drawback is of course that direct access to the database bypassing the application can be a problem).
* According to the survey here http://www.paragon-cs.com/mag/issue5.pdf (at the bottom) JAVA is now an equally important client environment for MySQL based applications as is PHP (and this is not because of the acquisition of MySQL by Sun - it started long before that).

Anybody out there want to buy phpMyAdmin (I can spare a few copies!) ?

Bug fix:
* Depending on the chosen installation environment and the Linux distro, the RPM build might not install ‘on top’ of a previous installation.  Before installing a new version it was necessary to uninstall the previous version. This is a limitation with all RPM builds released till now.  From this build and onwards it will always be possible to ‘upgrade on top’ of a previous version. Note: this  was an issue with the RPM installer - not the program binary. There is no change in the binary as such and also no change in the Windows installer and the .gz build for Linux.

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