List:Announcements« Previous MessageNext Message »
From:Javier Treviño Date:March 27 2014 5:48pm
Subject:MySQL for Excel 1.2.1 has been released
View as plain text  
The MySQL Windows Experience Team is proud to announce the release of MySQL for Excel
version 1.2.1.  This is a maintenance release for 1.2.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

 

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 for Excel 1.2.1 from our official Downloads page at
http://dev.mysql.com/downloads/windows/excel as a standalone MSI, and it will be
available shortly in the MySQL Installer for Windows that can be downloaded from
http://dev.mysql.com/downloads/installer/.


MySQL for Excel 1.2.1 introduces the following features:

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

o   Bug #16238788 - CONNECTIONS FOR FOUND MYSQL SERVICES SHOULD BE AUTOMATICALLY
CREATED

 

Known limitation / requirement:

·         You must uninstall any current
installation of MySQL for Excel before performing this upgrade, due to a bug that
prevented upgrades from previous versions. This applies to both the standalone MSI and
MySQL Installer installation methods, and the fix allows for simpler upgrades in the
future.

 

Also this release contains the following bug fixes:

·         With Microsoft Excel 2013,
closing an Excel window containing an open MySQL for Excel plugin did not properly
dispose of the link to the plugin, which caused a delay when opening the plugin inside
additional Excel windows.

o   Bug #18392674 - SEVERAL CLICKS NEEDED ON THE MYSQL FOR EXCEL RIBBON BUTTON
TO START/CLOSE ADD-IN

·         Attempts to upgrade MySQL for
Excel would sometimes fail. 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 plugin

o   Bug #18354533 - MYSQL FOR EXCELL ADDIN 1.2.0 (STAND ALONE) IS NOT ABLE TO
UPDATE AN OLD VERSION

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

o   Bug #18269654 - EXPORT DATA - ERROR ON CHANGING PRIMARY KEY OPTIONS

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

o   Bug #18269602 - EXPORT DATA - EXCLUDING COLUMNS CAUSE THE EXPORT DATA TO
FAIL

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

o   Bug #18113057 - EXPORT DATA - UNHANDLED EXCEPTION WHEN SELECTING THE WHOLE
SPREADSHEEET'S DATA

·         A MySQL database with unique keys
would sometimes fail to import, when executing Import MySQL Data.

o   MySQL Bug #71004, Bug #17891357 - ONLY ONE TABLE FROM A DATABASE WON'T
IMPORT

·         The creation of named tables did
not function in all cases during an import, and could generate an exception.

o   MySQL Bug #70925, Bug #17806468 - IMPORTING TABLES WITH GUID TO EXCEL -
EXCEPTION

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

o   Bug #17665496 - APPEND DATA - NEW STORED MAPPING NOT APPLIED AFTER CREATION

·         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 plugin was optimized to help with these use cases,
and these changes include:

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

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

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

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

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

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

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

o   Bug #17577014 - EXPORTING HUGE TABLE (250,000 ROWS) NEVER FINISH (SERVER
LOST THE CONNECTION)

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

o   Bug #16501338 - EXPORT DATA - EMPTY COLUMNS ARE NOT ALWAYS FLAGGED AS
EXCLUDED

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

o   Bug #16238994 - APPEND DATA - DISPLAY WARNINGS ON MAPPED COLUMNS WHERE
DATATYPE DOESN'T MATCH

·         The table icons were cut off on
the Database Objects list when tables were exported to an empty schema on Windows XP
environments.

o   Bug #16238484 - TABLE ICON IS CUTOFF ON THE TABLE LIST WHEN TABLE IS
EXPORTED TO AN EMPTY SCHEMA

·         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" would fail and return a
Range.Count property related exception. This check now uses native Excel functions, which
are optimized for speed less memory usage.

o   Bug #14362824 - SELECTING A HUGE AMOUNT OF CELLS IN EXCEL FREEZES EXCEL 

o   Bug #17349260 - ERROR WHEN SELECTING THE WHOLE SPREADSHEET'S CELLS

 

 

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.

Thread
MySQL for Excel 1.2.1 has been releasedJavier Treviño27 Mar 2014