MySQL for Visual Studio – Uninstall workaround

In MySQL for Visual Studio version 1.2.4 and earlier, there was an issue, existing only under a specific scenario, which was preventing the plugin to be uninstalled (either using the “Remove” option in the Windows Control Panel/Programs, or the MySQL Installer for Windows) or upgraded to a newer version, causing the uninstall/update action to be rolled back during the process. (For further information about this issue please refer to http://bugs.mysql.com/bug.php?id=71226).

Such scenario can be achieved as follows:

  1. First install Visual Studio 2012, or VS 2013 or VS 2015
  2. Then, install MySQL for Visual Studio version 1.2.4 or earlier
  3. Later, uninstall Visual Studio 2012, or VS2013 or VS2015

With the scenario described above, the uninstall/upgrade process of the MySQL for Visual Studio plugin is aborted, leaving it installed on the computer.

It is important to mention that this issue was already fixed in MySQL for Visual Studio 1.2.5 or later, so we encourage you to download and install the latest version available. You can choose to upgrade via the MySQL Installer for Windows, or running the MySQL for Visual Studio standalone installer that you can download here: http://dev.mysql.com/downloads/windows/visualstudio.

Anyway, if you only want to uninstall the MySQL for Visual Studio plugin, and have the scenario described above, you can follow the next steps:

1. Manually create the missing registry values and files needed for the uninstall process of the MySQL for Visual Studio plugin:

a) Create (if not exists) the following registry hive:

* If you had VS 2012 when the MySQL for Visual Studio plugin was installed:

– For 32-bit OS:

HKLM:\Software\Microsoft\VisualStudio\11.0\Setup\VS

Having the key “EnvironmentDirectory” with the value “C:\Program Files\Microsoft Visual Studio 11.0\Common7\IDE\

– For 64-bit OS:

HKLM:\Software\Wow6432Node\Microsoft\VisualStudio\11.0\Setup\VS

Having the key “EnvironmentDirectory” with the value “C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\

vsRegistryPath_VS2012

(Figure 1: Registry key needed for Visual Studio 2012)

* If you had VS 2013 when the MySQL for Visual Studio plugin was installed:

– For 32-bit OS:

HKLM:\Software\Microsoft\VisualStudio\12.0

Having the key “ShellFolder” with the value “C:\Program Files\Microsoft Visual Studio 12.0\

– For 64-bit OS

HKLM:\Software\Wow6432Node\Microsoft\VisualStudio\12.0

Having the key “ShellFolder” with the value “C:\Program Files (x86)\Microsoft Visual Studio 12.0\

vsRegistryPath_VS2013

(Figure 2: Registry key needed for Visual Studio 2013)

* If you had VS 2015 when the MySQL for Visual Studio plugin was installed:

– For 32-bit OS:

HKLM:\Software\Microsoft\VisualStudio\14.0

Having the key “ShellFolder” with the value “C:\Program Files\Microsoft Visual Studio 14.0\

– For 64-bit OS

HKLM:\Software\Wow6432Node\Microsoft\VisualStudio\14.0

Having the key “ShellFolder” with the value “C:\Program Files (x86)\Microsoft Visual Studio 14.0\

vsRegistryPath_VS2015

(Figure 3: Registry key needed for Visual Studio 2015)

b) Create (if not exists) an empty file named “extensions.configurationchanged“, in the following path:

* If you had VS 2012 when the MySQL for Visual Studio plugin was installed:

– For 32-bit OS:

C:\Program Files\Microsoft Visual Studio 11.0\Common7\IDE\Extensions\

– For 64-bit OS

C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Extensions\

extensionsFilePath_VS2012

(Figure 4: File needed for Visual Studio 2012)

* If you had VS 2013 when the MySQL for Visual Studio plugin was installed:

– For 32-bit OS:

C:\Program Files\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\

– For 64-bit OS

C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\

extensionsFilePath_VS2013

(Figure 5: File needed for Visual Studio 2013)

