MySQL for Excel Release Notes

Abstract

This document contains release notes for the changes in each release of MySQL for Excel.

For additional MySQL for Excel documentation, see MySQL for Excel.

Updates to these notes occur as new product features are added, so that everybody can follow the development process. If a recent version is listed here that you cannot find on the download page (http://dev.mysql.com/downloads/), the version has not yet been released.

The documentation included in source and binary distributions may not be fully up to date with respect to release note entries because integration of the documentation occurs at release build time. For the most up-to-date release notes, please refer to the online documentation instead.

For legal information, see the Legal Notices.

For help with using MySQL, please visit either the MySQL Forums or MySQL Mailing Lists, where you can discuss your issues with other MySQL users.

For additional documentation on MySQL products, including translations of the documentation into other languages, and downloadable versions in variety of formats, including HTML and PDF formats, see the MySQL Documentation Library.

Document generated on: 2016-12-23 (revision: 10527)

Preface and Legal Notices

This document contains release notes for the changes in each release of MySQL for Excel.

Legal Notices

Copyright © 1997, 2016, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

This documentation is NOT distributed under a GPL license. Use of this documentation is subject to the following terms:

You may create a printed copy of this documentation solely for your own personal use. Conversion to other formats is allowed as long as the actual content is not altered or edited in any way. You shall not publish or distribute this documentation in any form or on any media, except if you distribute the documentation in a manner similar to how Oracle disseminates it (that is, electronically for download on a Web site with the software) or on a CD-ROM or similar medium, provided however that the documentation is disseminated together with the software on the same medium. Any other use, such as any dissemination of printed copies or use of this documentation, in whole or in part, in another publication, requires the prior written consent from an authorized representative of Oracle. Oracle and/or its affiliates reserve any and all rights to this documentation not expressly granted above.

Changes in MySQL for Excel 1.3.7 (Not yet released, General Availability)

Version 1.3.7 has no changelog entries, or they have not been published because the product version has not been released.

Changes in MySQL for Excel 1.3.6 (2016-01-07, General Availability)

Functionality Added or Changed

Bugs Fixed

Functionality Added or Changed

A new Generate an INSERT statement for each data row option was added to the Advanced Options dialog for Append and Export Data operations. This is disabled by default. A single INSERT statement is generated that inserts all affected rows, unless this option is enabled.

When checked, an INSERT statement for each data row being appended or exported is generated in the resulting SQL query sent to the MySQL server. When unchecked, a single INSERT statement is generated as a bulk data operation, which performs better than multiple INSERT statements.

While row-by-row inserts are slower, for debugging errors it could help determine which row causes an error, since the MySQL Server will process them row by row.

Added column properties to the Export Data dialog to support the definition of Auto Increment and Default Value for new MySQL tables where the data will be exported.

Added a context menu to declare a numeric field to be Unsigned or to have Zero-Fill, accessible by right-clicking the Data Type combo box.

Added the TIMESTAMP data type to the full list of valid data types, as it was not being shown before. Added help tool tips to fields in the Export Data dialog that explain in detail how the column properties work in a MySQL database.

Bugs Fixed

The Pivot Table feature was updated to work with Excel 2016. (Bug #22387425)

Closing the plugin via the Close button in the panel would not toggle the MySQL for Excel checkbox in the Data ribbon. (Bug #22374026, Bug #79655)

Fixed the content detector for the active Excel cell after importing data and after loading database objects when a database is opened. Now, the data options are not enabled until a table is selected. (Bug #22372915)

Append and Export operations would not append/export boolean data. (Bug #22138966)

The MySQL for Excel Refresh All function would throw an unhandled exception. (Bug #22110627, Bug #78941)

With Office 2007, data would not auto-save after closing Excel. (Bug #22081313, Bug #78910)

Numeric data stored in text columns is now correctly formatted by Excel as text, and not as the "General" format that automatically formats cells as numbers when the data is stored in a text object. This fixes the issue where text columns were formatted as numbers, which stripped leading zeros. (Bug #20905284, Bug #76738)

Changed settings for containers and forms to let all UI components automatically scale on different DPI settings. Also removed the restriction to resize the MySQL for Excel's pane, so in case a different DPI setting is used and the fonts look too big, the pane can be resized to see contents as best as possible. (Bug #18099454, Bug #71389)

Changes in MySQL for Excel 1.3.5 (2015-10-23, General Availability)

Functionality Added or Changed

Bugs Fixed

Functionality Added or Changed

A new Append Data advanced option was added, titled Confirm column mapping overwriting. When enabled, dragging and dropping source columns over target columns that were already mapped (in other words, they already contained a mapped source column) now triggers a confirmation dialog asking if the overwrite should be executed. This option is disabled by default as data overwrite is a common operation. (Bug #16239058)

Added a new advanced option named Show column data types above column names. When checked, the Append Data dialog grid will show data type information for columns on source and target grids. This is especially helpful when manually mapping columns.

Added support for the JSON data type that was added in MySQL Server 5.7.

The JSON data type is now selectable from the Export Data column dialog, if the advanced option to show all data types is enabled. All data operations (Import, Export, Append and Edit) now function with the JSON data type.

Bugs Fixed

Attempting to save data to a column where the data can not be written (incompatible data type) now generates an error. (Bug #21898699, Bug #78550)

Changed the way data type related warnings are linked to grid columns in the Append Data dialog. Now the warnings are linked to the target (lower) grid view columns, because a single source column can be mapped to multiple target columns, and the warnings are about source data not being suitable for the target column's data type. (Bug #21898678, Bug #78549)

When scrolling the target MySQL table grid horizontally, the upper column headers that contained names of the mapped source columns were not rendering text properly. The text moved while scrolling, and the column separators disappeared when scrolling to the right. (Bug #21898210, Bug #78548)

Change the data type detection logic for a column's data that was failing when only the first row of data contained data, when the rest of the rows were empty. (Bug #21799680, Bug #78358)

The Append Data dialog was incorrectly mapping columns when only a single row of Excel data was selected to append.

Also, if a single row of Excel data is selected with First Row Contains Column Names enabled, a warning is now displayed stating that no rows are available to complete the append operation. (Bug #21799500, Bug #76517)

Connection information created after the last save was cleared from memory when an Excel Workbook was closed, thus causing the connection information to not write to disk. Now the connection cleanup happens after a Workbook is saved, thereby saving the new connection information. (Bug #21172751, Bug #21089790, Bug #76475, Bug #77016)

Stopped using hidden defined names to store formulas that transform date values into a date format used by MySQL. These defined names were being detected by Excel as macros or user functions that could not be saved in macro-free workbooks, thus generating bogus warnings every time a Workbook was saved when the Excel add-in was active. (Bug #19358961, Bug #73467)

Updated the data connection library to Connector/NET v6.9.8, which fixes the problem of accessing a schema that contained Unicode (non-ASCII) characters in its name. These databases now successfully open. (Bug #17409832)

Deleted stored mappings would remain in the stored mapping method list. (Bug #16493255)

Enhanced the custom grid view control used in the Append Data dialog to automatically adjust the width of the grid columns. This adjustment considers the grid's cell contents, the base column header text, and also the contents of the additional header rows. Before, the target column width was too short. (Bug #16237502)

Changes in MySQL for Excel 1.3.4 (2015-03-06, General Availability)

Functionality Added or Changed

Bugs Fixed

Functionality Added or Changed

Two new options were added to the Manage Import/Edit connection information maintenance dialog. The first is used to automatically remove stored connection information related to Excel Workbooks that are no longer found where they were originally saved. The second new option is used to select all connection information entries that have not been used in the last n days, where n is configurable. (Bug #19789907, Bug #74304)

Bugs Fixed

For Excel 2007, a pop-up warning message incorrectly stated that some features could not be saved in a macro-free workbook would appear when closing a Workbook that was not saved. (Bug #20540331, Bug #75900)

References: See also: Bug #19358961.

The Refresh All action did not function on pivot tables. Each pivot table had to be individually updated. (Bug #20524883, Bug #75565)

When a named table in Excel was filtered using the standard Excel filtering option, this filter was not taken into account when the append function of the MySQL for Excel add-in was called. All rows of the table were inserted, not just the remaining (filtered) ones. (Bug #20433602, Bug #75635)

While the Export Data operation automatically assembles the SET declaration when detecting values suitable for a SET data type (such as lists of values separated by commas), the SET declaration assembled by MySQL for Excel was incorrect and did not correctly merge all of the values nor did it remove the duplicates when generating a single list of suitable values. (Bug #20426374, Bug #75660)

An error similar to "Exception from HRESULT: 0x800A03EC" was generated when importing data with dates older than January 1, 1900. Dates older than this are now converted to text, as to prevent the COM exception. (Bug #20340588, Bug #75450)

For Excel 2007, only .xls files were available in the Save As dialog. Now, all formats supported by Excel 2007 are available. (Bug #20296618, Bug #75389)

Executing Export Data to a New Table with the Preview SQL statements before they are sent to the server option enabled would report an incorrect (off by -1) number of affected rows under the Review SQL Script dialog. (Bug #20286897, Bug #75342)

During Data Export, if the number of rows to be exported was higher than the number of previewed rows, the export operation was restricted to the number of previewed rows.

A workaround was to increase the number of previewed rows to the number of rows being exported. (Bug #20077608, Bug #74942)

Connection information entries could not be deleted. (Bug #19789907, Bug #74304)

During an Edit Data session, and after data was added to a new row (and the row turned blue to indicate uncommitted changes), copying a value from a cell that lacked a status color (not modified) and pasting it into the new blue row did not retain the blue color. (Bug #19783737, Bug #74285)

The Import Data, Append Data and Edit Data action labels were not disabled after a DB Object was deselected from the list. (Bug #18323840)

Excel cells selected before MySQL for Excel was launched were not recognized, which caused the Export Data action label to remain disabled unless cells were selected again after MySQL for Excel was opened. (Bug #18323840)

When performing an Export Data operation, and while overriding the data type for a column that contained ENUM or SET values, MySQL for Excel validates the data type entered in the data type combo box. If a value within the SET or ENUM did not have a corresponding left or right single quote to wrap the value, the Export Data dialog did not generate a warning for the invalid data type. (Bug #18298155)

After executing an Export Data operation, a false warning of "Data in the current column is not unique" was generated when the Unique Index checkbox was checked on a column that only contained the column name but no other data.

Before, MySQL for Excel used the ADO.NET method of determining if the data in a DataColumn was unique (by creating a Unique constraint against it), which used Microsoft SQL Server's rules and regarded null values as duplicates even when the column was set to allow null data. MySQL allows duplicate null values in a column that is set to allow null data.

Now, MySQL for Excel uses the MySQL rules, so if a column is set to allow null data, those values are not considered in the uniqueness check, otherwise they are. If duplicate values are found when flagging a column as Unique, a dialog containing the sets of duplicate values along with the count of those sets can be displayed by clicking the More Information link shown within the column warning. (Bug #18270644)

The name of the automatically added Primary Key was changed when a column name was changed. (Bug #18270044)

Executing Export Excel Data to New Table after editing the column names of imported data would incorrectly emit a warning about repeated column names. (Bug #18270044)

Changes in MySQL for Excel 1.3.3 (2014-10-27, General Availability)

This section documents all changes and bug fixes applied to MySQL for Excel since the release of 1.3.2. Several new features were added the 1.3.x branch, for more information see What Is New In MySQL for Excel 1.3.

Known limitation:

Upgrading from versions MySQL for Excel 1.3.2 and lower is not possible due to a bug fixed in MySQL for Excel 1.3.3. In that scenario, the old version (MySQL for Excel 1.3.2 or lower) must be uninstalled first. Upgrading from version 1.3.3 works correctly.

Bugs Fixed

The MySQL for Excel MSI was not replacing the registry keys on an upgrade, in that registry keys from previous versions remained and were not upgraded. (Bug #19783949, Bug #74286)

Using semicolons (';') in values like schema names, column names or text values caused SQL queries sent to the MySQL server to fail. Internally, MySQL for Excel treated the semicolon as a separator for SQL statements. (Bug #19680607, Bug #74057)

Committing 20+ cell changes and new rows at the same time would fail to commit. (Bug #19639669, Bug #73911)

The "Preview SQL statements before they are sent to the server" option is now overridden when the "Auto-Commit" checkbox in the Edit Data dialog is checked. Before, each edit (that was auto committed) would first show the preview dialog. (Bug #19607260, Bug #73900)

The Export Data dialog's preview grid would display time data as a standard decimal numbers.

Also, exported data with time values were not properly wrapped in single quotes. (Bug #19607195, Bug #73899)

Importing a table with a row count that exceeded the number of rows below the cursor would generate a fatal "High severity error" and fail to import the data. Now, the import succeeds but the "Import will be truncated since it exceeds the available worksheet space." (Bug #19588933, Bug #73866)

When selecting a non-primary column that only contains integer values, the "Create Index" option is automatically checked, and the "Allow Empty" option is unchecked. This is the expected behavior with the advanced "Automatically check the Allow Empty checkbox for columns without an index" option enabled. (Bug #19503820, Bug #73719)

For consistency, all references to "Varchar" were changed to "VarChar". (Bug #19501346, Bug #73712)

The Allow Empty checkbox only had an effect the first time the SQL query was previewed. (Bug #19467535, Bug #73646)

Changed the way NULL and zero dates are handled. Previously, MySQL zero dates ("0000-00-00 00:00:00") were imported into Excel as the minimum valid date allowed by .NET (DateTime.MinValue), which was then converted into a text representation where the cell's value was no longer recognized as a date. Now, zero dates are always treated as NULL. (Bug #19423952, Bug #73541)

Exporting data that used a comma as the decimal separator would fail to export. The commas are now converted to periods, as already done when appending data. (Bug #19403063, Bug #73293)

When the number of mapped columns was less than the number of columns in the target table, and when the last MySQL column contained NULL values, append operations would insert NULL values for all fields in the aforementioned last column instead of inserting the values defined in Excel. (Bug #19402572, Bug #73175)

Values returned from Excel formulas were not recognized by MySQL for Excel when used in Export or Append Data operations. The Export/Append Data preview grids showed empty or unexpected numeric values (such as -2146826265) instead of the actual value returned by the formulas. (Bug #19389936, Bug #73505)

Appended DATETIME fields would change to 000-00-00 00:00:00 if the table also had an auto-increment field present. (Bug #19389609, Bug #73468)

DATETIME columns were not automatically mapped when an Append Data action was executed. (Bug #19191183, Bug #73268)

TIME values are now converted to Excel's time values to avoid type related errors when importing a range of data to or from Excel. (Bug #18693067, Bug #72504)

Rows involved in a commit action during Edit Data operations are now refreshed from the database after the transaction is committed, so values that are modified at the server side (auto increment fields, timestamps, or others by stored procedures), are returned to Excel after the push. This avoids optimistic update warnings stating that the data was changed outside of the Edit Data session. (Bug #18142293)

When renaming or deleting a stored mapping from the Append Data's Advanced Options dialog, clicking Cancel would not undo the rename or delete action. (Bug #16501859)

Changes in MySQL for Excel 1.3.2 (2014-09-22, General Availability)

This section documents all changes and bug fixes applied to MySQL for Excel since the release of 1.3.1. Several new features were added the 1.3.x branch, for more information see What Is New In MySQL for Excel 1.3.

Known limitation:

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.

Functionality Added or Changed

Bugs Fixed

Functionality Added or Changed

Excel tables created from stored procedures can now be refreshed. (Bug #19129583, Bug #73151)

Changed the way stored procedure result sets are laid out in a Excel worksheet when all of them are imported horizontally or vertically, and when PivotTables are created for each result set. Instead of skipping one row or column, the necessary rows and columns are skipped so the created PivotTables for the result sets do not collide.

The Schema Selection panel now includes collation information for the listed schemas that can be shown by right-clicking the Schemas list and choosing Display Schema Collations from the context menu.

When importing multiple database objects, the ability to add related tables to the directly related tables (i.e. indirectly related tables) was added by right-clicking a table in the related tables list (at the right side of the dialog) and choosing Add Related Tables from the context menu.

The generated summary row added by the Add Summary Fields option when importing MySQL data is now bold and includes a thick border, as to differentiate from actual data.

A single PivotTable can now be created for the entire Excel data model when importing multiple MySQL tables, which allows analyzing the related Excel tables within a single PivotTable. The Excel data model contains all Excel tables at the time the single PivotTable is created, so if previous imports were already performed, the data model may show more tables than the imported ones in the last multiple import operation. The option to create a PivotTable for each imported table is still present, but single PivotTable creation is selected by default.

MySQL for Excel now handles the managed Fabric connection type that was introduced in MySQL Workbench 6.2. New icons were introduced for SSH and managed Fabric connections. Connections that are not of the type native, native_socket, or native_sshtun, will not be listed in the connections listing under the Welcome Panel.

A new global option called "Preview MySQL table data before an Edit Data session is opened" was added. When checked (default), the data of a selected MySQL table to be edited is shown in a preview dialog before the Edit Data session is opened. If the option is unchecked, no preview takes place and the Edit Data session is simply opened.

A new context menu option called "Preview Data" was also added, and it is available when right-clicking a MySQL table or view that is listed in the DB Objects selection panel. The option opens the Preview Data dialog and shows the first 10 (by default) rows of the selected table or view.

In previous versions, the Import Data dialog was always displayed when an Edit Data was started, the Preview Data dialog replaces it to avoid confusion about the type of operation being performed.

Several fields next to checkboxes were updated to automatically be focused and selected when the corresponding checkbox or radio button is checked.

Bugs Fixed

A pop-up warning message stated that some features could not be saved in a macro-free workbook would appear when closing a Workbook that was not saved.

Internationalization formulas used by MySQL for Excel that are stored in Workbook Names are now removed before the Workbook is saved, and these formulas are added again after the save operation. (Bug #19358961, Bug #73467)

Duplicate edit session connection information would be saved to the settings.config file, which generated a "Editing not possible" error message after using the "Work Offline" option.

Closing an unsaved workbook now opens an Excel "Save As" dialog. (Bug #19347634)

The Append Excel Data to Table operation failed when the number of columns did not match, even when the data was manually mapped. (Bug #19346203, Bug #73453)

In the Import Multiple dialog, Excel relationships were created on import when the "Create Excel relationships for imported tables" was unchecked. (Bug #19299550, Bug #73402)

Two labels were changed: the context menu option "Import Selected and Related DB Objects" changed to "Import Selected and Related Tables", and "Selected related Tables and Views" changed to "Selected related Tables". This is because these options only apply to tables. (Bug #19296989, Bug #73398)

Entries for invalid connections from import sessions were saved in the %APPDATA%\Oracle\MySQL for Excel\settings.config file even when the workbook was not saved. (Bug #19242130, Bug #73319)

The Append Data action incorrectly became unavailable when changing database object nodes.

A workaround was to reselect the Excel data to re-enable Append Data. (Bug #19190638, Bug #73267)

Sometimes MySQL styles were missing from the data list. (Bug #19189185, Bug #73263)

The table schema initialization procedure was fixed to only import the selected columns into Excel, instead of always importing all of them. (Bug #19181877, Bug #73247)

When importing multiple database objects, related tables and views were only detected when the originally selected database object (shown at the left side of the dialog) had a MySQL Foreign Key explicitly declared, but they were not detected if the selected database object was actually the foreign object. In other words, only a 1-directional relationship was detected. (Bug #19154006, Bug #73193)

Reconnection information stored in the %APPDATA%\Oracle\MySQL for Excel\settings.config configuration file to reconnect Excel tables with their corresponding MySQL database objects counterparts was being written to disk even when the workbook save operation was cancelled. (Bug #19153978, Bug #73192)

Excel relationships were not created for the relationships among selected database objects when a multiple import was performed. Only relationships among database objects in the original selection were successfully created, while those from the original selection were not. (Bug #19153946, Bug #73191)

On Windows 7 (x64) with Excel 2007, MySQL for Excel did not save connection information for edit sessions or data imports. (Bug #19145707, Bug #73182)

Either checking the "Create Pivot Table..." box and/or selecting vertical or horizontal import options with stored procedures failed with the following error: "An external data table can be resized only to include or exclude rows of data. The column boundaries cannot be changed." (Bug #19129609, Bug #73152)

The Import MySQL Data feature failed to import stored procedures. (Bug #19129583, Bug #73151)

The "Add Summary Fields" checkbox in the Import Table dialog would be enabled even though the required "Create an Excel table for the imported MySQL table data" option was disabled. (Bug #18979388, Bug #73004)

The "Create an Excel table for the imported MySQL table data" advanced option in the Import Data dialog was renamed to "Create an Excel table for the imported MySQL data", because it also imports non-tables such as views and procedures. (Bug #18979352, Bug #73003)

Text for the Restore Saved Edit Sessions and Reconnect Import Sessions dialogs was updated to be more descriptive.

All "Edit Session" references were renamed to "Edit Connection", and all "Import Session" references were renamed to "Import Connection".

When creating Excel tables for imported data, MySQL for Excel created two Excel Workbook connections instead of one.

Changes in MySQL for Excel 1.3.1 (2014-07-01, Release Candidate)

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.

Known limitations:

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.

Functionality Added or Changed

Bugs Fixed

Functionality Added or Changed

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)

Bugs Fixed

Data could not be imported from a remote MySQL server. (Bug #19012634, Bug #73040)

The Edit Connection dialog 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 Refresh All from the Data tab would fail to refresh the data, and it generated an "Initialization of the data source failed" error. (Bug #18962538, Bug #72974)

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 checkbox 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)

Line and LinearRing were 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.

Changes in MySQL for Excel 1.3.0 (2014-06-06, Beta)

This section documents all changes and bug fixes applied to MySQL for Excel since the release of 1.2.1. Several new features were added, for more information see What Is New In MySQL for Excel 1.3.

Known limitations:

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.

Control + A cannot be used to select all database objects. Either shift + Arrow or Control + click must be used instead.

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.

Functionality Added or Changed

Bugs Fixed

Functionality Added or Changed

A new collation option was added for the schema and table creation wizards. The default schema collation is "Server Default", and the default table collation is "Schema Default." Collation options may be selected from a drop-down list of all available collations.

A new Add Summary Fields for Numeric Columns option was added to the Import Data dialog that automatically adds summary fields for numeric data after the last row of the imported data. The specific summary function is selectable from many options, such as "Total" and "Average."

The option dialogs now include a Refresh To Defaults button that resets the dialog's options to their defaults values. Each option dialog is set individually.

A new Export Data, Advanced Options option was added that shows all available data types in the Data Type combo box, instead of only showing a subset of the most popular data types.

All options now have descriptive tooltips. Hovering over an option/preference displays helpful information about its use.

Multiple objects (tables and views) can now be imported into Excel, when before only one object could be selected. Relational information is also utilized when importing multiple objects.

Functionality was added to import data directly into PivotTables, which can be created from any Import operation.

Imported data can now be refreshed by using the native Refresh feature. Fields in the imported data sheet are then updated against the live MySQL database using the saved connection ID.

Bugs Fixed

MySQL for Excel would take a long time to load (minutes instead of minutes) when a large number of MySQL connections were present, such as 300. (Bug #17852222)

Changes in MySQL for Excel 1.2.1 (2014-03-26)

Known limitation / upgrade requirement:

You must uninstall all current versions of MySQL for Excel before performing this upgrade, due to a bug that prevented upgrading from previous versions. This applies to both the standalone and MySQL Installer installation methods, and the fix allows for simpler upgrades in the future. Your MySQL for Excel settings will be preserved.

Functionality Added or Changed

Bugs Fixed

Functionality Added or Changed

When MySQL Workbench is not installed, MySQL connections are now automatically created for discovered MySQL services. If MySQL Workbench is later installed, these connections are not migrated over to MySQL Workbench as MySQL Workbench also creates connections for discovered MySQL services. (Bug #16238788)

Bugs Fixed

With Microsoft Excel 2013, closing an Excel window containing an open MySQL for Excel add-in did not properly dispose of the link to the add-in, which caused a delay when opening the add-in inside additional Excel windows. (Bug #18392674)

Attempts to upgrade MySQL for Excel failed. The Installer would attempt to add Registry keys that were already present from a previous installation. A workaround was to uninstall and then reinstall the add-in.

This bug applies to the standalone and MySQL Installer installation methods, and to MySQL for Excel versions 1.1.3 and later. (Bug #18354533)

Executing Export Data while the first data column was not numeric would cause an "AutoPK" column (Automatically create a Primary Key) to be created as the first column in the table. This column was also created if the user manually selected the Add a Primary Key column radio button. The generated CREATE TABLE statement did not contain the AutoPK column. (Bug #18269654)

The Export Data operation failed when checking the Exclude Column checkbox for any column. The generated CREATE TABLE query did not show the excluded columns, but the generated INSERT statements did (incorrectly) include them. (Bug #18269602)

The Remove columns that contain no data, otherwise just flag them as "Excluded" option was removed from the Export Data Advanced Options preference panel. Now, the default behavior is to always remove empty columns from the calculations. (Bug #18113057)

A MySQL database with unique keys would sometimes fail to import, when executing Import MySQL Data. (Bug #17891357, Bug #71004)

The creation of named tables did not function in all cases during an import, and could generate an exception. (Bug #17806468, Bug #70925)

After creating a new stored mapping in the Append Data dialog, the default selection for the Stored Mapping drop-down list was a blank value. The new default is the newly created stored mapping. (Bug #17665496)

Exporting large table (250,000+ rows) would not function, as MySQL for Excel would disconnect from the MySQL Server before completion. The MySQL for Excel add-in was optimized to help with these use cases, and these changes include:

Optimized the way SQL statements are sent to the server. When compared to statements sent in version 1.2.0, a 30-35% time improvement was achieved.

Optimized the way SQL queries are created for a modified row, by processing the warnings returned by the MySQL server and the overall creation of result text for errors and warnings to optimize processing and reduce the memory usage. On average, a 30-40% time improvement was achieved.

Optimized how the Excel data is loaded into the MySqlDataTable object, so now a temporary (and hidden) Excel worksheet is used to prepare the data to be loaded, and then it is loaded after it was preprocessed instead of preprocessing cell-by-cell as it was done before. This preprocessing also eliminates many blank Excel cells. On average, an 80% time improvement was achieved.

Added an advanced option to the Export Data dialog to create secondary indexes after all of the data has been inserted. This saves disk I/O for bulk inserts (thousands of rows) since reindexing will not happen every time a row is inserted, but only once at the end of the data insertion. This option is enabled by default.

Added an advanced option to the Append Data dialog to temporarily disable unique indexes and foreign keys for the duration of the data insertion. This option is disabled by default, since you must make sure that if unique indexes are present, that the data mapped to that column does not contain duplicate data.

Added checks for lost or broken connections before each statement is executed against the database, and will now properly display connection issues back to the user.

The global option Wait XX seconds for a database query to execute before timing out is now setting the net_write_timeout and net_read_timeout accordingly. The default value for this option was increased from 30 to 60 seconds.

(Bug #17577014)

When performing an Export Data with the "Remove columns that contain no data, otherwise flag them as Excluded" advanced option disabled (unchecked), empty columns were not flagged as "Excluded" if the first row contained data, even when the first row contained header information. (Bug #16501338)

When mapping a source column to a target column that has a different data type, a visual warning is now displayed as a warning icon with associated text next to it, and the problematic grid column changes to red. (Bug #16238994)

On Windows XP, the table icons were cut off on the Database Objects list when tables were exported to an empty schema. (Bug #16238484)

When selecting all cells in a spreadsheet, MySQL for Excel attempted to compute if data was present in each cell. Due to the large number of cells, the Excel API component "VSTO" failed and return a Range.Count property related exception. This check now uses native Excel functions, which are optimized for speed less memory usage. (Bug #14362824, Bug #17349260)

Changes in MySQL for Excel 1.2.0 (2014-01-23)

This section documents all changes and bug fixes applied to MySQL for Excel since the release of 1.1.3. Several new features were added, for more information see What Is New In MySQL for Excel.

Functionality Added or Changed

Bugs Fixed

Functionality Added or Changed

Excel tables are now automatically created for any data imported from MySQL to an Excel worksheet, with a name like "Schema.DB-Object-name".

Edit Data sessions can now be saved.

The Advanced Options dialogs opened from the Import, Export, and Append Data windows now immediately apply the option changes.

The selected schema name is now displayed on top of the MySQL for Excel Database Object Selection panel.

The Data Export feature now has an option to only create a table without inserting the data.

Several new "Preview" preferences were added, when previewing import/export results, which includes options to show the MySQL statements.

Append Data now warns of incompatible types when mapping source Excel columns to target MySQL columns.

Optimistic Updates are now an option, when before only Pessimistic Updates were available. Optimistic updates are enabled by default, and this means that changes made from outside of Excel during a session (such as a field update) will not be overwritten by Excel, and instead a notification is generated with the option to force the change.

MySQL connections can now be edited from within the MySQL for Excel add-in by right-clicking and choosing Edit Connection.

A new orange color was added. A cell is colored orange when MySQL for Excel detects a change from an external source before a commit is attempted. This requires 'Optimistic Updates' to be enabled (default).

Bugs Fixed

After deleting an entire row in a worksheet, the row after it would change color to green. (Bug #17852774)

The meaning of the blue and green cell backgrounds were switched. A modified cell is now blue, whereas a modified and committed cell is now green.

Changes in MySQL for Excel 1.1.3 (2013-10-16)

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

Bugs Fixed

MySQL for Excel 1.1.2 could not be uninstalled via the Microsoft Windows "Add or Remove Programs" dialog.

MySQL for Excel 1.1.2 could only be reopened if it was closed using the toolbar icon. Closing it with the [x] icon would cause the add-in to stay hidden, until Microsoft Excel was restarted. This bug does not apply to Microsoft Excel 2013.

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

Bugs Fixed

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)

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)

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)

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 http://support.microsoft.com/kb/976477). (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.

Changes in MySQL for Excel 1.1.1 (2013-04-26)

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

Bugs Fixed

Even with the Remove columns that contain no data, otherwise flag them as Excluded option disabled, the data type for empty columns would become undefined. Blank columns are now defined as VARCHAR(255). (Bug #16495493)

Imported data would become corrupt if the Excel cell format was different than the format of the data being imported. The cell format is now reset before import. (Bug #16495155)

The Export data and Append data action buttons were visible when no data was present, but they are now hidden. (Bug #16495151)

Automatic mapping would not function in Edit or Append mode if only one row was selected. (Bug #16493139)

Refresh would not refresh MySQL for Excel with connection changes that were made in MySQL Workbench while MySQL for Excel was open. (Bug #16493129)

Attempting to Edit MySQL Data on a recently removed table in Edit Mode would generate an unhandled exception. It will now emit an error message similar to "Table x does not exist." (Bug #16487827)

The data type combo box would accept a type definition that included text after the closing parenthesis, such as "varchar(200)asad", which would generate an error when attempting to create the table. Entering an invalid type will now raise a warning message similar to "Entered Data Type is not a MySQL valid data type." (Bug #16486410)

The MySQL performance_schema database was listed under Schemas, which is reserved for user created databases, but it is now listed under System Schemas. (Bug #16473033)

While using the Export Data dialog, clicking on the First Row Contains Column Names checkbox repeatedly after excluding some columns would cause MySQL for Excel to freeze. (Bug #16419402)

Checking the Exclude Column checkbox from within the preview grid would always change the cursor focus to the first column. The current focus is now preserved. (Bug #16397637)

Adding a new MySQL Server connection would cause the connection list to flicker. (Bug #16392862)

The Import Table Data dialog for the Edit Data operations did not display a horizontal scrollbar on the preview grid. (Bug #16239011)

An About section was added to MySQL for Excel, which contains version and copyright information. (Bug #16238860)

The Remote Connections list is now expanded by default while MySQL for Excel is initialized, when before only the Local Connections listing was expanded. (Bug #16238782)

The context menu from right-clicking a preview grid in the Import Data form is now aware of its context. The Select All and Select None options will only be available where applicable. (Bug #16238663)

When using the Export Data dialog with Auto-Detection of data types enabled (default), the Create Index checkbox is now checked by default when the data type is an detected as an integer. (Bug #16238445)

On systems that define number format using European regional settings, MySQL for Excel failed on INSERT because it would attempt to split these into two numbers at the comma. As a result, the query failed with an error such as "Column count doesn't match value count." These commas are now converted to periods. (Bug #15903921)

Changes in MySQL for Excel 1.1.0 (2012-09-30)

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

This adds the Edit MySQL Data feature.

Functionality Added or Changed

Bugs Fixed

Functionality Added or Changed

The Installer will now check if MySQL for Excel is already installed. It will abort if a newer version of MySQL for Excel is already installed, or uninstall an older version of MySQL for Excel.

Added a new Export Data advanced option: "Remove columns that contain no data, otherwise just flag them as 'Excluded'."

Added two new Append Data advanced options: "Automatically store the column mapping for the given table" and "Reload stored column mapping for the selected table automatically".

Added the Edit MySQL Data feature. MySQL data can now be edited directly from the MySQL server in Microsoft Excel.

Bugs Fixed

On Microsoft Windows 7, MySQL for Excel would not load when the "Display settings" configuration setting was set to Adjust to Best Performance. (Bug #14521405)

It was difficult to determine which operations succeeded and failed due to how the optimistic locking strategy was implemented. Transactions are now used that will revert the entire operation if an error occurs. (Bug #14356054)

It was possible for the query confirmation window to differ from the general query log. The two are now synchronized and identical. (Bug #14355970)

The Revert Data, Refresh Data from DB sequence would not clear colored cells of data that was already committed. Only cells with data that was not committed would be altered. (Bug #14350321)

When Auto-Commit is enabled, an information dialogue will now notify the user if a commit generates warnings and/or errors. (Bug #14349284)

Stopping the connected MySQL Server while in edit mode would generate an error upon commit, but it would also display a success message along with displaying a bogus query. It will now only show a proper error message. (Bug #14349256)

The Revert/Commit window would remain on top of all other windows. It will now only be shown on top of MySQL for Excel windows. (Bug #14349218)

A commit could return a success message if a commit failed while editing a primary key. (Bug #14349192)

The Show Details button now toggles and reads as Hide Details after it is pressed, and while the details panel is open.

A change after the Append Data automatic mapping is performed will now reset the mapping status to "manual mapping."

Connections are now refreshed after they are migrated from MySQL for Excel to MySQL Workbench.

The Import Data preview grid did not refresh after pressing Call to execute a routine.

Append Data would emit the error "Index was outside the bounds of the array" and not function if a "Stored Column Mapping" contained unmapped columns.

Changes in MySQL for Excel 1.0.7 (2012-08-10)

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

Bugs Fixed

The Export button is now disabled if the table name is empty. (Bug #14389853)

Auto mapping did not function properly while appending to "enum" or "set" data types.

Also, while toggling the First Row Contains Column Names configuration option, the column names would update on the Source grid but not on the mapped headers of the Target grid. (Bug #14370049)

Controls would overlap when resizing the MySQL for Excel window to a small size (to a height of less than 500px).

And the Excel window could not be resized if Excel with MySQL for Excel enabled would open with a small window size. (Bug #14369568, Bug #14406412)

Connections created from within MySQL for Excel were not usable by MySQL Workbench. They are now usable by MySQL Workbench 5.2.42 and above. (Bug #14368158)

Clicking Manage Connections would throw an exception. (Bug #14367145)

The Export Data dialogue's preview grid would truncate a column name if it was altered after the initial load. (Bug #14350168)

Changes in MySQL for Excel 1.0.6 (2012-07-25)

Initial public release of MySQL for Excel.

Bugs Fixed

The Append Excel Data to Table tool would generate an error, and not function. (Bug #14369777)

It was not possible to create a New Connection unless MySQL Workbench was installed. (Bug #14368155)

Added support for SSL connections that were created in MySQL Workbench. And if a connection using SSL is detected but will not connect, then an a warning dialog is now displayed within the Show Details section. And the add-in will attempt to connect without using the SSL parameters. (Bug #14368116)

The {AppData}/Oracle/MySQL For Excel/ directory is now created when Microsoft Excel is first opened with the MySQL for Excel add-in enabled. (Bug #14366579)

Schema and database objects had their names grayed out, which made them appear disabled. (Bug #14366416)

Toggling the First Row Contains Column Names option after changing a primary key column name from the auto-suggested value would revert the name change back to the initial auto-suggested value. (Bug #14366393)

Exporting and appending data would generate a single INSERT statement under all conditions. Large queries would result in max_allowed_packet related errors, and fail to execute the query. Multiple INSERT queries are now generated. (Bug #14362783)

The Export Data and Append Data preview panels can now be configured to limit the number of rows for preview. Before it would display all rows, which would stall MySQL for Excel when large data sets are being exported. The default value is 100 rows. (Bug #14362781, Bug #14366469, Bug #14362780)

The MySQL Installer for Windows would not upgrade the MySQL for Excel add-in. A workaround was to uninstall it manually beforehand. (Bug #14357305)

The MySQL Notifier version is now displayed within the Microsoft Windows Add/Remove programs listing. (Bug #14357291)

Incorrect service information could be displayed in the new connection dialog while using Test connection. It's now automatically refreshed. (Bug #14356149)

Stored procedure results containing many rows (10,000+) would cause the input form to hang while attempting to change result sets. Also, a warning is now displayed when the number of imported rows exceeds the Excel limit (65,535) that explains why the data will be truncated. (Bug #14351468, Bug #14368490)

Windows Authentication plugin support was added. (Bug #14351296)

It was not possible to re-enter an incorrectly entered password. (Bug #14350983)

Uninstalling the MySQL for Excel add-in would cause Microsoft Excel to generate an error titled "Installing Office customization." (Bug #14350751)

The Append Excel Data to Table option would not function nor warn the user if the primary key could not be mapped. (Bug #14350536)

The defined Advanced Options were not used when opening a new connection. (Bug #14350361)

Altering a column in the Export Data grid would refresh the Use existing column configuration option even though the column properties did not change. (Bug #14350299)

Changing the column on the combo box next to the Use existing column radio button in the Export Data dialog would not set the focus to the column in the grid, nor refresh the column property controls. (Bug #14350288)

While using the Export Excel Data to New Table wizard, toggling the First Row Contains Names checkbox would reset and disable the Use Existing Column configuration option. (Bug #14350275)

Changes in MySQL for Excel 1.0.5 (Not released)

Developmental release of MySQL for Excel.

Bugs Fixed

Strings that are too long to fit in a window are now truncated with an ellipses, and a tooltip now exists to show the full text. (Bug #14350205)

The date data types were not being imported/exported. They are now imported, and treated as follows:

For importing data: NULL is imported as a "blank" cell. Zero date values are imported as DateTime.MinValue (which displays as "12:00:00 am" in Excel) to prevent losing the Date formatting in Excel

For exporting/appending data: blank cells, "0000-00-00 00:00:00", "000-00-00", and "00-00-00" are exported as NULL if the DATETIME column allows NULL, otherwise a zero date is inserted into the column. (Bug #14350058)

Imported data would not report warnings, such as operations that truncated or converted data. Warnings are now shown for the Export, Append, and Edit operations if executing them were successful, but with warnings. (Bug #14349507)

The following operations now generate errors if the connection is lost before execution:

Selecting, refreshing, or filtering a schema

Refreshing and filtering database objects

Appending data

Importing data from a table, stored procedure, or view

(Bug #14349309)

Changes in MySQL for Excel 1.0.4 (Not released)

Developmental release of MySQL for Excel.

Bugs Fixed

Errors were not being logged. The following log file now exists: {AppData}/Oracle/MySQL For Excel/MySQLForExcel.log (Bug #14351349)

While testing a MySQL Server connection, the user would sometimes not be prompted for a password, and instead it would use the previously set user/pass combination. (Bug #14351001)

The connection details in the Connection Password window did not correctly display the information, as some field were either empty or missing. (Bug #14350974)

User settings were being saved in the Microsoft Office folder instead of the MySQL for Excel folder. They are now saved here: {AppData}/Roaming/Oracle/MySQL For Excel/settings.config (Bug #14350837)

Editing a table would not release the table (for editing elsewhere) even after the table worksheet was deleted. Now, it is released when either the table worksheet is deleted, or the user explicitly exits edit mode. (Bug #14350827)

Deleting rows would not be detected while editing a table, thus causing the Commit button to be disabled. (Bug #14350817)

Mapping a column from the "Source Table" to several columns in the "Target Table" in the Append Data dialog would prompt to replace existing mapping when there was nothing to replace in the "Target Table."

Also, when choosing to overwrite the existing mapping, only the last column was mapped. (Bug #14350802)

The Export Excel Data data type drop down is now disabled when the field is a primary key, because it should not change from being an INTEGER. (Bug #14350795)

The Edit MySQL Data function would not generate full reports. For example, editing a particular row would generate a query log with a missing WHERE clause. (Bug #14350780)

Exporting Excel data to a new table to a schema with a ' (single quote) in the schema name would create the table but the data would not be exported. (Bug #14350765)

A dialog now exists that notifies the user that connections created from within MySQL for Excel are not saved if MySQL Workbench is also open. (Bug #14350739)

Revert Data, Refresh from DB would refresh and display all columns instead of the limited ones. (Bug #14350582)

The Edit MySQL Data option would edit the incorrect row. (Bug #14350550)

It was not possible to delete a MySQL Server connection. (Bug #14350516)

The Information Dialog window that is displayed after confirming an operation against MySQL (append, edit, or export) was not resizable. It can now be resized after the Show Details button is clicked. (Bug #14350330)

Text could be truncated when doing so was not required. (Bug #14350220)

Schemas and objects can now be refreshed by right-clicking and selecting the Refresh option. (Bug #14349606)

Adding a new table via the MySQL for Excel add-in would corrupt the table listing. (Bug #14349362)

Changes in MySQL for Excel 1.0.3 (Not released)

Developmental release of MySQL for Excel.

Bugs Fixed

The SSH Connection option was removed because Connector/NET does not support SSH. (Bug #14350996)