-
-
Notifications
You must be signed in to change notification settings - Fork 390
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 9 support #1841
Comments
Prerelease 9.0.0-preview.1 (compatible with EF Core |
Hi @lauxjpn, do you have any plans to update to 9.0.0-preview.5? |
The same for .NET 9 preview7 ? |
An EF Core 9 RC compatible Pomelo release will be out in about 2-3 weeks. |
…re.MySql isnt updated to .Net 9 RC (or greater)
@lauxjpn Can we please get a NuGet release that's compatible with RC2 soon? I'd like to run our 9000+ test suite against it. I don't mind using the pomelo-nightly feed. |
Hi, what's the timeline for a RC2 compatible release? |
Looking forward to .NET 9 version 👀 |
One of the problems of this library that I see with respect to others of the same type is that it forces a range of versions that makes it impossible to use it in versions +1 of .NET... If it didn't do that at least we could get to use it “theoretically” if there are no breaking changes in EF Core that shouldn't because of Microsoft policies... But because of the decision to use ranges in the EF Core dependency, we always depend on a new stable release specific for that version... Mongo for example does not do it so we can use that same version with EF Core 9.x (which would be the logical thing with Pomelo) Another example: https://www.nuget.org/packages/Npgsql.EntityFrameworkCore.PostgreSQL/8.0.10#dependencies-body-tab |
@bdovaz I think there are breaking changes in EF Core 9, in the pubternal types that providers need to implement. That's why suppressing the version range warning doesn't make it work. |
@bkoelman I mean that “maybe not always” there are breaking changes that affect this library between major versions and that it is limiting by default its use |
I will try to get a compatible version out early next week (I am very much swamped this week, so earlier will just not be possible). While this prerelease will be compatible with EF Core 9, it will probably not contain a lot of the new EF Core 9 features yet.
@bdovaz That is a deliberate decision (doesn't have to be stable though). Every major EF Core release contains breaking changes and is incompatible with provider releases that target any preceding major version. |
This comment was marked as off-topic.
This comment was marked as off-topic.
He just replied above your message. He's hoping this week but swamped |
This comment was marked as duplicate.
This comment was marked as duplicate.
Maybe early in this week, please refer the above message. |
20240426151710 is not the latest version available. Look for 20241207210245 or newer. |
Thank you. That worked. I don't know why it didn't show up on the feed in the GUI so I installed it using command line. |
Prerelease 9.0.0-preview.2.efcore.9.0.0 (compatible with EF Core |
@lauxjpn Amazing - I will get it added to EF Core Power Tools ASAP! |
With
The codes above works ok with 8.0.11.
|
The same thing happens to me too for simple queries that should produce // List<Guid> userIds = [Guid.NewGuid()];
var users = await dbContext.Users
.Where(x => userIds.Contains(x.Id))
.ToListAsync(); |
yup have noticed the same, before i thought it was because pomelo was on preview 1 |
A solution is mentioned here: EnablePrimitiveCollectionsSupport() and TranslateParameterizedCollectionsToConstants() |
Thanks, @devnullue, I should have looked for existing issues first. Yes, with just And big thanks to @lauxjpn for all the hard work on this! |
Hi, is there any estimates on when you would publish a stable EF Core 9.0 version? We've been following this issue since November. |
@jossean-rivera Our Schedule and Roadmap is up-to-date, so we still plan to release the 9.0 GA version in January. |
We are nearing the end of January and my team is scheduled for .NET 9 upgrades for the next sprint (Start of February) from these initial release notes. Are we still on track for that or should I pivot? |
Have your team contribute to the package, that should definitely speed things up. |
I'm facing a weird issue, in version 8 the Column order annotation was working as expected, it still works but the following does not seem to work anymore for me |
This comment has been minimized.
This comment has been minimized.
You people are poison for the open source community. Just taking and demanding for free, not even giving anything back. You can still use the EF Core 8 version which runs on the LTS .NET8 so you don't have to use EF Core 9. |
@MeikelLP, my two cents is that it isn't the delays that are the problem. It is the lack of communication about the delays. And the same thing happens every year with this project. (and I'm not trying to defend enisn's obnoxious image; that doesn't help anything). |
I have been using the Pomelo.EntityFrameworkCore.MySql 9.0.0-preview.2.efcore.9.0.0 for many weeks in production.
I have comprehensive test suites for the DAL, so I am fairly confident Pomelo.EntityFrameworkCore.MySql 9.0.0-preview.2.efcore.9.0.0 won't break my app --- I won't say it won't break yours since my app is probably not complicated enough to encounter the edge cases you have experienced. A trick when using 9.0.0-preview.2.efcore.9.0.0 is, you may need to explicitly reference Microsoft.EntityFrameworkCore.Relational or Microsoft.EntityFrameworkCore 9 or 9.01 in some of your csproj files when the compiler or runtime MIGHT complains downgrading of the package. |
I can also confirm that version And I, too, don't see a point in constant nagging about the final version. It will be out once it's ready. Writing and maintaining EF Core provider for free is not an easy task. Sooner or later, life catches up, especially if you are (more or less) the only person maintaining a huge codebase. We should be thankful for things moving on at all, or jump in to help - it is open-source, after all. For those concerned about the stability and the release cadence, you can try to migrate to another database. In our case, we don't have technical but business obstacle. We are trying to push the management to make the transition to Postgres, but they are a bit reluctant at this point, since that means another software to maintain by the infra team. |
@zijianhuang: You can use version ranges to prevent that: https://learn.microsoft.com/en-us/nuget/concepts/package-versioning?tabs=semver20sort#version-ranges VS should not warn you then. Very useful tip I learned recently with FluentAssertions the fiasco
@mc2002tii This is still a free (most likely hobbyish) project from some people from the internet. They are not required to implement anything. It's a blessing they do it for free. Oracle is worse even though they are paid. Also they are developer not PR guys. The are not required be transparent to respond at all. If you don't like them: Fork the project. That's the OSS spirit. |
Update Pomelo.EntityFrameworkCore.MySql from 8.0.2 to 9.0.0-preview.2.efcore.9.0.0 We have a "Contains" using an 'enum' in our query, which runs fine in version v8.0.2, but fails in v9: public LoadDataSpecification(Guid mandatorId, List<ServiceType> serviceTypes)
: base(f => f.MandatorId.Equals(mandatorId) && serviceTypes.Contains(f.ServiceType)); Without "Contains" this query runs fine in v9 as well: public LoadDataSpecification(Guid mandatorId, List<ServiceType> serviceTypes)
: base(f => f.MandatorId.Equals(mandatorId)); So can you please support "Contains" in v9, as well? Result:
System.InvalidOperationException
HResult=0x80131509
Message=The LINQ expression '@__serviceTypes_1' could not be translated.
Additional information: Primitive collections support has not been enabled.
Either rewrite the query in a form that can be translated, or switch to client evaluation explicitly by inserting a call to 'AsEnumerable', 'AsAsyncEnumerable', 'ToList', or 'ToListAsync'.
See https://go.microsoft.com/fwlink/?linkid=2101038 for more information.
Source=Pomelo.EntityFrameworkCore.MySql
StackTrace:
at Pomelo.EntityFrameworkCore.MySql.Query.Internal.MySqlQueryableMethodTranslatingExpressionVisitor.TranslatePrimitiveCollection(SqlExpression sqlExpression, IProperty property, String tableAlias) |
@boeschenstein, this has been referenced in the past comments. I have asked the same question, and @devnullue has pointed me to #1960. Adding option |
Is anyone having trouble with seeding data the new way (https://learn.microsoft.com/en-us/ef/core/modeling/data-seeding#configuration-options-useseeding-and-useasyncseeding-methods)? I am getting:
Troubleshooting steps: dotnet/efcore#33319 (comment) Additional research: |
I already mentioned that people (and I) would be willing to donate time. However, the project is under-documneted and not in a shape which would allow any outsider to help out or dig into the code with a reasonable amount of effort. This project needs new direction in order to involve more people to help out. We can't just have one or two people be blockers and the single point of failure for such an important project |
I have time on my hands again, probably until the end of summer. So we should be able to release the GA version in March. |
We will use this issue to track the progress on supporting EF Core 9, including its previews.
The text was updated successfully, but these errors were encountered: