WinMySQL Professional - Releases

If you find any bug, please report a description of it to winmysql@online.fr, indicating the WinMySQL Professional version and the MySQL® server used.

WinMySQL Professional 1.01 :

• Bug in the cell zoom window fixed (the «Cancel» button didn't work properly).

• Report title range extended to HTML input forms and PHP3 scripts

• Shareware time increased to 25 seconds

WinMySQL Professional 1.02 :

• With some releases of MySQL® servers, bug on table structures read fixed.

• Cell zoom window width increased to hold more information in title and in the editor.

WinMySQL Professional 1.03 :

• When attempting to update a cell without enough privileges, the old cell value is restored.

• When the link is lost, the status bar is reset to the copyright information.

• It is now possible to choose the delimiter character when exporting the output grid to office automation softwares.

WinMySQL Professional 1.04 :

• The output grid becomes resizeable.

• The application is default launched maximized.

• In HTML and PHP3 generators, it becomes possible to double-click on a column name to select (or unselect) it.

• By clicking on the « MySQL® » logo, the about box appears now with the actual licence values.

WinMySQL Professional 1.05 :

• The memory violation which occured after an «access denied» message when an user (whithout enough privileges) asked the connections list on an old server is fixed.

• The bug which often hung WinMySQL Professional when loading corrupted dBase® data is fixed.

• The bug on dBase® columns of type «logical» always positionned to «FALSE» when loading dBase® data is fixed.

• The bug which improperly left the editor mode switched to on when loading dBase® data is fixed.

• The «Value must be between 1 and 20» message which occured sometimes in big reports is fixed.

• WinMySQL Professional now supports partially dBase IV® and dBase V®.

• It becomes possible to insert data into a MySQL®table from a delimited text file using the new submenu : «Load data from a delimited file (Menu table management)»

WinMySQL Professional 1.06 :

• The bug hindering the possibility to load data from a delimited file in any column order is fixed.

WinMySQL Professional 1.07 :

• To reduce keys piracy, the unlocking key is now hidden. Warning, each attempt to enter into the key dialog box will reset it and force the user to write it again. However, the key stays readable in the «wmyspro.ini» file.

• When exporting a delimited file with data containing carriage returns or line feed, the data recovery by the target software was chaotic. This case is now processed by WinMySQL Professional which replaces these special characters by inoffensive blank spaces.

WinMySQL Professional 1.08 :

• The dialog boxes displaying the tables structure (in submenu «Table management>Structure info») and displaying the databases lists (in submenu «Server administration>Show databases) are replaced by listboxes to prevent very long data lists which could be larger than the screen.

• WinMySQL Professional enters into the Wap world. Indeed, new generators has been added to generate WML decks and PHP3 WML oriented scripts to handle MySQL® databases. These new generators may be invoked with the following submenus :

«Client generators>Wap generators>WML input deck»

«Client generators>Wap generators>PHP 3.0> 'Select' script»

«Client generators>Wap generators>PHP 3.0> 'Insert' script»

«Client generators>Wap generators>PHP 3.0> 'Delete' script»

«Client generators>Wap generators>PHP 3.0> 'Update' script»

WinMySQL Professional 1.09 :

• When submiting a manual query, if the result includes null values, it is now displayed as «NULL» instead of an empty string. This modification is also available for the «EXPLAIN» button of the pseudo terminal.

• However, this modification is unavailable when the output is resulting from features which enable the grid editor mode (because of a possible confusion between a null value and the string 'NULL') : example, when opening a table.

• In the tables creation screen, an incorrect buttons management (on enabling or disabling) resulting from untimely table name changes is now fixed.

• A bug, in the pseudo-terminal concerning the scripts support is now fixed.

• In the tables creation screen, two buttons are added («Up» and «Down») close to the columns listbox, in order to allow to change columns orders at any time of a table design.

• Two «reverse engineering» features are added : after a database analysis, WinMySQL Professional can establish the data dictionary and the SQL scripts which has created the tables. These new features can be invoked with the following submenus :

Server administration>Analyze database>Data dictionary

Server administration>Analyze database>Tables «create» SQL script

WinMySQL Professional 1.10 (aka «1.0.10») :

• A bug «TEXTCOLOR» in HTML generators is now fixed with «TEXT» instead.

• A new feature is now added in blob management : if a blob is a JPEG stream, from now on, it is possible to display it in a viewer. This new feature can be invoked with the following submenu : Record>View Blob JPEG photos

• An important wish from WinMySQL Professional users is now granted : it is possible to generate Windows® applications with a native link to MySQL®. To do it, a new generator is added to the menus : Client generators>WinMySQL Baby apps for Windows®

WinMySQL Professional 1.11 (aka «1.0.11») :

• A bug on menus enabling gave improper status to the «Record» menu when deleting the current table. It is now fixed.

• WinMySQL Professional allowed to drop the active database. It is now forbidden.

• It is now possible to launch the WinHelp file (using the «F1» shortcut) even if WinMySQL Professional had changed the current directory (loading a file from another directory, for instance).

WinMySQL Professional 1.12 (aka «1.0.12») :

• The most recent GPL versions of MySQL® daemons handles a new structure of privileges tables. Then, WinMySQL Professional performed improper queries when adding a user. A new privileges structure detector is now implemented in WinMySQL Professional to fix this trouble.

WinMySQL Professional 1.13 (aka «1.0.13») :

• To handle big tables, new features are implemented : WinMySQL Professional now counts the records before opening a table to allow abortion when if over 6000.
  It is now possible to «activate» a table instead of «opening» it. It means that the table becomes active and then enables lot of menus, but no records are loaded and the «record» menu stays disabled. To do that, a new button is added on the «tables open screen» appearing when invoking the «File>Open>MySQL table».

• Views are not implemented yet on the MySQL® daemons, but are now simulated from WinMySQL Professional. With it, it is possible to handle extracts of tables instead of handling the full tables. To create a view, see the «File>New MySQL view» submenu. To open a view, see the «File>Open MySQLview».

• A new routine warns when WinMySQL Professional is running more than which is allowed by the license. The unregistered version limits to one instance with no mean to override the limitation.

WinMySQL Professional 1.14 (aka «1.0.14») :

• The web script generator is now PHP 4.0 compliant. A same script may work either thru a PHP 3.0 and a PHP 4.0 parser.

• PHP scripts are running now in silent mode on connecting ('@' is added on connection functions).

• The new MySQL official logo replaces the old one on the main screen.

WinMySQL Professional 1.15 (aka «1.0.15») :

• Bugs running the privileges manager with some MySQL® 4.0 versions, are fixed.

• To export universally your MySQL® data (Example : to Oracle® RDBMS), it is now possible to generate an XML datafile from the output grid, just invoking the «Output grid>Save output to XML» submenu.

• The WML client generator inserts a header with the correct mime-type in the PHP scripts to avoid to insert it manually.

WinMySQL Professional 1.16 (aka «1.0.16») :

• PHP generators allow now to choose the behaviour of HTML or WML forms posted variables. Indeed, in PHP3 (or in PHP4 with a php.ini file PHP3 behaviour oriented), posted variables are managed as '$varname' in PHP scripts. In earliers PHP releases, it is recommended to use a PHP safe behaviour. The posted variables are then managed as $_REQUEST['varname'], $_SERVER['varname'], ... You are now allowed to choose the behaviour that you wish (to keep PHP3 compatibility, for instance).