MySQL Connector/C 6.1.10 GA has been released

Dear MySQL Users,

A new GA (general availability) version of MySQL Connector/C has been
made available: MySQL Connector/C 6.1.10 GA. The MySQL Connector/C 6.1
implements the MySQL C API for connecting client applications to the
MySQL Server 5.5 or newer.

You can download the production release at:
http://dev.mysql.com/downloads/connector/c/6.1.html

MySQL Connector C (Commercial) will be available for download on the My
Oracle Support (MOS) website. This release will be available on
eDelivery (OSDC) in next month’s upload cycle.

Please see the documentation and the README file in the source distribution
for a detailed description of bugs that have been fixed.

Enjoy!

Changes in MySQL Connector/C 6.1.10 (2017-04-28, General
Availability)

Compilation Notes

* The Windows version of MySQL Connector/C Community is now
built using the dynamic C runtime libraries (that is,
with the /MD compiler option), with the following
implications for users:

+ Target hosts running Windows applications that use
MySQL Connector/C Community now need the Visual C++
Redistributable for Visual Studio 2015
(https://www.microsoft.com/en-us/download/details.aspx?id=48145)
installed on them.

+ Client applications on Windows that use MySQL
Connector/C Community should be compiled with the
/MD compiler option.

Security Notes

* The linked OpenSSL library for MySQL Connector/C 6.1
Commercial has been updated to version 1.0.2k. For a description
of issues fixed in this version, see
http://www.openssl.org/news/vulnerabilities.html. This change
does not affect the Oracle-produced MySQL Community build of
Connector/C, which uses the yaSSL library instead. (Bug
#25615447)

On behalf of the Oracle MySQL Release Engineering Team,
Nawaz Nazeer Ahamed

MySQL Connector/J 5.1.42 has been released

Link

Dear MySQL Users,

MySQL Connector/J 5.1.42, a maintenance release of the production 5.1
branch has been released. Connector/J is the Type-IV pure-Java JDBC
driver for MySQL.

MySQL Connector Java is available in source and binary form from the
Connector/J download pages at
http://dev.mysql.com/downloads/connector/j/5.1.html
and mirror sites as well as Maven-2 repositories.

MySQL Connector Java (Commercial) is already available for download on the
My Oracle Support (MOS) website. This release will be available on eDelivery
(OSDC) in next month’s upload cycle.

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

MySQL Connector/J 5.1.42 includes the following general bug fixes and
improvements, also available in more detail on
http://dev.mysql.com/doc/relnotes/connector-j/en/news-5-1-41.html

Changes in MySQL Connector/J 5.1.42 (2017-04-28)

Version 5.1.42 is a maintenance release of the production 5.1
branch. It is suitable for use with MySQL Server versions
5.5, 5.6, and 5.7. It supports the Java Database Connectivity
(JDBC) 4.2 API.

* Functionality Added or Changed

* Bugs Fixed

Functionality Added or Changed

* A null value can now be extracted from a result set to a
class belonging to the java.time package. Before, such an
extraction resulted in a NullPointerException being
thrown. Thanks to Martin Desharnais for contributing the
code. (Bug #25250938, Bug #84189)

* Connector/J now checks that a MySQL server’s SSL
certificate and the Certificate Authority (CA) that
issued it are not expired before establishing an SSL
connection with the server, even if the connection
property verifyServerCertificate is set to false. (Bug
#20515688)

* Name-value pairs contained in the connection property
sessionVariables can now be separated by either commas or
a semicolons. (Bug #17757070)

Bugs Fixed

* An invalid timezone identifier was used in
StatementRegressionTest.java of the Connector/J
testsuite. (Bug #25687718, Bug #85351)

* A mysql client failed to establish an SSL connection to
the server using the SSL certificates provided in the
Connector/J source package. It was because the
certificates have been generated with the same Common
Name. This fix corrects the Common Names and regenerates
the SSL certificates. (Bug #25636947)

* The unit test testsuite.simple.ResultSetTest.testPadding
failed with the error Unknown character set: ‘gb18030’
after the collation map updates in release 5.1.40. (Bug
#25556597)

* In a multi-host connection, query timeouts did not occur
as configured. It was because the CancelTask thread, when
trying to access the top level, virtual connection
object, ran into a race condition with the connection
monitor and then hung. With this fix, the CancelTask
thread is passed a direct reference to the underlying
physical connection, with which it can execute the
cancellation. (Bug #25490163, Bug #84783)

* CallableStatement.extractProcedureName() did not return
the correct result when the procedure name contained a
dash. This was due to an error in the stripComments()
method of the StringUtils class, which has now been
corrected. (Bug #25321524, Bug #84324)

* The ConnectionImpl.isReadOnly() method returned a
confusing error message when it could not retrieve the
read-only status of the server. The message has now been
changed to “Could not retrieve transaction read-only
status from server.” (Bug #25101890, Bug #83834)

* A NullPointerException was thrown when a null boolean
value was being read from the database. (Bug #25048406,
Bug #83662)

* After a BIT value had been retrieved from a result set,
the wasNull() method of the result set returned value for
the last wasNull() query instead of the value for the
last retrieved column. (Bug #24841670, Bug #83368)

* Using a partially-quoted identifier (with only the
database or the procedure name quoted) or a non-existent
parameter to register an output parameter in a
CallableStatement caused a NullPointerException. With
this fix, a partially-quoted identifier is accepted, and
a non-existent parameter causes a SQLError to be thrown.
(Bug #22333996, Bug #79561)

* DatabaseMetaData.getProcedureColumns() and
DatabaseMetaData.getFunctionColumns() did not return
expected results. This was due to the errors with the
matching algorithm for the column names, which have now
been fixed. Notice that, however, the effects of the
connection parameter getProceduresReturnsFunctions on the
two methods when JDBC 4 is used remain unchanged. (Bug
#19531384, Bug #73775)

* When an UpdatableResultSet was used, trying to close the
result set and its prepared statement simultaneously by
different threads might result in a deadlock. This fix
updates the synchronization mechanism for
UpdatableResultSet to avoid the issue. (Bug #17653733,
Bug #70704)

* After a connection had already switched catalog with
setCatalog(), cached data from the old catalog was
returned for a reused server-side prepared statement.
With this fix, the cache of a server-side prepared
statement cache now includes the catalog in its key to
avoid wrong cache hits when the statement is reused on
another catalog. (Bug #16714868, Bug #66430)

On Behalf of MySQL/ORACLE RE Team
Gipson Pulla

MySQL for Visual Studio 2.0.5 has been released

The MySQL Windows Experience Team is proud to announce the release of  MySQL for Visual Studio 2.0.5 m4. Note that this is a development preview release and not intended for production usage.

MySQL for Visual Studio 2.0.5 m4 is the fourth development release of the MySQL for Visual Studio 2.0 series. This series adds support for the new X DevAPI. The X DevAPI enables application developers to write code that combines the strengths of the relational and document models using a modern, NoSQL-like syntax that does not assume previous experience writing traditional SQL.

To learn more about how to write applications using the X DevAPI, see http://dev.mysql.com/doc/x-devapi-userguide/en/. For more information about how the X DevAPI is implemented in MySQL for Visual Studio, and its usage, see http://dev.mysql.com/doc/refman/5.7/en/mysql-shell-visual-studio.html.

Please note that the X DevAPI requires at least MySQL Server version 5.7.12 or higher with the X Plugin enabled. For general documentation about how to get started using MySQL as a document store, see http://dev.mysql.com/doc/refman/5.7/en/document-store.html.

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/, under the tab “Development Releases”.

 

Changes in MySQL for Visual Studio 2.0.5 (2017-04-24)

Known limitation of this release: MySQL Connections Manager does not save the changes made to the default schema when editing a connection. Use one of the following workarounds to resolve this limitation:

  • For new connections created with MySQL Connections Manager in which a default schema is specified, close MySQL Connections Manager and then reopen it. After performing this action, you can add the connection to the Microsoft Visual Studio Server Explorer.
  • For existing connections, set the default schema with MySQL Workbench.

Functionality Added or Changed

  • Removed Support for Microsoft Visual Studio 2010.
  • Added support for Microsoft Visual Studio 2017.
  • Added an output pane to the MySQL SQL Editor window. The new MySQL Output pane includes the information that previously appeared in the Messages tab.

Bugs Fixed

  • The MySQL Data Export Tool exported data from the wrong schema when a second schema was selected and then deselected. In addition, all selected schemas were deselected when a single schema was deselected. (Bug #23666666)
  • Script files did not accept most keyboard input after the file was saved for the first time. (Bug #24751945)
  • The Field Type view in the result tab of an executed SQL query did not display field information correctly when the query included a schema name explicitly. (Bug #24601948)
  • The bit() data type was incorrectly implemented as bit(10) for MySQL tables in the Table Designer window.  (Bug #13477821)

 

Quick links

MySQL Connector/Python 2.1.6 GA has been released

Dear MySQL users,

MySQL Connector/Python 2.1.6 GA is a fourth GA version of 2.1 release
series of the pure Python database driver for MySQL. It can be used for
production environments.

MySQL Connector/Python version 2.1.6 GA is compatible with MySQL Server
versions 5.5 and greater. Python 2.6 and greater as well as Python 3.3
and greater are supported. Python 2.4, 2.5 and 3.1, 3.2 are not
supported.

MySQL Connector/Python 2.1.6 is available for download from:

http://dev.mysql.com/downloads/connector/python/#downloads

The ChangeLog file included in the distribution contains a brief summary
of changes in MySQL Connector/Python 2.1.6. For a more complete list of
changes, see below or online at:

http://dev.mysql.com/doc/relnotes/connector-python/en/

Enjoy!

Changes in MySQL Connector/Python 2.1.6 (2017-04-18, General
Availability)

Functionality Added or Changed

* An ssl-cipher option is now supported for specifying the
encryption cipher for secure connections. (Bug #22545879,
Bug #78186)

Bugs Fixed

* Compatibility issues with Django 1.9 were corrected. (Bug
#25726671)

* The fix for Bug #22529828 caused Python 2.7 to be unable
to insert binary data. (Bug #25589496, Bug #85100)
References: This issue is a regression of: Bug #22529828.

* Some SQL statements that worked using pure Python failed
with the Connector/Python C Extension enabled. (Bug
#25558885)

* Connector/Python produced no error or warning if the
server certificate was expired. (Bug #25397650)

* If an exception reset the underlying session, connections
in a connection pooled could become unavailable to the
pool. (Bug #25383644, Bug #84476)

* Methods for filtering time and datetime fields were
changed in Django 1.9 from value_to_db_datetime to
adapt_datetimefield_value and from value_to_db_time to
adapt_timefield_value. Proxy methods with the previous
names were added to Connector/Python ensure
compatibility. Thanks to Brian Tyndall for the patch.
(Bug #25349918, Bug #84410)

* Extra encapsulation was removed from the get_constraints
method for the foreign_key parameter. Thanks to Brian
Tyndall for the patch. (Bug #25349912, Bug #84409)

* Connector/Python added support for a database backend API
change introduced in Django 1.9 for the bulk_insert_sql
method. Thanks to Brian Tyndall for the patch. (Bug
#25349897, Bug #84408)

* Loading the world sample database worked using pure
Python but failed with the Connector/Python C Extension
enabled. (Bug #22476689, Bug #79780)

* If the output from the mysql_config –include command
included more than one directory, the C Extension failed
to compile. (Bug #20736339, Bug #76350)

On Behalf of the MySQL/ORACLE RE Team,
-Sreedhar S

MySQL for Visual Studio 1.2.7 has been released

The MySQL Windows Experience Team is proud to announce the release of MySQL for Visual Studio 1.2.7. 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 (352.8 MB) which includes a complete set of MySQL products with their binaries included in the downloaded bundle.
  • Web (1.7 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.7 (2017-04-10)

Functionality Added or Changed

  • Removed Support for Microsoft Visual Studio 2010.
  • Added support for Microsoft Visual Studio 2017.

Bugs Fixed

  • The MySQL Data Export Tool exported data from the wrong
    schema when a second schema was selected and then deselected.
    In addition, all selected schemas were deselected when a single
    schema was deselected. (Bug #25713981)
  • Script files did not accept most keyboard input after the
    file was saved for the first time. (Bug #25713638)

 

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.

https://dev.mysql.com/doc/connector-net/en/connector-net-tutorials-web-personalization-provider.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!