29 votes9 comments · [Closed] Entity Framework Core Feature Suggestions · Flag idea as inappropriate… · Admin →
When we originally marked this issue as completed we did not take into consideration the ability to ignore certain tables in migrations for overlapping models.
This is still not supported in EF Core (or in EF6)Gordon commented
All that is needed is another 'ApplicationId' column like in ASP.Net memberships, simple !
Or use separate db schemas per Application / DB Context.
Setting a default schema name should actually be a lot simpler than it currently is.Gordon commented
This would be great for hosting websites at places like GoDaddy, where you just have to make do with 1 or 2 MS SQL databases.
Without it you cannot use Code-first for more than 1 website. :-(Gordon supported this idea ·