* If you had VS 2015 when the MySQL for Visual Studio plugin was installed:

– For 32-bit OS:

C:\Program Files\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\

– For 64-bit OS

C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\

extensionsFilePath_VS2015

(Figure 6: File needed for Visual Studio 2015)

c) Proceed to uninstall the MySQL for Visual Studio plugin, using the “Remove” option in the Windows Control Panel/Programs, or executing the plugin installer (version 1.2.4 or earlier).

2. Create and execute two PowerShell scripts to automate the process mentioned in step 1, performing the next operations:

a) Using a text editor, create a new text file

b) Copy the following script into the file:

Note: This script is provided as a convenience to you as-is, without any express or implied warranties of any kind. Its intention is to automate the process of create the registry values and files needed by the MySQL for Visual Studio plugin uninstall process.  Oracle is not liable for any issues arising out of your use of the script.

c) Save the file as “M4VSUninstall_Validation.ps1”. Verify the file extension is “.ps1” (selecting the option “All Files” from the drop-down list in the “Save as type” option), so the same is not saved as text, but as a valid PowerShell file. Save it to a valid path, like “C:\Temp”.

d) Following the same steps explained above, create a second “.ps1” file, with the following script:

Note: This script is provided as a convenience to you as-is, without any express or implied warranties of any kind. Its intention is to automate the cleanup operations once the registry values and files needed by the MySQL for Visual Studio plugin uninstall process has been created.  Oracle is not liable for any issues arising out of your use of the script.

Save the file as “M4VSUninstall_PostValidation.ps1” in the same path, validating it is saved as a PowerShell file.

e) Open a PowerShell command window, and go to the path where you saved the scripts (like “C:\Temp”)

f) Execute the following command:

g) Uninstall the MySQL for Visual Studio plugin.

h) Execute the following command:

in order to cleanup any registry/files created by the scripts, and needed by the uninstall process.

With this workaround, you should be able to uninstall MySQL for Visual Studio 1.2.4 and earlier.

Thank you all for your support, and keep enjoying MySQL for Visual Studio.

MySQL for Excel 1.3.6 has been released

The MySQL Windows Experience Team is proud to announce the release of MySQL for Excel version 1.3.6. This is a maintenance release for 1.3.x. It can be used for production environments.

MySQL for Excel is an application add-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 which 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 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/.

MySQL for Excel 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.6 (2016-01-07)

