An entity with an interface property – is there a better approach when using Entity Framework Core?
I’m currently running into an issue where the structure of my object is not conducive with what is expected by Entity Framework Core (v7), as my model has an interface as a property. I’m wondering if there is a better approach to achieve what I am trying to do.
An entity with an interface property – is there a better approach when using Entity Framework Core?
I’m currently running into an issue where the structure of my object is not conducive with what is expected by Entity Framework Core (v7), as my model has an interface as a property. I’m wondering if there is a better approach to achieve what I am trying to do.
Save a lot of notes in the database with Entity Framework Core [closed]
Closed 3 days ago.
Resolving an entity from a SQL query in EF Core
I have added an entity which resolves from a SQL query like this. This entity is owned/managed by some other DbContext and I just use it as a data reference. No updates/deletes or DDL will be created from my app for this entity.
Save a lot of notes in the database with Entity Framework Core [closed]
Closed 3 days ago.
Entity framework navigation properties remain null until saving to database
Say I have a basic example of a data tree to save in the database:
Entity Framework Core : nullable FK update child issue
Some question has not group so I set FK as a optional field. When I am trying to update group, I get an error. If GroupId is required, then there is no problem.
Entity Framework Core : nullable FK update child issue
Some question has not group so I set FK as a optional field. When I am trying to update group, I get an error. If GroupId is required, then there is no problem.
Override Entity Framework Core circular dependency
I have the table structure (simplified):
EF Core: Looking for non existent column?
EDIT: Issue doesn’t exist if I remove RelatedItems property.