Entity that owns multiple entities of the same type with navigations back to the owning type makes model construction fail #35346
Comments
you have two UserId columns in your Owned entity. As your User "Owns" a "UserTimestamp" there is an implicit "UserId"-Column in that entity. i imagine just removing the UserId from UserTimestamp would be enough to fix it |
|
@kirides Yes, that is by design. The |
|
@alexanderchr what happens if modify it to this? [ForeignKey(nameof(User))]
public int UserId { get; set; }
public User User { get; set; } |
|
I get the same error with that change. But as you can see from the model with |
AndriySvyryd
added
the
closed-fixed
I have lots of entities for which I need to track when and by whom they were created and last updated. I have solved this by putting an owned type
UserTimestampon tracked entities asCreatedandUpdated. Something like this:This worked well until I needed to add tracking to the
Usermodel, probably because of the self referencing that this introduces. If I putCreatedandUpdatedas above on theUsermodel, EF throws during model construction.Below is a minimal reproduction:
which throws
However, if I remove the
Updatedproperty from the type and the configuration, the following model is created, which looks as expected:Everything also works if I make a copy of the class
UserTimestampand use that copy for theUpdatedproperty (so thatCreatedandUpdatedhave nominally different, but otherwise equivalent, types).It seems to me that since it works to have navigations back to owning entity type for the case when the owning type owns a type once, and also when it owns multiple (nominally different) types, the expected behaviour is that is should also work for the case when it owns the same type multiple times.
Include provider and version information
EF Core version: 9.0.0
Database provider: occurs with both SQLServer and Postgres providers
Target framework: .NET 9.0
Operating system: N/A
IDE: N/A
The text was updated successfully, but these errors were encountered: