Changes (as compared to 8.1 beta 1) include:

Features:
* The caption ‘Migration Toolkit’ was changed to ‘Import External Data’ in menus etc.
* The session.xml file (used by SJA internally) is now not exposed to users in Wizards. The file is created in user’s ‘AppData’ folder when job is invoked from a Wizard. If invoked from command-line files will be created in the folder where the SJA executable is, if not specified differently from command line. The reason for this change is that the two XML files (jobfile and sessionfile) have frequently been confused by users.
* The changes in beta1 were ‘polished’.

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

Comments(0)

Changes (as compared to 8.05) include:

Features:
* Added an option to import text/.csv, .xls (Excel) and .mdb (Access) files without without using a preconfigured DSN setting (user only need to specify the file and  ODBC driver details are passed transparently for user). When using this option also detailed column mapping is possible. Also Office2007 formats (.xlsx, .accdb) are supported like this provided that this Microsoft driver set is installed (it is not per default on any Windows version).
* Added an option to ‘preview SQL’ in CREATE/ALTER TABLE.
* OBJECTS tab was renamed to INFO tab. There is now a choice between the (old) text-based display and a new tabular/HTML-based view.
* New GUI for defining ENUM and SET columns in Create/Alter GUI.
* Autocomplete had a complete ‘overhaul’ resulting in better performance.
* Column width in all GRIDs (not only DATA and RESULT tabs) are now persistent.

Bug Fixes:
* Query Profiler would sometimes fail to display the total time in SHOW PROFILE.
* Fixed a painting issue in Schema Designer.
* Fixed a program crash in copy database/table.
* On Win2K and Wine icons will now be 8 bit color depth, as those environments do not support 32 bit color depth icons properly.
* Autocomplete would sometimes erroneously insert a linebreak.
* Query Builder could generate SQL with an ambiguous column (not prefixing columnname with tablename for a PK-column) if the same column name existed in joined tables. This bug was introduced in 8.03.
* When connected to MySQL before 4.1 a string containing special (non-ASCII) characters could be identified as a binary string. Also this bug was introduced in 8.03.
* Autocomplete was not functional within the argument-list of a function.
* ‘empty database’ (from the database menu/context menu) caused Autocomplete to become non-functional for the session.
* Scheduled backup did not handle the “&” character in file and folder names.

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

Comments(0)

Changes (as compared to 3.07) include:

Bug fixes :
* Query Analyzer did not show correct output when displaying a sorted result. A wrong LIMIT clause was generated when querying the temporary database containing queries.
* Fixed a bug in checksum calculation on 64 bit builds. The checksum is used by Query Analyzer for indexing. On 64 bit wrong sort order could result from this.
* If SSH-tunnelling to a MySQL server had been used and later the setting for ‘Use SSH’ was changed to “No”, MONyog would continue to use SSH tunnel as long as valid tunnelling details were available.

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

Comments(0)

Changes (as compared to 3.06) include:

Bug fixes :
* With SMTP notifications turned “ON” various issues (connection failure, program crash) could occur if SMTP authentication was not used. This bug was introduced with SMTP authentication support in 3.05.
* Fixed a crash with SSH-tunneling.  Only 64 bit build for Linux was affected.
* Counters “cache hit rate”, “pruned as percentage of inserts” and “queries not cached” reported wrong in ‘History/trends’ timeframe.

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

Added: IMPORTANT NOTICE: the Windows TRIAL and single-server binaries have been replaced on May 6th due to a build error with those specific builds. The error could result in mail notifications not working. Only the 2 mentioned binaries were affected. The file names are unchanged, but the installer screen will identify the new builds as ‘3.07a’. Please replace if you have installed one of those. We are sorry for the inconvenience.

Comments(0)

http://www.pinoytux.com/linux/john-dvorak-the-sun-mysql-deal-stinks

Comments(0)

Hi,

We will be present at MySQL Conference & Expo, 2009. If you are around Silicon Valley, don’t forget to meet the team behind your favorite MySQL tools at Booth #317. We are happy to offer a flat 20% discount on all purchases made during this month. Use the coupon code: uc2009 during the purchase.

Also, we are pleased to announce the release of MONyog 3.06.

Changes (as compared to 3.05) include:

