MySQL for Excel Release Notes  /  Changes in MySQL for Excel 1.1.2 (2013-10-01)

Changes in MySQL for Excel 1.1.2 (2013-10-01)

This section documents all changes and bug fixes applied to MySQL for Excel since the release of 1.1.1.

Functionality Added or Changed

  • A global options dialog was added that can be accessed from the Schema Selection and DB Object Selection panels, where the default timeout for the connection to the DB Server (15 seconds) and query commands (30 seconds) can be changed. (Bug #17191646, Bug #68732)

Bugs Fixed

  • Attempting to use a connection with an expired password would yield an error with "You must SET PASSWORD before executing this statement." A proper dialog to reset the expired password is now generated. (Bug #17354118)

  • Imported text values that begin with an equal sign ("=") were being treated as formulas. By default, these are no longer treated as formulas in Excel, although this behavior can be toggled through the Import Data dialog. (Bug #17354102)

  • After appending data, sometimes the name of the last column would not be detected when data was later inserted. (Bug #17278349, Bug #69220)

  • In Microsoft Excel 2013, opening more than one file in Excel that opens a new Excel window, the MySQL for Excel add-in was present in only one of the Excel windows, and not in all of them as it is in Microsoft Excel 2007 / 2010. (Bug #17272087, Bug #68792)

  • Behavior of the MySQL for Excel toggle button was changed. Instead of just showing or hiding the add-in, it now opens and closes it. (Bug #17272087, Bug #68792)

  • A backslash was inserted before each apostrophe after performing an Edit Data operation. (Bug #17271693, Bug #68669)

  • All spaces typed by the user in an overridden data type for a new column in an Export Data operation were being removed. (Bug #17260260)

  • Overriding the data type by typing "year(2)" or "year(4)" in the Data Type combo box for a column with numeric integer data during an Export Data to New Table operation created a misleading warning stating "Entered Data Type is not a MySQL recognized data type." Entering "year" was accepted, and now "year(2)" and "year(4)" are also considered valid. (Bug #17259915)

  • A "Selected Data Type is not suitable for all the values in this column" error was falsely reported after selecting the "text" data type for a column. (Bug #17259490)

  • Clicking Manage Connections failed to open MySQL Workbench. (Bug #17258966)

  • When Export Data from Microsoft Excel was used to create a MySQL table, and any of the Excel spreadsheet cells contained over 4,000 characters of text, the export failed with the following message: "MySQL Error 1118: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs"

    Under this condition, the data type is now changed to Text instead of Varchar(65535). (Bug #17191633, Bug #69779)

  • Changed the location of the registry where the MySQL for Excel add-in is installed from HKEY_CURRENT_USER to HKEY_LOCAL_MACHINE so that the add-in is now accessible by all users of the system, and not only to the user that installed it via MySQL Installer. For this to work with Excel 2007, a hotfix may be required (see (Bug #16675992, Bug #68746)

  • Connections created from within MySQL for Excel could not be deleted, as the Delete Connection dialog failed to function. (Bug #16500331)

  • Attempting to connect to a MySQL server that was down would emit an error message claiming that an incorrect password was entered. The proper error message is now displayed. (Bug #16239007)

  • Replaced the logo that is shown on the splash screen in the About page.