MySQLforExcel1.3.1RChasbeenreleased The MySQL Windows Experience Team is proud to announce the release
MySQL for ExcelVersion 1.3.1. This is a RC release for 1.3.x.
MySQL for ExcelIs an application plug-in enabling data analysts to very easily access and manipulateMySQLDataMicrosoft Excel. It enables you to directly work withMySQLDatabase fromMicrosoft ExcelSo you can easily do tasks such:
- ImportingMySQLDataExcel
- ExportingExcelData directlyMySQLTo a new or existing table
- EditingMySQLData directlyExcel
As this is a Release Candidate versionMySQL for ExcelProduct can be downloaded only by using the product standalone installer at this link:
Http://dev.mysql.com/downloads/windows/excel/
Changes inMySQL for Excel1.3.1 (2014-07-02, Release Candidate)
This section documents all changes and bug fixes appliedMySQL for ExcelSince the release of 1.3.0. Several new features were added the 1.3.x branch, for more information seeWhat Is New In MySQL for Excel.
Known limitations:
- Upgrading from versionsMySQL for Excel1.2.0 and lower is not possible due to a bug fixed inMySQL for Excel1.2.1. In that scenario, the old version (MySQL for Excel1.2.0 or lower) must be uninstalled first. Upgrading from version 1.2.1 works correctly.
- Specified ttables are normally placed to the right (skipping one column) of the imported data, they will not be created if there is another existingExcelObject at that position.
Functionality Added or Changed
- When reopening a saved Excel workbook that contains importedMySQLData,MySQL for ExcelAttempts to reconnectExcelTables with the correspondingMySQLDatabases where the importedMySQLData was imported from. IfMySQLConnections 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 timeExcelWorkbook is opened. (Bug #18961860, Bug #72966)
- + Now selects all tables and views in Database ObjectsSelection panel. (Bug #18961544, Bug #72963)
Bugs Fixed
- Data cocould not be imported from a remoteMySQLServer.
- Bug #19012634.
- Bug #73040.
- TheEdit ConnectionDialog was not populated with information from the selectedMySQLConnection.
- Bug #18968777.
- Bug #72990.
- InExcel2013, importing the same table twice in the sameExcelWorksheet failed after deletingExcelTable linked to in the first report.
- Bug #18962670.
- Bug #72976.
- Data cocould not be imported to the left of previusly imported data if the new data intersected with the existing import.
- Bug #18962617.
- Bug #72975.
- After importing data, clickingRefresh AllFromDataTab wocould 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 toMySQLServer when data was exported to a new table withFirst Row Contains Column NamesCheckbox deselected. The generated error was similar to "Error while inserting rows... MySQL Error 1062: Duplicate entry '1' for key 'primary '".
- Bug #18962470.
- Bug #72973.
- WithCreate a temporary Table with the imported dataOption enabled, Data Import failed to create a portable ttable for tables that contained a large data set.
- Bug #18962371.
- Bug #72972.
- When importing tables,Pick related Tables or ViewsFeature did not function in Excel 2007 or Excel 2010, but did in Excel 2013.
- Bug #18962354.
- Bug #72971.
- For new columns,Export DataDialog wocould 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 inExport DataDialog's data type combo box.
- Bug #18962184.
- Bug #72969.
- Hovering over elements inMySQLConnecting and object listing cocould cause the text of each item to be bold.
- Bug #18962130.
- Bug #72968.
- Imported data wocould not refresh if the table name was changed inExcelDuring the import. The table name is no longer used to verifyMySQLConnection.
- Bug #18961806.
- Bug #72964.
- Edit Sessions wowould fail to restore with sessions that contained tables with zero DATETIME values. Edit Sessions wowould also fail to restore whenMySQL for ExcelWas started on a currently opened Excel workbook.
- Bug #18889495.
- Bug #72842.
- Attempting to import a table with ENUM values wowould fail with an "Input string was not in a correct format." error.
- Bug #18728748.
- Bug #72434.
- Bug #18962214.
- Bug #72970.
Quick links:
- You can access the MySQL for Excel documentation athttp: // dev.mysql.com/doc/en/mysql-for-excel.html.
- You can find our team's blog athttp: // blogs.oracle.com/MySQLOnWindows.
- You can also post questions on our MySQL for Excel forum found athttp: // forums.mysql.com/list.php? 172.
- You can follow our videos on our YouTube channel found athttp: // www.youtube.com/user/MySQLChannel.
Enjoy and thanks for the support!
