EF Core 9 support

[lauxjpn]

We will use this issue to track the progress on supporting EF Core 9, including its previews.

[lauxjpn]

Prerelease 9.0.0-preview.1 (compatible with EF Core 9.0.0-preview.1.24081.2) is now available on nuget.org.

[rodolforeinaperficient]

Hi @lauxjpn, do you have any plans to update to 9.0.0-preview.5?

[ysmoradi]

Hi @lauxjpn, do you have any plans to update to 9.0.0-preview.5?

The same for .NET 9 preview7 ?

[dajma00]

I think we need a release for .NET 9, RC1. I get this error:

[lauxjpn]

An EF Core 9 RC compatible Pomelo release will be out in about 2-3 weeks.

[dajma00]

Anyone else getting this both with Pomelo RC1 and RC2, .NET9 RC2:

[glennawatson]

Anyone else getting this both with Pomelo RC1 and RC2, .NET9 RC2:

Yeah, seems to be more members were added in the RC vs the preview in entity framework itself.

[bkoelman]

@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.

[raffidahmad]

Hi, what's the timeline for a RC2 compatible release?

[siriak]

Looking forward to .NET 9 version 👀

[bdovaz]

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...

https://github.com/PomeloFoundation/Pomelo.EntityFrameworkCore.MySql/blob/main/Dependencies.targets#L3

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

[bkoelman]

@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.

[bdovaz]

@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

[lauxjpn]

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.

---

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...

@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.

[Emiliowilvca]

when is version 9.0.0 released?

[glennawatson]

when is version 9.0.0 released?

He just replied above your message. He's hoping this week but swamped