Bug fixes:
* Installation on Windows could fail with a js32.dll-related error. Waiting a few seconds and ‘retry’ would solve this but now the error does not come.
* Fixed a ‘false alert’ related to settings for temporary tables (the error occurred because of comparing an integer with a non-integer).
* With slow query logs generated from servers greater than 5.1 Query Analyzer “Max” column would show a value without decimal point if the query count was greater than 1.
* Chart popups from Monitors/Advisors page would sometimes only populate from next time data was sampled (it was a concurrency issue in code).
* 32 bit builds for Linux failed to populate the Monitors/Advisors page. This bug was introduced in 3.05.
* 3.05 TRIAL build for Windows would expire at a fixed date and not after one month as it should.

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

Regards,
Team Webyog

Comments(0)

Hi,

MySQL Conference & Expo, the largest gathering of MySQL developers, users and DBAs worldwide is happening April 20-23, 2009 in Santa Clara, CA. How can it be complete without the leader in MySQL tools… If you are around Silicon Valley, don’t forget to meet the team behind your favorite MySQL tools at Booth #317. We will be more than happy to answer you queries, demo new features, interact with you on product roadmap. We are also happy to offer a flat 20% discount on all purchases made during this month, use the coupon code: uc2009 during the purchase.

Regards,
Team Webyog

Comments(0)

Changes (as compared to 8.04) include:

Features:
* User Management icon was re-introduced in the Icon Bar.
* In DATA and RESULT tab you can now open the BLOB VIEWER for BLOB and TEXT types with any keyboard keystroke (like SPACEBAR). The ‘NOT NULL’ checkbox will then automatically uncheck (if checked) and BLOB VIEWER window is ready for input from the keyboard without any mouse action.

Bug Fixes:
* SQLyog could crash when retrieving binary data over a HTTP-connection.
* Fixed a crash when updating from the RESULT tab (details: a pointer used internally could contain an invalid value).
* When multiple reconnects took place in ‘copy database/table’ with short intervals various issues could occur - including a program crash.
* When Schema Sync CREATED a table having a string column with default ” (empty string) the default was not created for that column (it was no problem if the table on <target> existed in advance and was ALTERED)..
* On MySQL 4.1 and 5.0 SHOW FULL FIELDS does not expose an ON UPDATE CURRENT_TIMESTAMP clause for a TIMESTAMP column . We will now get this information from SHOW CREATE TABLE . The most serious problem before this was that when syncing from 4.1/5.0 to 5.1/6.0 an ON UPDATE CURRENT_TIMESTAMP clause could erroneously be dropped on target.
* Also this release contains a large number of GUI-releated fixes including fixes for painting issues and Object Browser issues related fixes. Also the Object Browser fixes in 8.04 introduced new issues that were now also fixed.

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

Comments(2)

Changes (as compared to beta 2) include:

Bug Fixes:
* When Schema Sync CREATED a table having a string column with default ” (empty string) the default was not created for that column (it was no problem if the table on <target> existed in advance and was ALTERED) .
* On MySQL 4.1 and 5.0 SHOW FULL FIELDS does not expose an ON UPDATE CURRENT_TIMESTAMP clause for a TIMESTAMP column . We will now get this  information from SHOW CREATE TABLE .  The most serious problem  before this was that when syncing from 4.1/5.0 to 5.1/6.0 an ON UPDATE CURRENT_TIMESTAMP clause could erroneously be dropped  on target.

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

Comments(1)

Bug Fixes:
* Fixed a critical bug in Beta 1: BLOB and TEXT types would not update from the RESULT tab.  The ‘red alert’ that data were changed but not saved would disappear, but no SQL was sent to the server.

Miscellaneous:
Beta 1 release notes reading:
* The SET NULL checkbox in BLOB VIEWER will now uncheck automatically when user types into the BLOB VIEWER window.
.. were incorrect.  Correct  documentation for this new implementation is
* In DATA and RESULT tab you can now open the BLOB VIEWER for BLOB and TEXT types with any keyboard keystroke (like SPACEBAR). The ‘NOT NULL’ checkbox will then automatically uncheck (if checked) and BLOB VIEWER window is ready for input from the keyboard without any mouse action.

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

Comments(0)