Arthur Vickers

Note from triage: consider as part of #1985

@BBGONE The methods like `GetDatabaseValues`, `SetValues` etc work on a single entity instance. Since the owned type is really just an entity type, these methods need to be called both...

@s8moahme `HouseNumber` is configured has a generated property with `[DatabaseGenerated(DatabaseGeneratedOption.Identity)]`. For generated properties configured in this way, EF will leave it up to the database to generate a value unless...

Note from triage: attempt to warn in this case that there is no mechanism in the database to generate the default value.

@aligunel `JsonIgnore` is an attribute used by the JSon serializer; it does not change the EF model. `NotMapped` can be used to exclude a property from the EF model.

@aligunel I don't think that is supported.

@erdalsivri We use votes (👍) on issues as a rough measure of customer demand for issues, which then feeds into the [planning process](https://docs.microsoft.com/en-us/ef/core/what-is-new/release-planning). This issue doesn't have any votes, which...

@roji Agreed we should change this, but will the change be breaking for no-tracking queries where multiple objects with the same primary key value can be returned?

@IlyaNavodkin In the link posed above it states, "If you customize the Migrations history table after applying migrations, you are responsible for updating the existing table in the database." However,...

**EF Team Triage:** Closing this issue as the requested additional details have not been provided and we have been unable to reproduce it. *BTW this is a canned response and...