This section documents all changes and bug fixes applied to MySQL for Excel since the release of 1.3.6. Several new features were added to the 1.3.x branch, for more information see What Is New In MySQL for Excel 1.3 (http://dev.mysql.com/doc/mysql-for-excel/en/mysql-for-excel-what-is-new-1-3.html).

Functionality Added or Changed

  • A new Generate an INSERT statement for each data row option was added to the Advanced Options dialog for Append and Export Data operations. This is disabled by default. A single INSERT statement is generated that inserts all affected rows, unless this option is enabled. When checked, an INSERT statement for each data row being appended or exported is generated in the resulting SQL query sent to the MySQL server. When unchecked, a single INSERT statement is generated as a bulk data operation, which performs better than multiple INSERT statements. While row-by-row inserts are slower, for debugging errors it could help determine which row causes an error, since the MySQL Server will process them row by row.
  • Added column properties to the Export Data dialog to support the definition of Auto Increment and Default Value for new MySQL tables where the data will be exported. Added a context menu to declare a numeric field to be Unsigned or to have Zero-Fill, accessible by right-clicking the Data Type combo box. Added the TIMESTAMP data type to the full list of valid data types, as it was not being shown before. Added help tool tips to fields in the Export Data dialog that explain in detail how the column properties work in a MySQL database.

Bugs Fixed

  • The Pivot Table feature was updated to work with Excel 2016.
  • Closing the plugin via the Close button in the panel would not toggle the MySQL for Excel checkbox in the Data ribbon.
  • Fixed the content detector for the active Excel cell after importing data and after loading database objects when a database is opened. Now, the data options are not enabled until a table is selected.
  • Append and Export operations would not append/export boolean data.
  • The MySQL for Excel Refresh All function would throw an unhandled exception.
  • With Office 2007, data would not auto-save after closing Excel.
  • Numeric data stored in text columns is now correctly formatted by Excel as text, and not as the “General” format that automatically formats cells as numbers when the data is stored in a text object. This fixes the issue where text columns were formatted as numbers, which stripped leading zeros.
  • Changed settings for containers and forms to let all UI components automatically scale on different DPI settings. Also removed the restriction to resize the MySQL for Excel‘s pane, so in case a different DPI setting is used and the fonts look too big, the pane can be resized to see contents as best as possible.

Quick links:

Enjoy and thanks for the support!

MySQL for Visual Studio 1.2.6 has been released

The MySQL Windows Experience Team is proud to announce the release of MySQL for Visual Studio 1.2.6. This is a maintenance release for 1.2.x. It can be used for production environments.

MySQL for Visual Studio is a product that includes all of the Visual Studio integration functionality to create and manage MySQL databases when developing .NET applications.

MySQL for Visual Studio is installed using the MySQL Installer for Windows which comes in 2 versions:

  • Full (150 MB) which includes a complete set of MySQL products with their binaries included in the downloaded bundle.
  • Web (1.5 MB – a network install) which will just pull MySQL for Visual Studio 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/.

MySQL for Visual Studio can also be downloaded by using the product standalone installer found at http://dev.mysql.com/downloads/windows/visualstudio/.

 

Changes in MySQL for Visual Studio 1.2.6 (2016-01-07)

Bugs Fixed

  • With MySQL for Visual Studio installed, attempting to create MSSQL connections would fail and throw an exception.
  • The Tools, Extensions and Updates, Installed, Tools window always reported “1.0.0” as the current MySQL for Visual Studio version number.
  • Executing Generate Database from Model from an existing Entity Framework model would throw an exception related to an error with the T4 template file, when then aborted the creation of the database. The Connector/Net Entity Framework assembly (MySql.Data.Entity.EF6.dll) path was fixed in the MySQL T4 template file (SSDLToMySQL.tt).
  • With Visual Studio 2012, generating a database from a model would fail and throw an exception. However, clicking OK after the error would cause the action to succeed.

 

What Is New In MySQL for Visual Studio 1.2

  • New MySQL Project Items for creating data views in Windows Forms and ASP.NET MVC web applications.
  • A new option in web configuration tool for the ASP.NET Personalization Provider (this feature requires MySQL Connector/NET 6.9 or newer).
  • A new option in web configuration tool for the ASP.NET Site Map Provider (this feature requires MySQL Connector/NET 6.9 or newer).
  • A new option for the MySQLSimpleMembership provider in the web configuration tool. (This feature requires MySQL Connector/NET or newer).

 

MySQL Windows Forms Project Item


This Project Item is available on the Add New Item dialog in Visual Studio when adding a new item to an existing project.

The dialog presented to create the MySQL Windows Forms Project Item automates the generation of a Windows Form, representing a view for MySQL data available through an existing Entity Framework’s model entity containing a MySQL table or view. Different view types are available to present the data:

  • Single-column: A form that contains one control by each existing column in the table with navigation controls and that allows CRUD operations.All controls can include validations for numeric and DateTime data types.
  • Grid: A form with a data grid view that contains navigation controls.
  • Master-detail: A form with a single control layout for the Parent table and a data grid view to navigate through child table’s data.

Supported with C# or Visual Basic language. This feature requires Connector/NET 6.7.5, 6.8.3 or 6.9.x.

For more details on the features included check the documentation at: https://dev.mysql.com/doc/connector-net/en/visual-studio-project-items-forms.html

 

MySQL ASP.NET MVC Project Item


This Project Item is available on the Add New Item dialog in Visual Studio when adding a new item to an existing project.

The dialog presented to create the MySQL ASP.NET MVC Item automates the generation of a controller and its corresponding view, representing a view for MySQL data available through an existing Entity Framework’s model entity containing a MySQL table or view. The MVC versions supported by this wizard are 3 when using Visual Studio 2010 or 2012, and 4 when using Visual Studio 2013 or greater.

The generation of the MVC items is done by creating an Entity Framework data model either with Entity Framework version 5 or 6 depending on the user’s selection.

Supported with C# or Visual Basic language. This feature requires Connector/NET 6.7.5, 6.8.3 or 6.9.x.

For more details on the features included check the documentation at: https://dev.mysql.com/doc/connector-net/en/visual-studio-project-items-mvc.html

 

New option in web configuration tool for the ASP.NET Personalization Provider


Personalization provider allows to store personalization state-state data regarding the content and layout of Web Parts pages-generated by the Web Parts personalization service using MySQL as a data source. This feature requires Connector/NET 6.9.x or greater.

http://dev.mysql.com/doc/connector-net/en/connector-net-website-config.html

 

New option in web configuration tool for the ASP.NET Site Map Provider


Site Map provider allows to show a hierarchical list of links that describe the structure of a site. This feature requires Connector/NET 6.9.x or greater.

http://dev.mysql.com/doc/connector-net/en/connector-net-website-config.html

 

New option in web configuration tool for the ASP.NET Simple Membership provider


The latest provider added to handle web site membership tasks with ASP.NET. This feature requires Connector/Net 6.9.x or greater.

http://dev.mysql.com/doc/connector-net/en/connector-net-simple-membership-tutorial.html

 

Quick links:

Enjoy and thanks for the support!

MySQL Connector/J 5.1.38 has been released

I’m pleased to announce that MySQL Connector/J 5.1.38 Maintenance Release is now generally available.

MySQL Connector/J can be downloaded from the official distribution channels MySQL Downloads and The Central repository. The commercially licensed version is available for download at My Oracle Support.

As always, we recommend that you check the CHANGES file in the download archive and/or the release notes to be aware of changes in behavior that might affect your application.

MySQL Connector/J 5.1.38, although released shortly after its predecessor, includes several important fixes and improvements. Most of them related to MySQL Fabric, multi-host replication aware connections support and support for TLSv1.2 and new encryption defaults. Even if you don’t require such features, we do recommend the upgrade to the latest version.

I’d like to highlight some of the most relevant fixes and improvements in this release:

MySQL Fabric and Multi-Host Replication Connections Revision

MySQL Fabric support in Connector/J is based on multi-host replication aware connections and the ability to dynamically manage server groups. Most of the server groups management is done automatically and, possibly, concurrently. The combination of all these features was never thoroughly used and stressed as much as now and the consequence is that they were effectively in need of some improvements.

This release ships with a fully re-factored multi-host replication aware connections support, which now inherits from the same base architecture as the remaining multi-host connections alternatives, the fail-over connections and load-balanced connections. This architecture provides a layered connection support structure and an improved statement execution routing model that effectively determines the correct physical connection to use at execution time, also fixing, by this way, a couple of existing bugs. The synchronization model in the server groups management was revised as well in order to overcome a few known thread deadlock situations. As a direct result the fail-over in MySQL Fabric support is now way more robust.

In the process of the improvements made in multi-host replication aware connections, two new connection properties were added:

allowSlaveDownConnections. This property sets the behavior for establishing replication aware connections when no slave hosts available. While, previously, this would result in a failed connection attempt, now we can define the behavior we prefer. This property takes a boolean value:

readFromMasterWhenNoSlaves. This property sets the behavior for the situations where, at run-time, all slave hosts in a replication aware connection become unavailable. The alternatives “should it fail?”, the only possible outcome before introducing this property, or “should the master host(s) be used in their place?”, are now available to the developer. Mind that when you set the option to use the master host(s), they will be used in read-only state as if they were slave hosts. Also mind that setting this property to true might, transparently, incur in extra load to the master host(s). This property takes a boolean value:

Security Compliance and Improvements

In its way of complying with the up-to-date security regulations and requirements, MySQL server 5.7 is now shipped with SSL/TLS enabled by default and any clients connecting to it should make use of such data protection features by default as well. Following this path, Connector/J 5.1.38 prioritizes the usage of SSL/TLS when establishing connections to this server. The missing support for TLSv1.2 and TLSv1.1 was additionally included in this release.

Connector/J now attempts to use the highest security layer available at run-time, starting from TLSv1.2 and, at the end, providing the best encryption system possible for the moment. This obviously depends on the MySQL server version we are connecting to and on the JVM version in use. In some situations it may be somewhat complex to find a compatible set of cyphers that can be used in both ends and some tweaks or adjustments could be required. The connection property enabledSSLCipherSuites may be a good companion in such cases.

Additional Bug Fixes

This release also includes a few other minor bug fixes. Although not especially relevant, these fixes help improving the overall quality of this Connector/J release.

Thanks!

Thank you all for your support. Enjoy this new Connector/J and keep in touch!

On behalf of the MySQL Connector/J Team.

Connector/Net joins MySQL products on Github

We are very pleased to announce that the MySQL Connector/Net source code has been added to GitHub. All of our versions can be found at MySQL Connector/Net repository, under the umbrella of the MySQL organization. This repository will expose the source code of the latest generally available (GA) releases. Same versions that are available in the official MySQL download site.

There are no changes to the releases cycles or the channels that we use for publishing new versions of Connector/Net. The purpose of publishing on GitHub is providing our users a quicker way to get the source code of all our GA versions. The repository contains all history since 6.7 alpha version.

You can clone the repository or download the source code at the GitHub site or using any Git client of your preference.

At the Git shell you can type:

$ git clone https://github.com/mysql/mysql-connector-net.git

Obviously, in order to execute git commands, you’ll have to install it previously in your computer. You can follow the official getting started guide in case you need some help for that.

We love to hear your thoughts or any comments you have about our product. Please send us your feedback at our forums, filing a bug at our community site, or at the social media channels.

Hope you found this information useful.

Thank you!

On behalf of the MySQL Connector/Net team.

 

 

 

MySQL for Visual Studio 1.2.5 has been released

The MySQL Windows Experience Team is proud to announce the release of MySQL for Visual Studio 1.2.5. This is a maintenance release for 1.2.x. It can be used for production environments.

MySQL for Visual Studio is a product that includes all of the Visual Studio integration functionality to create and manage MySQL databases when developing .NET applications.

MySQL for Visual Studio is installed using the MySQL Installer for Windows which comes in 2 versions:

  • Full (150 MB) which includes a complete set of MySQL products with their binaries included in the downloaded bundle.
  • Web (1.5 MB – a network install) which will just pull MySQL for Visual Studio 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/.

MySQL for Visual Studio can also be downloaded by using the product standalone installer found at http://dev.mysql.com/downloads/windows/visualstudio/.

 

Changes in MySQL for Visual Studio 1.2.5 (2015-10-29)

This section documents all changes and bug fixes applied to MySQL for Visual Studio since the release of 1.2.5. Several new features were added to the 1.2.x branch, for more information see the section below called: What Is New In MySQL for Visual Studio 1.2.

Known Limitations:

  • Item templates do not work correctly with MySQL Server 5.7.x, as it prevents the creation of an Entity Framework model.

Functionality Added or Changed

  • Added the Entity Framework option to the MySQL Website Configuration dialog for web projects, so Entity Framework version 5 or 6 can be used with a MySQL database provider. These automatically add the configuration/references needed to the web.config file and the project itself. Also, all available configuration options are now listed in the dialog.
  • Project Templates were replaced with Project Items. The Project Templates option was removed from the plugin toolbar, and from the Project menu, in order to add the Project Items feature with two options: MySQL New MVC Item and MySQL New Windows Form, which are available on the Add New Item dialog when adding a new Project Item. They add new windows forms or MVC controllers/views connected to MySQL.

Bugs Fixed

  • The Installer could not uninstall MySQL for Visual Studio if Visual Studio was uninstalled first.
  • In v1.2.4, the Launch Workbench and Open MySQL Utilities Console toolbar buttons were disabled.
  • The Templates installer feature could not be uninstalled via Add/Remove Programs. Because Project Templates were replaced by Project Items, this is no longer a concern.
  • The dataset designer wizard was not showing the stored procedure parameters when creating a “TableAdapter” using existing stored procedures for the “Select” command. Also, the stored procedure command had an “error” thus causing the dataset to not be created.

 

What Is New In MySQL for Visual Studio 1.2

  • New MySQL Project Items for creating data views in Windows Forms and ASP.NET MVC web applications.
  • A new option in web configuration tool for the ASP.NET Personalization Provider (this feature requires MySQL Connector/NET 6.9 or newer).
  • A new option in web configuration tool for the ASP.NET Site Map Provider (this feature requires MySQL Connector/NET 6.9 or newer).
  • A new option for the MySQLSimpleMembership provider in the web configuration tool. (This feature requires MySQL Connector/NET or newer).

 

MySQL Windows Forms Project Item


This Project Item is available on the Add New Item dialog in Visual Studio when adding a new item to an existing project.

 

The dialog presented to create the MySQL Windows Forms Project Item automates the generation of a Windows Form, representing a view for MySQL data available through an existing Entity Framework’s model entity containing a MySQL table or view. Different view types are available to present the data:

  • Single-column: A form that contains one control by each existing column in the table with navigation controls and that allows CRUD operations.All controls can include validations for numeric and DateTime data types.
  • Grid: A form with a data grid view that contains navigation controls.
  • Master-detail: A form with a single control layout for the Parent table and a data grid view to navigate through child table’s data.

Supported with C# or Visual Basic language. This feature requires Connector/NET 6.7.5, 6.8.3 or 6.9.x.

For more details on the features included check the documentation at: https://dev.mysql.com/doc/connector-net/en/visual-studio-project-items-forms.html

 

MySQL ASP.NET MVC Project Item


This Project Item is available on the Add New Item dialog in Visual Studio when adding a new item to an existing project.

The dialog presented to create the MySQL ASP.NET MVC Item automates the generation of a controller and its corresponding view, representing a view for MySQL data available through an existing Entity Framework’s model entity containing a MySQL table or view. The MVC versions supported by this wizard are 3 when using Visual Studio 2010 or 2012, and 4 when using Visual Studio 2013 or greater.

The generation of the MVC items is done by creating an Entity Framework data model either with Entity Framework version 5 or 6 depending on the user’s selection.

Supported with C# or Visual Basic language. This feature requires Connector/NET 6.7.5, 6.8.3 or 6.9.x.

For more details on the features included check the documentation at: https://dev.mysql.com/doc/connector-net/en/idm139719963401984.html

 

New option in web configuration tool for the ASP.NET Personalization Provider


Personalization provider allows to store personalization state-state data regarding the content and layout of Web Parts pages-generated by the Web Parts personalization service using MySQL as a data source. This feature requires Connector/NET 6.9.x or greater.

http://dev.mysql.com/doc/connector-net/en/connector-net-website-config.html

 

New option in web configuration tool for the ASP.NET Site Map Provider


Site Map provider allows to show a hierarchical list of links that describe the structure of a site. This feature requires Connector/NET 6.9.x or greater.

http://dev.mysql.com/doc/connector-net/en/connector-net-website-config.html

 

New option in web configuration tool for the ASP.NET Simple Membership provider


The latest provider added to handle web site membership tasks with ASP.NET. This feature requires Connector/Net 6.9.x or greater.

http://dev.mysql.com/doc/connector-net/en/connector-net-simple-membership-tutorial.html

 

 

Quick links:

Enjoy and thanks for the support!

MySQL for Excel 1.3.5 has been released

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 add-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 which 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 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/.

MySQL for Excel 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)

