MySQL for Excel 1.3.4 has been released

[Karen Langford]

Dear MySQL users,

The MySQL Windows Experience Team is proud to announce the release of
MySQL for Excel version 1.3.4. 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.4 (2015-03-06)

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

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.