-
Notifications
You must be signed in to change notification settings - Fork 386
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
EF Core 8 support #1746
Comments
Support, look forward to... |
We would very much appreciate it if you would add support for EF Core 8 soon, as we would like to continue using maria DB. |
Any updates? |
I'm working on upgrade Pomelo.EFCore.MySql to 8.0-preview6, there are still several cases failing now. There is already a branch |
Any progress here? There's lots of us that want to work with cutting edge stuff, but if you're dealing with for example MySql, it's difficult to find a workaround for making concrete implementations of repositories, basically, because everything online has relied on this third party package for years. I haven't made it work yet, so far. |
I agree is there any progress ? |
Prerelease 8.0.0-beta.1 (compatible with EF Core 8.0 RC1) is now available on nuget.org. Everything that worked in 7.0.0 should still work. There is full support for all new EF Core 8 features, except for primitive collections, which we have implemented but currently disabled by default, due to major bugs in MySQL and MariaDB. For more information about that, see #1791. Expect about 2 more beta releases. (Also be aware that MariaDB versions 10.3, 10.7, 10.8 and 10.9 have reached their end-of-life, and MySQL 5.7 will reach its end-of-life shortly in October 2023). |
The latest prerelease |
Any chance 8.0.0-rc.2 can become a nuget prerelease? |
.net 8 released please add a compatible nuget package version it can still be beta but at a bare min working to some degree.. |
Just upgraded a working app from v7 packages to v8 packages: System.Collections.Generic.KeyNotFoundException: Method 'WithComposedConverter' in type 'Microsoft.EntityFrameworkCore.Storage.BoolTypeMapping' from assembly 'Microsoft.EntityFrameworkCore.Relational, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' does not have an implementation. Exception thrown: 'System.TypeLoadException' in System.Private.CoreLib.dll |
|
Method 'WithComposedConverter' in type 'Microsoft.EntityFrameworkCore.Storage.BoolTypeMapping' from assembly 'Microsoft.EntityFrameworkCore.Relational, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' does not have an implementation. |
Expect the official Pomelo |
Thanks for the heads-up! Do you still need us to report issues such as those?
|
@setoy Only if you would get them with a compatible EF Core version. In that case, create a new issue for it. Otherwise, missing methods are expected. |
Hello @lauxjpn! Happy new year! Thanks a lot for such an amazing EF core provider for MySql. Could you please tell me if there is ETA for the stable release? I would be very grateful for the information! |
After bumped up many microservices from EF 7.0.15 & Pomelo 7.0.0 to EF 8.01 & Pomelo 8.0.0-beta.2, all are working fine, no problems at all database related !!! |
Guys its been more than 2 months since .NET 8 was released. Can we have a release date? |
Yesterday I thought about this too. They just released EF 8 recently. But what I like about Pomelo is the lack of dependencies. |
Right now this is the only thing holding up out net8.0 deploy so I'm hopeful this will be resolved soon. Very much appreciate the work @lauxjpn and team are doing to get this across the line! Go team Pomelo! |
Is there a place to see the list of critical bugs? Maybe people would be willing to pick some up if we knew what they were. I think part of the problem here is how dotnet is being managed now. dotnet 7 is set to go out of support in just a few months and then dotnet 6 before the end of the year. |
It looks like it's missing advanced type mappings for the compiled model on Issue opened here: Similar problem on other provider (I posted there first by mistake, but deleted): |
@lauxjpn Are you alive? :) What is the plan ? |
@pantonis Yeah, I am still here. Just got down with an unusually persistent cold that appears to be surprisingly hard to get rid of. However, with the beginning of February, I am getting now time back on my hands, so good new for Pomelo. The plan is the same: Fix any critical bugs and then get the GA release out the door. If there isn't too much going wrong, this weekend should be possible as release date. |
@lauxjpn hope you are well man. You are not alone on this :) . The entire world has these persistent colds lately. That is very good news. Thanks again and wishes for a speedy recovery! |
@lauxjpn do you have a "buy me a coffee" or any way for individual supporters to thank you? |
@lauxjpn |
@lauxjpn This is great news! Get well soon! |
@linchenrr Unfortunately not. I have a local work-in-progress branch regarding that feature, but it isn't production-ready yet and we will go GA now.
@paladinu No, I don't, but I appreciate the sentiment.
@felipe-villela We triaged this issue as critical. A fix will make it into |
@lauxjpn - I hope you are feeling much better now and thanks for all your hard work. Based on your earlier comment, I was expecting stable 8.0 release this weekend but it seems it didn't happen. By any chance, do you have a tentative date for the release? I've to take a call for our product release based on that. |
@rranjancoding The fix for #1835 has just been merged. We will release |
@lauxjpn Thank you so much ! |
Thank you all for your efforts I have this problem when I enter a field of type blob, mediumblob or longblob, it shows in the console: |
@kasemov-mt Please open a new issue, so we can take a look at it. This issue here was created to track the progress of our EF Core 8 support. People follow it to get informed about EF Core 8 related releases and don't want to get notified about other individual issues. Thanks! |
We will use this issue to track the progress on supporting EF Core 8, including its previews.
The text was updated successfully, but these errors were encountered: