Dear MySQL users,

The MySQL Windows Experience Team is proud to announce the
release of MySQL for Excel version 1.3.7. This is a maintenance
release for 1.3.x. It can be used for production environments.

MySQL for Excel is an application plug-in enabling data analysts
to very easily access and manipulate MySQL data within Microsoft
Excel. It enables you to directly work with a MySQL database from
within Microsoft Excel so you can easily do tasks such as:

  * Importing MySQL Data into Excel

  * Exporting Excel data directly into MySQL to a new or existing table

  * Editing MySQL data directly within Excel

MySQL for Excel is installed using the MySQL Installer for Windows.

The MySQL Installer comes in 2 versions

- Full which includes a complete set of MySQL products with
  their binaries included in the download.

- Web (network install) which will just pull the MySQL for
  Excel over the web and install it when run.

You can download MySQL Installer from our official Downloads page at

The MySQL for Excel product can also be downloaded by using the product
standalone installer found at this link

Changes in MySQL for Excel 1.3.7 (2017-05-24)

   Functionality Added or Changed

     * The way MySQL for Excel shares data-editing sessions
       among users and between computers was improved. (Bug
       #25509085, Bug #73314)

     * The Append Excel Data to Table operation was updated with
       new advanced options to manage the behavior of rows
       containing unique key values that are duplicates of those
       in the database. (Bug #25479653, Bug #83801)

     * Added a new global option that specifies how to format
       spatial data as text: Well-Known Text, Keyhole Markup
       Language, Geography Markup Language, or GeoJSON. (Bug

     * Enhanced the logic that migrates stored MySQL connections
       to the MySQL Workbench connections.xml file. In previous
       versions, the migration was offered and if not done at
       that moment, the dialog to migrate was shown every time
       MySQL for Excel was launched. There was no way to choose
       to continue storing MySQL connections in the MySQL for
       Excel configuration folder, instead of merging them with
       MySQL Workbench.
       Now, the Connections Migration dialog offers a way to
       postpone the migration by one hour, one day, one week,
       one month, or indefinitely. If the migration is
       postponed, the dialog is shown again after that time
       elapses. If the migration is postponed indefinitely, then
       an option is added to the Options dialog that permits the
       migration of connections to be done manually, as long as
       MySQL Workbench is installed.

     * Support for MySQL Fabric was removed.

   Bugs Fixed

     * SSL connections when created with MySQL Workbench should
       be inactive within MySQL for Excel, which does not
       support SSL connections. (Bug #25962564)

     * Selecting a schema containing at least one stored
       procedure for a MySQL 8.0 or 8.1 connection emitted an
       error. (Bug #25962347)

     * Empty string values within Excel column data that were
       used in an export or append-data operation caused the
       generated SQL queries to have no value, instead of an
       empty value corresponding to the data type of the target
       column (for example: 0 for Integer; false for Bool if the
       column does not allow NULL values, or NULL otherwise).
       (Bug #25509312, Bug #84851)

     * MySQL data could not be refreshed or edited directly in
       an Excel worksheet by different users or from different
       computers, which reduced the ability to share
       data-editing sessions among users or between computers.
       This fix alters the way connection information is stored
       by migrating the connection details for related import
       and edit-data operations from the user settings file to
       the XML parts of a workbook when the workbook is opened,
       and if the workbook supports XML parts and the connection
       information related to that workbook is found in the user
       settings file. (Bug #25509085, Bug #73314)

     * User-selected data types that replaced the detected
       values of a column were lost when the First Row Contains
       Column Names check box was selected or deselected in
       preparation for an export-data operation. This fix
       retains the selected value when the data type is set
       manually to override the automatically detected type and
       the check box is selected or deselected. It further adds
       a new action to reset the column back to automatic
       detection. (Bug #25492772, Bug #84802)

     * A portion of the preview area that should be displayed
       during import, export, and append data operations was
       concealed by other fields. (Bug #25325457)

     * Attempting to refresh MySQL data in an Excel worksheet
       while the MySQL for Excel task pane was closed generated
       an error. (Bug #25301136)

     * Edit-data operations in which the SQL query used
       optimistic updates, and the data contained empty strings,
       produced errors during the commit to MySQL. Enhanced
       mapping of character sets and clearer error-message text
       were added to identify the use of client character sets
       that are unsupported in MySQL. (Bug #25236221, Bug

     * A mismatch between the current schema and the current
       connection caused the refresh action to fail when a
       worksheet with imported data was created as an Excel
       table, saved, closed, and then reopened. (Bug #25233309)

     * Inactive connections and unsaved passwords caused the
       refresh action to generate errors for worksheets with
       imported MySQL data in Excel tables. (Bug #25227226)

     * Excel worksheets that had currency values with comma
       separators produced errors when the data was exported to
       a MySQL table. (Bug #25214984, Bug #84049)

     * MySQL connection passwords were not saved to the secure
       password vault and produced a password request every time
       an existing connection was opened. (Bug #25108196)

     * Excel cells containing empty strings, which are not
       actually blank, generated errors with export, append, or
       edit data operations. With this fix, an empty string is
       now equivalent to a blank cell. (Bug #24431935, Bug

     * Although the Refresh All action in the Data ribbon
       refreshed all MySQL connections, it did not refresh the
       other connections associated with a workbook when the
       MySQL for Excel add-in was enabled. (Bug #23605635, Bug

     * Clearing numeric parameter values within a stored
       procedure, or setting any of the initial values to NULL,
       during an Import MySQL Data operation emitted an error.
       (Bug #23281495, Bug #81417)

     * Type TinyInt was mapped as type Bool when data was
       imported to Excel from MySQL. (Bug #23022665, Bug #80880)

     * MySQL columns of type DATE and DATETIME produced errors
       during import-data operations. This fix improves the way
       MySQL for Excel handles these types for all operations:
       import data, export data, append data, and edit data.
       (Bug #22627266, Bug #80139)

     * Excel data of type Date could not be exported to a MySQL
       table. (Bug #22585674, Bug #80079)

     * Tables and views imported to Excel without the Include
       Column Names as Headers option first being selected
       omitted the expected default column names (Column1,
       Column2, and so on). (Bug #22373140)

     * Creating a new schema with the binary - binary collation
       produced an error. (Bug #22371690)

     * Saved edit-data sessions could not be restored after a
       workbook was closed and then reopened. (Bug #22138958)

     * Connection sharing between MySQL for Excel and MySQL
       Workbench resulted in some incorrect connection
       information being passed to the MySQL Server Connection
       dialog. (Bug #22079779)

     * The default schema of the current MySQL connection
       changed unexpectedly when a table in a different schema
       was edited. (Bug #22074426)

     * With a cursor positioned at the bottom of a worksheet and
       with the Add Summary Fields check box selected, the
       import-data operation failed despite having enough space
       to fill the cells. (Bug #19652840)

Quick links:
MySQL for Excel documentation:
Inside MySQL blog (NEW blog home):
MySQL on Windows blog (OLD blog home):
MySQL for Excel forum:
MySQL YouTube channel:

Enjoy and thanks for the support!
The MySQL on Windows team at Oracle.

MySQL General Mailing List
For list archives:
To unsubscribe:

Reply via email to