This section documents all changes and bug fixes applied to MySQL for Excel since the release of 1.3.0. Several new features were added the 1.3.x branch, for more information see What is New in MySQL for Excel 1.3.
Upgrading from versions MySQL for Excel 1.2.0 and lower is not possible due to a bug fixed in MySQL for Excel 1.2.1. In that scenario, the old version (MySQL for Excel 1.2.0 or lower) must be uninstalled first. Upgrading from version 1.2.1 works correctly.
PivotTables are normally placed to the right (skipping one column) of the imported data, they will not be created if there is another existing Excel object at that position.
When reopening a saved Excel workbook that contains imported MySQL data, MySQL for Excel attempts to reconnect the Excel tables with the corresponding MySQL databases where the imported MySQL data was imported from. If the MySQL connections are not found, then a new dialog prompts you to either ignore, create, or delete the missing connections. Ignore allows you to work offline, and the dialog will open the next time the Excel workbook is opened. (Bug #18961860, Bug #72966)
Control + A now selects all tables and views in the "Database Objects" selection panel. (Bug #18961544, Bug #72963)
Data could not be imported from a remote MySQL server. (Bug #19012634, Bug #73040)
Thedialog was not populated with information from the selected MySQL connection. (Bug #18968777, Bug #72990)
In Excel 2013, importing the same table twice in the same Excel worksheet failed after deleting the Excel table linked to in the first report. (Bug #18962670, Bug #72976)
Data could not be imported to the left of previously imported data if the new data intersected with the existing import. (Bug #18962617, Bug #72975)
After importing data, clicking Data tab would fail to refresh the data, and it generated an "Initialization of the data source failed" error. (Bug #18962538, Bug #72974)from the
When exporting data, a duplicate entry was sent to the MySQL server when data was exported to a new table with the First Row Contains Column Names check box deselected. The generated error was similar to "Error while inserting rows... MySQL Error 1062: Duplicate entry '1' for key 'PRIMARY'". (Bug #18962470, Bug #72973)
With the Create a Pivot Table with the imported data option enabled, Data Import failed to create a PivotTable for tables that contained a large data set. (Bug #18962371, Bug #72972)
When importing tables, the Pick related Tables or Views feature did not function in Excel 2007 or Excel 2010, but did in Excel 2013. (Bug #18962354, Bug #72971)
For new columns, the Export Data dialog would not accept manually typed in data types that contained a parenthesis, such as
ENUM. (Bug #18962214, Bug #72970)
LinearRingwere removed from the list of valid data types, so they no longer appear in the Data Export data type form. (Bug #18962184, Bug #72969)
Hovering over elements in the MySQL connecting and object listing could cause the text of each item to be bold. (Bug #18962130, Bug #72968)
Imported data would not refresh if the table name was changed in Excel during the import. The table name is no longer used to verify the MySQL connection. (Bug #18961806, Bug #72964)
Edit Sessions failed to restore with sessions that contained tables with zero DATETIME values.
Edit Sessions would also fail to restore when MySQL for Excel was started on a currently opened Excel workbook. (Bug #18889495, Bug #72842)
Attempting to import a table with ENUM values failed with an "Input string was not in a correct format." error. (Bug #18728748, Bug #72434)
References: See also: Bug #18962214, Bug #72970.