Dear MySQL users,

The MySQL Windows Experience Team is proud to announce the release of
MySQL for Excel version 1.3.1. This is a RC release for 1.3.x.

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


As this is a RC version the MySQL for Excel product can be
downloaded only by using the product standalone installer at this link
http://dev.mysql.com/downloads/windows/excel/


Changes in MySQL for Excel 1.3.1 (Not yet released, RC)

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
(http://dev.mysql.com/doc/refman/5.6/en/mysql-for-excel-what-is-new.html).

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

* 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 would fail 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 would fail with
an "Input string was not in a correct format." error. (Bug
#18728748, Bug #72434)
References: See also Bug #18962214, Bug #72970.

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.

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql