"Problem Description:
I'm looking forward to [StoreIgnore] attribute in EF 4 CTP 5. I would like to see a way to create index in table. Something like: [Indexed(Unique=false,Clustered=false)] int A { get; set; } [Indexed(Unique=false,Clustered=false)] int B { get; set; } [Indexed(Unique=false,Clustered=false)] int C { get; set; }"
This item was migrated from the DevDiv work item tracking system [ID=87553].
This work item originated from connect.microsoft.com. A member of the EF team at Microsoft should close the related Connect issue when closing this work item.
Comments: @RoMiller I don't know if I'm misunderstanding, but what is the point in changing the schema in a migration, but not representing that as an attribute or using the Fluent API when creating the model? Surely that means that the schema change will not be applied when the database is created from scratch (like on a new install of SQL Server).
I'm looking forward to [StoreIgnore] attribute in EF 4 CTP 5. I would like to see a way to create index in table. Something like: [Indexed(Unique=false,Clustered=false)] int A { get; set; } [Indexed(Unique=false,Clustered=false)] int B { get; set; } [Indexed(Unique=false,Clustered=false)] int C { get; set; }"
This item was migrated from the DevDiv work item tracking system [ID=87553].
This work item originated from connect.microsoft.com. A member of the EF team at Microsoft should close the related Connect issue when closing this work item.
Comments: @RoMiller I don't know if I'm misunderstanding, but what is the point in changing the schema in a migration, but not representing that as an attribute or using the Fluent API when creating the model? Surely that means that the schema change will not be applied when the database is created from scratch (like on a new install of SQL Server).