repository·master·Indexed 23 days ago
https://github.com/mysql-net/mysqlconnectorA high-performance, fully asynchronous ADO.NET data provider for MySQL and MariaDB. It is a clean-room implementation of the MySQL protocol designed to outperform the official MySQL Connector/NET, providing managed code implementations of core ADO.NET classes like DbConnection, DbCommand, DbDataReader, and DbTransaction without relying on native dependencies.
MySQL Connector for .NET is an ADO.NET data provider for MySQL and compatible servers like MariaDB. It provides the standard implementations of the core ADO.NET classes required to query and update databases from managed code:
DbConnectionDbCommandDbDataReaderDbTransactionIt is designed to be high-performance, fully asynchronous, and lightweight, implementing the MySQL Protocol in managed code without relying on native dependencies.
MySqlConnector is compatible with several popular .NET Object-Relational Mappers (ORMs). Depending on your architectural needs, you can use the following libraries:
MySqlConnector.Authentication namespace provides the core abstractions for implementing and interacting with MySQL authentication plugins. It includes a registry of known plugins and the interfaces required to define custom authentication logic.MySqlConnector.Logging namespace provides the infrastructure to redirect or implement custom logging for the MySQL Connector. You can control logging behavior using MySqlConnectorLogManager and implement your own logging targets by implementing the IMySqlConnectorLogger and IMySqlConnectorLoggerProvider interfaces.When storing .NET date values, choose between TIMESTAMP and DATETIME columns based on your requirements:
TIMESTAMP:1970-01-01 00:00:01 to 2038-01-19 03:14:07.DATETIME:1000-01-01 to 9999-12-31.Consult the official MySQL documentation for detailed behavior regarding these types.
All spans produced by MySqlConnector use ActivityKind.Client. The following spans are created during common operations:
| Span name | Created by | Notes |
|---|---|---|
Open | MySqlConnection.Open() and OpenAsync() | Covers connection establishment or pool checkout. |
Execute | MySqlCommand.Execute*() and MySqlBatch.Execute*() | Begins when the command is sent and ends when the MySqlDataReader is closed or disposed. |
Commit | MySqlTransaction.Commit() and CommitAsync() | Covers the transaction commit round-trip. |
Rollback | MySqlTransaction.Rollback() and RollbackAsync() | Covers explicit or implicit rollback. |
MySQL FLOAT columns use 32-bit single-precision IEEE 754 values. When retrieving these values, MySQL may use the FLT_DIG constant, which can cause an apparent loss of precision in the least-significant digit.
To retrieve exact values without precision loss, use one of the following:
DOUBLE column type.SELECT value+0).MySqlCommand.Prepare, which utilizes the binary protocol to retrieve the original value.MySqlDataSource is an implementation of DbDataSource for MySQL. It is available for all Target Framework Monikers (TFMs) and serves as a centralized way to manage connection configuration and registration with dependency injection.MetaDataCollections schema is used to retrieve information about available schemas within the database. When querying this schema, you can access details regarding collection names, the number of restrictions allowed, and the number of identifier parts required for composite names.When an Execute span is active and the .NET Activity uses W3C ID format, MySqlConnector attempts to send the active trace context to the MySQL Server as query attributes. This requires the server to support query attributes.
Attributes sent:
traceparent: The W3C traceparent value from Activity.Id.tracestate: The W3C tracestate value (if non-empty).Note: If these attributes are already manually provided in MySqlCommand.Attributes, MySqlConnector will not add duplicates.
MySqlConnector, note that transactions may not be nested. Attempting to start a transaction while another is already active on the connection will result in an error.When the Server option contains a comma-delimited list of host names, you can use the LoadBalance option to control how connections are distributed.
Note: RoundRobin and LeastConnections require Pooling=True. Random and FailOver can be used with Pooling=False.
Available strategies:
RoundRobin (Default): Each new connection opened for the pool uses the next host name sequentially with wraparound.FailOver: Each new connection tries the first host; subsequent hosts are used only if the first fails.Random: Servers are tried in a random order.LeastConnections: Servers are tried in ascending order of the number of currently-open connections in the pool.