This section documents all changes and bug fixes applied to MySQL for Excel since the release of 1.3.5. Several new features were added to the 1.3.x branch, for more information see What Is New In MySQL for Excel 1.3 (http://dev.mysql.com/doc/mysql-for-excel/en/mysql-for-excel-what-is-new-1-3.html).

Functionality Added or Changed

  • 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.
  • Added a new advanced option called 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.
  • 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 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.

Bugs Fixed

  • Attempting to save data to a column where the data can not be written (incompatible data type) now generates an error.
  • 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.
  • 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.
  • 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.
  • The Append Data dialog was incorrectly mapping columns when only a single row of Excel data was selected to append. Also, if a single row of Excel data is selected with First Row Contains Column Names enabled, a warning is now displayed stating that no rows are available to complete the append operation.
  • 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 Workbook is saved, thereby saving the new connection information.
  • 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 add-in was active.
  • 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.
  • Deleted stored mappings would remain in the stored mapping method list.
  • 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.

 

Quick links:

Enjoy and thanks for the support!

MySQL Connector/J 5.1.37 has been released

I’m pleased to announce: MySQL Connector/J 5.1.37 Maintenance Release is now available.

MySQL Connector/J can be downloaded from the official distribution channels MySQL Downloads and The Central repository. Commercial license version is available for download at My Oracle Support.

As always, we recommend that you check the “CHANGES” file in the
download archive and/or the release notes to be aware of changes in behavior that might affect your application.

MySQL Connector/J 5.1.37 includes several bug fixes and other improvements. I’d like to highlight just a few:

Support for JDBC 4.2

Connector/J now provides implementations for pretty much all new JDBC 4.2 methods, namely for large update counts and max rows support.

The other big change is the support for the new temporal classes from java.time package. LocalDate, LocalDateTime, LocalTime are fully supported and can now be used in the multiple versions of setObject(...) and getObject(...) methods. They deliver results very similar to their counterparts, Date, Time and Timestamp respectively. The types OffsetDateTime and OffsetTime are partially supported via conversion to *CHAR types as MySQL doesn’t provide support for temporal data containing time zone information and, thus, doesn’t support the new TIME_WITH_TIMEZONE and TIMESTAMP_WITH_TIMEZONE JDBC types as well.

As a consequence to this upgrade, Connector/J 5.1.37 and future versions require Java 8 for its building process. We maintained, however, full compatibility with the already supported Java versions – Java 5 and above, Thus, this is a seamless replacement for the previous drivers versions you may be using in your projects.

New Connection Properties

sendFractionalSeconds. This property controls whether fractional seconds in timestamps are to be truncated on the client side or to be sent to the server side where they may be subject to rounding. It takes a boolean value:

Rounding fractional seconds may lead to undesired situations, especially when this results in apparently “big” temporal leaps, such as advancing a timestamp value to the next minute, day or even year. Many times this is not the required behavior for applications and setting this property to false safely cancels it.

Mind that this option applies only to prepared statements, callable statements and updatable result sets.

enableEscapeProcessing. This property, introduced as part of the support for JDBC 4.2, sets the default escape processing behavior for Statement objects. It takes a boolean value:

The method Statement.setEscapeProcessing() allows to set the escape processing behavior for individual statements. This method’s documentation refers that the connection property escapeProcessing can be used to set the default behavior, however, in Connector/J, this property is actually named enableEscapeProcessing.

Note that the default escape processing behavior in prepared statements is set by the long time available property processEscapeCodesForPrepStmts.

Changes in the Building Process

With JDBC 4.2 support comes a dependency on the Java 8 compiler and with it some changes in the building from source procedure. The documentation contains all the details you need to know but, the fast shortcut is that the previous ant property com.mysql.jdbc.jdk6 was upgraded to com.mysql.jdbc.jdk8 and holds the obvious reference to the JDK 8 path.

The optional property com.mysql.jdbc.java6.rtjar was added as well and is used to obtain the most accurate byte codes for every single JDBC implementation contained in this driver. You are not required to use it unless you are building for production, in which case we recommend you to set it too.

Bug Fixes

Several bug fixes were introduced aiming to improve your Connector/J experience.

We were able to fix a few things in the meta data structures, a time zone related adjustment, a couple of null point exceptions and corrected the right type of exception, all observed in very specific situations. We improved the authentication procedure, making it more robust. And, finally, we tweaked the driver to be fully compliant with latest MySQL server releases.

Thanks!

This release contains some contributions from end users. Special thanks to Jie Han and KwonNam for their valuable contributions.

Thank you all for your support as well. Enjoy this new Connector/J and keep in touch!

On behalf of the MySQL Connector/J Team.

MySQL Connector/NET 6.7.9, 6.8.7, and 6.9.8 have been released

Dear MySQL users,

MySQL Connector/Net 6.7.9, 6.8.7, and 6.9.8 are maintenance releases for the series of the .NET driver for MySQL. They can be used for production environments.

They are appropriate for use with MySQL server versions 5.5-5.7.

  • The GB18030 Chinese character set is now supported, a character set that was added in MySQL 5.7.4.
  • The JSON type is now supported, a type that was added in MySQL 5.7.8.
  • Generated columns (GENERATION_EXPRESSION) are now supported, a feature added in MySQL 5.7.6.

An additional entry added for 6.8.7:

  • A connection string that included Chinese characters for a database or uid property would emit the following exception;
    “MySqlException: Unknown database ‘???'”. To solve this, the handshake process was hanged to use bytes instead of encoded strings.

The documentation is available at:
http://dev.mysql.com/doc/connector-net/en/

Nuget packages are available at:
https://www.nuget.org/packages/MySql.Data/
https://www.nuget.org/packages/MySql.Data.Entity/
https://www.nuget.org/packages/MySql.Fabric/
https://www.nuget.org/packages/MySql.Web/

Enjoy and thanks for the support!

On behalf of the MySQL Connector/NET Team.

 

 

MySQL Connector/NET 6.7.8, 6.8.6, and 6.9.7 have been released

Dear MySQL users,

MySQL Connector/Net 6.7.8, 6.8.6, and 6.9.7 are maintenance releases for the series of the .NET driver for MySQL. They can be used for production environments.

They are appropriate for use with MySQL server versions 5.5-5.7.

They are now available in source and binary form from http://dev.mysql.com/downloads/connector/net/
(note that not all mirror sites may be up to date at this point-if you can’t find this version on some mirror, please try again later or choose another download site.)

Changes in MySQL Connector/Net 6.8.8

  • Connections to MySQL server 5.7 now default to using SSL.

Changes in MySQL Connector/Net 6.8.6

  • Connections to MySQL server 5.7 now default to using SSL.

Changes in MySQL Connector/Net 6.9.7

  • The selection of a master or slave now takes into account
    both the status and mode, when before it only used the
    mode. Ignoring the status was problematic as, for
    example, an unreachable server’s status is marked as
    FAULTY while the mode does not change. (Bug #21203824)
  • Using MySqlConnection.Open() with Connector/Net 6.9.6
    would fail and raise the error “Unable to connect to
    Fabric server”. (Bug #20983968)
  • Connections to MySQL server 5.7 now default to using SSL.

The documentation is available at:
http://dev.mysql.com/doc/connector-net/en/

Nuget packages are available at:
https://www.nuget.org/packages/MySql.Data/
https://www.nuget.org/packages/MySql.Data.Entity/
https://www.nuget.org/packages/MySql.Fabric/
https://www.nuget.org/packages/MySql.Web/

Enjoy and thanks for the support!

On behalf of the MySQL Connector/NET Team.