-
Notifications
You must be signed in to change notification settings - Fork 345
-
- Opening a connection from the pool is now twice as fast: Implement pipelining #1089 .
- This may fail with Amazon Aurora RDS; to explicitly disable this, set
Pipelining = False;in the connection string.
- This may fail with Amazon Aurora RDS; to explicitly disable this, set
- Add support for query attributes: Support query attributes #930 .
- This requires MySQL Server 8.0.23 (or later) for regular commands, and MySQL Server 8.0.26 (or later) for prepared commands.
- Add attributes to the
MySqlCommand.Attributescollection to send them to the server when the command is executed.
- Add
MySqlDecimalsupport: Implement MySqlDecimal #1070 . - Improve
MySqlDataReader.GetXexceptions forNULLvalues: Unhelpful exception message when reading NULL value #1092 . - Improve detection of Azure Database for MySQL proxies: Improve proxy detection for Azure MySQL Flexible Server #1093 .
- Update Microsoft.SourceLink.GitHub.
- Thanks to @ejball and @sumitdvlp for contributions to this release.
MySqlConnector.Logging.Microsoft.Extensions.Logging
- Logger names are now prefixed with
MySqlConnector.by default: MySqlConnector.Logging.Microsoft.Extensions.Logging is not prefixing the category name like other loggers #1080 .- To return to the previous behavior, use
MicrosoftExtensionsLoggingLoggerProvider(loggingFactory, omitMySqlConnectorPrefix: true).
- To return to the previous behavior, use
- Added
.UseMySqlConnectorLogging()extension method to add logging easily.
This discussion was created from the release 2.1.0.
Beta Was this translation helpful? Give feedback.
All reactions
Replies: 1 comment 4 replies
-
I see that 2.1.x nugets ship assembly with 2.0.0 version. Is it expected change in v2 branch? v0/v1 releases had assembly version matching nuget version.
Beta Was this translation helpful? Give feedback.
All reactions
-
The version info on the DLL in the nupkg looks correct to me:
Are you talking about the strong name? MySqlConnector, Version=2.0.0.0, Culture=neutral, PublicKeyToken=d33d3e53aa5f8c92
Beta Was this translation helpful? Give feedback.
All reactions
-
Are you talking about the strong name?
If yes, then note that this is a recommended best practice:
✔️ CONSIDER only including a major version in the AssemblyVersion.
https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/versioning#assembly-version
Beta Was this translation helpful? Give feedback.
All reactions
-
Yep, version in strong name (one, returned by assembly.GetName().Version). I'm fine with it, just wanted to confirm it's expected behavior, as we used version for feature detection for older versions.
Beta Was this translation helpful? Give feedback.
All reactions
-
OK, yes it is expected behaviour.
v0/v1 releases had assembly version matching nuget version.
AFAIK they had a major-number-only strong name version, too.
I don't actually know exactly where it comes from. The build chain generates [assembly: System.Reflection.AssemblyVersionAttribute("2.0.0.0")] in src\MySqlConnector\obj\Release\net6.0\MySqlConnector.AssemblyInfo.cs so something in the standard build chain decides to use only a major version.
Beta Was this translation helpful? Give feedback.