Arthur Vickers
Arthur Vickers
Confirmed the regression is for async only.
@b-giavotto This is by-design. If the PK values are changed, then EF needs to be informed of this change by calling `DetectChanges`. For example: ```C# firstEn.CompositePK1 = "A"; firstEn.CompositePK2 =...
Possible duplicate of #33129
@archer87pl The repro code in your example project throws the same exception on 6.0.29 as it does on 8.0.4.
@archer87pl This appears to be directly the case you referenced above: [Orphaned dependents of optional relationships are not automatically deleted](https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-core-7.0/breaking-changes?tabs=v7#optional-deletes). The mitigations there are still the best way to deal...
@archer87pl Yes, if you want to delete orphans on optional relationships, then this needs manual processing. Otherwise the relationship will be severed but the entity will not be deleted automatically,...
Might be worth adding some logging/warnings, but not sure the value is high enough. I'll leave it to @AndriySvyryd to either close or backlog.
@prrami Store generated key values are not available until the database has generated these values. This means they will never be available in `SavingChangesAsync`, since this is called before SQL...
@PascalArdex You should not need all the code you have when dealing with non-collections of enums. Instead, this should work: ```C# protected override void ConfigureConventions(ModelConfigurationBuilder configurationBuilder) { configurationBuilder.Properties().HaveConversion(); } ```...
/cc @ericsink in case this rings any bells.