Skip to content
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

Try EF Core 9 now! #33030

Open
ajcvickers opened this issue Feb 8, 2024 · 8 comments
Open

Try EF Core 9 now! #33030

ajcvickers opened this issue Feb 8, 2024 · 8 comments

Comments

@ajcvickers
Copy link
Member

ajcvickers commented Feb 8, 2024

EF Core release notes for each version can be found in the GitHub Releases page.

You can try EF 9 before it goes GA using the daily builds or a preview release:

This issue is for general discussion around the EF Core 9 preview releases. See What's New in EF Core 9 for details on new features introduced as the EF9 work progresses.

@ajcvickers ajcvickers added this to the Discussions milestone Feb 8, 2024
@ajcvickers ajcvickers self-assigned this Feb 8, 2024
@erpardeepkaushik
Copy link

official support for IndexedDB will be superb for offline use case in blazor wasm apps. there are many packages but official one will be amazing.

https://github.com/Jinjinov/IndexedDB.Blazor
https://github.com/Reshiru/Blazor.IndexedDB.Framework

@ajcvickers ajcvickers changed the title Discussion for EF Core 9 previews and release candidates Try EF Core 9 now! Feb 16, 2024
@ajcvickers ajcvickers pinned this issue Feb 16, 2024
@sajjadarashhh
Copy link

official support for IndexedDB will be superb for offline use case in blazor wasm apps. there are many packages but official one will be amazing.

https://github.com/Jinjinov/IndexedDB.Blazor https://github.com/Reshiru/Blazor.IndexedDB.Framework

that would be very nice if we have them...

@tuespetre
Copy link
Contributor

Hey everyone, it's been a while... I just wanted to pop in to say you folks have been killing it. Last year I tried to revisit my query compiler project and update it for test and feature parity with EF Core just for fun, and I was blown away with how much EF Core has grown to support. I couldn't imagine having to use another ORM, and I am thankful for what you do as well as your receptiveness to my contributions those years ago.

@roji
Copy link
Member

roji commented Sep 1, 2024

Thank you @tuespetre!!

@caleblloyd
Copy link

Love these new Migration behaviors!

I was just starting to write the usual hackery to achieve this outside the library when, much to my delight, I discovered these. I'm sure you are already planning on adding it but should definitely mention those in the What's New docs. And as always, great work!

@jamo-semler
Copy link

How do we migrate to this new behavior regarding replacement of Discriminator to $type (#34269).

A updated solution just gets:

"Unable to materialize entity instance of type 'MyType'. No discriminators matched the discriminator value ''."

@roji
Copy link
Member

roji commented Sep 24, 2024

@jamo-semler it seems like you're asking how to access existing documents, which were created with earlier versions of EF, and so have a Discriminator property instead of `$type. If so, please read this breaking change note (the doc update isn't yet live, but this doc PR already contains the info).

Please let me know if that's clear and resolves things for you!

@jamo-semler
Copy link

jamo-semler commented Sep 24, 2024

@roji that worked perfectly.

For others arriving here the fix to revert to pre EF Core 9.0 behavior is to add these to the EntityTypeBuilder:

modelBuilder.Entity<SomeType>(builder => { builder.HasDiscriminator<string>("Discriminator"); builder.HasDiscriminatorInJsonId(); })

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants