-
Notifications
You must be signed in to change notification settings - Fork 55
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
Owned entities with Unique Index throws exception #469
Comments
Hello @virzak , The v6.13.10 has been released. Could you try it and let us know if everything is working with the latest release? Best Regards, Jon |
@JonathanMagnan thanks, it passes, but Here is a breaking commit: |
|
Great to hear! Don't hesitate to contact us if you need anything. Best regards, Jon |
@JonathanMagnan, sorry, |
Here is the exception:
|
@JonathanMagnan, would be great if you could look into it. I also believe that |
Thank for reporting, My developer pushed a fix early this week, I should be able to review it Friday and check if the |
Hello @virzak , Unfortunately, it will take us some more time. The code my developer provided fixed this case but some side impacts could happen in some other complex cases. If no fix is provided next week, we will create a temporary option for you so you will be able to use this features by turning this option to |
@JonathanMagnan Thanks so much for the update. |
Hello @virzak , As promised, since we're not able to complete the full fix, we added an option that will work with this scenario: EntityFrameworkManager.TmpUseDistinctTableLogic = true; This option is temporary and will be removed as soon as my developer provides a complete fix (I will give you an update when it happens). |
Thank you, @JonathanMagnan |
Description
Owned entity with a unique index works (with a workaround) in EF Core. See dotnet/efcore#11336
However it throws with EntityFramework-Extensions
Exception
If you are seeing an exception, include the full exceptions details (message and stack trace).
Project
This commit throws an exception
Further technical details
The text was updated successfully, but these errors were encountered: