-
Notifications
You must be signed in to change notification settings - Fork 453
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Announcement] Drop MySQL.Data support #3145
Comments
Added PR #3238, that removes provider support. If anyone have objections for this removal, you should rise them now... |
Do you have an example on how to use MySqlConnector with LINQ2DB? Simply replacing the nuget references doesn't seem to be sufficient as I'm getting |
After removal it will be enough to replace nuget, but for now you need to specify proper provider. I don't know how you configure your connection, so it's hard to say how to fix it for YOU. In general you need to change providerName option of your connection. |
If case this helps anyone else: We have a custom class that inherits from MySqlDataProvider. The trick was to pass the "MySqlConnector" string in the base constructor. @MaceWindu referencing |
You don't need to reference any of |
That did the trick, thank you! All our integration tests (against a real db) passed with |
On hold, need to check if we can provide support for big decimals. Basically only feature |
Facing strong opposition inside team, we will preserve mysql.data support for now :) |
Still it is highly discouraged from use due to low quality |
Looking for feedback regarding possible removal of MySQL.Data mysql provider support in v4 and support only MySqlConnector provider.
MySQL.Data disadvantages (only biggest, there are more of them):
MySQL.Data advantages:
Note that it shouldn't be breaking change for EF.Core integration as pomelo.mysql use MySqlConnector.
What this removal means for users:
linq2db.mysql
T4 nuget will be obsoleted and users will need to switch to T4 nuget for MySqlConnector. Note that we probably will obsolete all T4 nugets in v4 (not decided yet) as we plan to switch to new scaffolding tools in v4The text was updated successfully, but these errors were encountered: