{"push_id":1003185903,"size":2,"distinct_size":1,"ref":"refs/heads/TablusNamus0301","head":"f6552096f5a861eb17638e0731d1cf212157b159","before":"8a6728c1256fa49122f7707b94dcef8aaa52a672","commits":[{"sha":"ea4ec9223077d4c56ffabf9db4155c4f0e5af928","author":{"email":"7fcf9ee3bd99ae911d41c7f75dcf8235b5e580f8@hotmail.com","name":"Arthur Vickers"},"message":"Better handling for shadow FKs on attach, and general cleanup of change detection and fixup\n\nChangeDetector is now only responsible for detecting changes. It doesn't do any updating of state. NavigationFixter does all update of state that happens when a property or navigation changes, or when an entity is initially tracked, and is responsible for keeping the snapshots and dependent maps in sync.\n\nWe now no longer set properties (e.g. FKs, navigations) on entities that are not yet tracked. Instead we keep a side dictionary of these entities and do any necessary fixup when the entity is ultimately tracked.\n\nThis makes our behavior more consistent as to when we set modified or not. In particular, if an entity with a shadow state property is attached, then we will set its FK based on navigation values and the resulting entity will not be marked as modified. We also do the same thing now for non shadow state properties to be consistent.\n\nThe dependent map handles conceptually null FKs, although this could be optimized.","distinct":false,"url":"https://api.github.com/repos/aspnet/EntityFramework/commits/ea4ec9223077d4c56ffabf9db4155c4f0e5af928"},{"sha":"f6552096f5a861eb17638e0731d1cf212157b159","author":{"email":"7fcf9ee3bd99ae911d41c7f75dcf8235b5e580f8@hotmail.com","name":"Arthur Vickers"},"message":"Use DbSet property name as table names\n\nIssue #4540\n\nThe DbSet property name from the context is used as the name of the table mapped to by that entity type.\n\nIf the table name is specified explicitly with ToTable, then this is used instead.\n\nThe entity type name is used as the table name for entity types in the model that do not have a corresponding DbSet property. If there is more than one DbSet property for the same entity type, then we fall back to using the entity type name.","distinct":true,"url":"https://api.github.com/repos/aspnet/EntityFramework/commits/f6552096f5a861eb17638e0731d1cf212157b159"}]}