MySQL Connector/Net 8.0.8 is the fifth development release that expands cross-platform
support to Linux and macOS when using Microsoft’s .NET Core framework. Now, .NET
developers can use the X DevAPI with .NET Core and Entity Framework Core (EF Core)
1.0 to create server applications that run on Windows, Linux and macOS. We are very
excited about this change and really look forward to your feedback on it!
MySQL Connector/Net 8.0.8 is also the seventh development release of MySQL
Connector/Net to add 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/index.html.
For more information about how the X DevAPI is implemented in Connector/Net, see
http://dev.mysql.com/doc/dev/connector-net.
Note
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.
To download MySQL Connector/Net 8.0.8-dmr, see the “Development Releases” tab at
http://dev.mysql.com/downloads/connector/net/
Changes in MySQL Connector/Net 8.0.8 (2017-07-10, Development Milestone)
MySQL Connectors and other MySQL client tools and
applications now synchronize the first digit of their version
number with the (highest) MySQL server version they support.
For example, MySQL Connector/Net 8.0.12 would be designed to
support all features of MySQL server version 8 (or lower).
This change makes it easy and intuitive to decide which
client version to use for which server version.
MySQL Connector/Net 8.0.8 is the first release to use the new
numbering. It is the successor to MySQL Connector/Net 7.0.7.
* Functionality Added or Changed
* Bugs Fixed
Functionality Added or Changed
* X DevAPI: The format of document ID values generated when
adding documents to a collection has changed. It is still
a string of 32 hexadecimal digits based on UUID, but the
order of digits was changed to match the requirement of a
stable ID prefix.
* All connections created using MySQL Connector/Net now are
secure by default. Also, the Ssl-Enable connection option
has been replaced by Ssl-Mode. Permitted Ssl-Mode values
are None, Required (the default), VerifyCA, and
VerifyFull.
With this change, a non-SSL enabled server now requires
the Ssl-Mode option be set to None explicitly in the
connection string or the connection will fail.
* X DevAPI: It is no longer permitted to pass an empty
search condition, such as the NULL value or an empty
string, to the Collection.Modify and Collection.Remove
methods.
* X DevAPI: The NodeSession class has been renamed to
Session and the MySQLX.GetNodeSession method has been
renamed to MySQLX.GetSession. Also, the XSession class
has been removed.
* X DevAPI: When creating a new connection, multiple hosts
now can be specified as part of the connection string,
which will try each host until a successful connection is
established or all elements from the host list have been
tried. The following connection-string formats are
supported:
var mySession = MySQLX.GetSession(
"mysqlx://dbuser:password@[" +
"localhost:33060," +
"192.1.10.10:33060," +
"[2001:db8:85a3:8d3:1319:8a2e:370:7348]:33060" +
"]"
);
var mySession = MySQLX.GetSession(
"user=dbuser;" +
"password=dbpassword;" +
"server=" +
"192.1.10.10," +
"server.example.com," +
"localhost;" +
"port=33060;"
);
Bugs Fixed
* EF Core: The Database First feature did not support the
following data types: BINARY, VARBINARY, MEDIUMBLOB,
LONGBLOB, SET, DATE, TIME, and YEAR. (Bug #25493209)
* EF Core: Database First support produced an error when
the existing MySQL database included one or more views.
(Bug #25493086)
* EF Core: Using
System.ComponentModel.DataAnnotations.Schema.TableAttribu
te to initialize a new class instance that specified the
name of an existing MySQL table produced incorrect
mappings of table and column names.
(Bug #25394223, Bug #84423)
Nuget
Packages are available at:
https://www.nuget.org/packages/MySql.Data/8.0.8-dmr
https://www.nuget.org/packages/MySql.Web/8.0.8-dmr
https://www.nuget.org/packages/MySql.Data.EntityFrameworkCore/8.0.8-dmr
https://www.nuget.org/packages/MySql.Data.EntityFrameworkCore.Design/8.0.8-dmr
Enjoy and thanks for the support!
On Behalf of MySQL/Oracle Release Engineering Team
Prashant Team