MySQL for Excel 1.3.5 has been released (no replies)

Dear MySQL users,

The MySQL Windows Experience Team is proud to announce the release of
MySQL for Excel version 1.3.5. 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 (150 MB) which includes a complete set of MySQL products with
  their binaries included in the download.

- Web (1.5 MB - a 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
http://dev.mysql.com/downloads/installer/

The MySQL for Excel product can also be downloaded by using the product
standalone installer found at this link
http://dev.mysql.com/downloads/windows/excel/


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

   Functionality Added or Changed

     * 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.

     * Added a new advanced option to 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.

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

   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)

     * 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
       Workbench is saved, thereby saving the new connection
       information. (Bug #21172751, Bug #21089790, Bug #76475,
       Bug #73467)

     * 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 plugin 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)


Quick links:
You can access the MySQL for Excel documentation at http://dev.mysql.com/doc/en/mysql-for-excel.html.
You can find our team's blog at http://blogs.oracle.com/MySQLOnWindows.
You can also post questions on our MySQL for Excel forum found at http://forums.mysql.com/list.php?172.
You can follow our videos on our YouTube channel found at http://www.youtube.com/user/MySQLChannel.


Enjoy and thanks for the support!

The MySQL on Windows team at Oracle.