Ignoring migrations for one schema only with Entity Framework 6
I'm trying to do something using EF that I feel should be simple, but I can't work out exactly how to do it.
Let's say we have a core ASP.NET web app whose data lives on the dbo schema in our database. We then want to add an optional module whose data lives on the opt schema that we can enable based on some business needs.
The optional module will need data from the main schema- it's an extension of the functionality found in there. To make this painless, it'd be nice to have a seamless experience using LINQ.
The working prototype I have currently is an inheritance relation OptionalDataContext : CoreDataContext. CoreDataContext is used to access and modify existing data.
Let's say I want to just add the one table to the opt schema for now: DbSet<OptionalClass> OptionalClasses. It gets put on a property of the OptionalDataContext. Optional class looks like
[Table(Name="OptionalClasses", Schema="opt")]
OptionalClass {
public int Id {get; set;}
public string OptionalData {get; set;}
public virtual CoreAppClass CoreData {Get; set}
}
in which the virtual property points to a table dbo.CoreAppClasses.
Now, the setup we have, after a hacky start, allows my one context to freely perform LINQ joins and queries across the two schema. If the CoreAppClass in turn has virtual properties, I can access these with chained Include statements. This is great.
The issue I have is when I scaffold the optional app's initial migration, it tries to create every existing table in the dbo schema, but these already exist.
I can use -IgnoreChanges to generate the first migration after commenting out the optional context's one DbSet, then add my optional DbSet in, and carry on from there, but this means whenever someone updates the core app's database schema, we would need to run what's essentially a merge migration in the optional app.
Is there a simple solution to make it so that adding migrations basically has the -IgnoreChanges command for the Core part of this new OptionalDataContext only?
Using modelbuilder.Ignore() for every single core property is not viable- this is just more maintenance issues. I want to set some configuration so that these migrations will merely update the EF model snapshot for any changes to dbo tables, but to scaffold migrations for all opt changes.
c# entity-framework entity-framework-6
asked Nov 14 '18 at 11:04
Luke WLuke W
12
add a comment |
I'm trying to do something using EF that I feel should be simple, but I can't work out exactly how to do it.
Let's say we have a core ASP.NET web app whose data lives on the dbo schema in our database. We then want to add an optional module whose data lives on the opt schema that we can enable based on some business needs.
The optional module will need data from the main schema- it's an extension of the functionality found in there. To make this painless, it'd be nice to have a seamless experience using LINQ.
The working prototype I have currently is an inheritance relation OptionalDataContext : CoreDataContext. CoreDataContext is used to access and modify existing data.
Let's say I want to just add the one table to the opt schema for now: DbSet<OptionalClass> OptionalClasses. It gets put on a property of the OptionalDataContext. Optional class looks like
[Table(Name="OptionalClasses", Schema="opt")]
OptionalClass {
public int Id {get; set;}
public string OptionalData {get; set;}
public virtual CoreAppClass CoreData {Get; set}
}
in which the virtual property points to a table dbo.CoreAppClasses.
Now, the setup we have, after a hacky start, allows my one context to freely perform LINQ joins and queries across the two schema. If the CoreAppClass in turn has virtual properties, I can access these with chained Include statements. This is great.
The issue I have is when I scaffold the optional app's initial migration, it tries to create every existing table in the dbo schema, but these already exist.
I can use -IgnoreChanges to generate the first migration after commenting out the optional context's one DbSet, then add my optional DbSet in, and carry on from there, but this means whenever someone updates the core app's database schema, we would need to run what's essentially a merge migration in the optional app.
Is there a simple solution to make it so that adding migrations basically has the -IgnoreChanges command for the Core part of this new OptionalDataContext only?
Using modelbuilder.Ignore() for every single core property is not viable- this is just more maintenance issues. I want to set some configuration so that these migrations will merely update the EF model snapshot for any changes to dbo tables, but to scaffold migrations for all opt changes.
c# entity-framework entity-framework-6
asked Nov 14 '18 at 11:04
Luke WLuke W
12
add a comment |
I'm trying to do something using EF that I feel should be simple, but I can't work out exactly how to do it.
Let's say we have a core ASP.NET web app whose data lives on the dbo schema in our database. We then want to add an optional module whose data lives on the opt schema that we can enable based on some business needs.
The optional module will need data from the main schema- it's an extension of the functionality found in there. To make this painless, it'd be nice to have a seamless experience using LINQ.
The working prototype I have currently is an inheritance relation OptionalDataContext : CoreDataContext. CoreDataContext is used to access and modify existing data.
Let's say I want to just add the one table to the opt schema for now: DbSet<OptionalClass> OptionalClasses. It gets put on a property of the OptionalDataContext. Optional class looks like
[Table(Name="OptionalClasses", Schema="opt")]
OptionalClass {
public int Id {get; set;}
public string OptionalData {get; set;}
public virtual CoreAppClass CoreData {Get; set}
}
in which the virtual property points to a table dbo.CoreAppClasses.
Now, the setup we have, after a hacky start, allows my one context to freely perform LINQ joins and queries across the two schema. If the CoreAppClass in turn has virtual properties, I can access these with chained Include statements. This is great.
The issue I have is when I scaffold the optional app's initial migration, it tries to create every existing table in the dbo schema, but these already exist.
I can use -IgnoreChanges to generate the first migration after commenting out the optional context's one DbSet, then add my optional DbSet in, and carry on from there, but this means whenever someone updates the core app's database schema, we would need to run what's essentially a merge migration in the optional app.
Is there a simple solution to make it so that adding migrations basically has the -IgnoreChanges command for the Core part of this new OptionalDataContext only?
Using modelbuilder.Ignore() for every single core property is not viable- this is just more maintenance issues. I want to set some configuration so that these migrations will merely update the EF model snapshot for any changes to dbo tables, but to scaffold migrations for all opt changes.
c# entity-framework entity-framework-6
asked Nov 14 '18 at 11:04
Luke WLuke W
12
I'm trying to do something using EF that I feel should be simple, but I can't work out exactly how to do it.
Let's say we have a core ASP.NET web app whose data lives on the dbo schema in our database. We then want to add an optional module whose data lives on the opt schema that we can enable based on some business needs.
The optional module will need data from the main schema- it's an extension of the functionality found in there. To make this painless, it'd be nice to have a seamless experience using LINQ.
The working prototype I have currently is an inheritance relation OptionalDataContext : CoreDataContext. CoreDataContext is used to access and modify existing data.
Let's say I want to just add the one table to the opt schema for now: DbSet<OptionalClass> OptionalClasses. It gets put on a property of the OptionalDataContext. Optional class looks like
[Table(Name="OptionalClasses", Schema="opt")]
OptionalClass {
public int Id {get; set;}
public string OptionalData {get; set;}
public virtual CoreAppClass CoreData {Get; set}
}
in which the virtual property points to a table dbo.CoreAppClasses.
Now, the setup we have, after a hacky start, allows my one context to freely perform LINQ joins and queries across the two schema. If the CoreAppClass in turn has virtual properties, I can access these with chained Include statements. This is great.
The issue I have is when I scaffold the optional app's initial migration, it tries to create every existing table in the dbo schema, but these already exist.
I can use -IgnoreChanges to generate the first migration after commenting out the optional context's one DbSet, then add my optional DbSet in, and carry on from there, but this means whenever someone updates the core app's database schema, we would need to run what's essentially a merge migration in the optional app.
Is there a simple solution to make it so that adding migrations basically has the -IgnoreChanges command for the Core part of this new OptionalDataContext only?
Using modelbuilder.Ignore() for every single core property is not viable- this is just more maintenance issues. I want to set some configuration so that these migrations will merely update the EF model snapshot for any changes to dbo tables, but to scaffold migrations for all opt changes.
c# entity-framework entity-framework-6
c# entity-framework entity-framework-6
asked Nov 14 '18 at 11:04
Luke WLuke W
12
asked Nov 14 '18 at 11:04
Luke WLuke W
12
asked Nov 14 '18 at 11:04
Luke WLuke W
12
asked Nov 14 '18 at 11:04
Luke WLuke W
12
asked Nov 14 '18 at 11:04
Luke WLuke W
12
12
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53298717%2fignoring-migrations-for-one-schema-only-with-entity-framework-6%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53298717%2fignoring-migrations-for-one-schema-only-with-entity-framework-6%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
