Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Save migration info in separate DB schema

+2
−0

When creating a code-first solution in dot net core using Visual Studio, you manipulate the database by changing model classes and migrating the changes.

I can set the schema for tables that I create, but how do I set a schema for the migration table itself? Currently it defaults to 'dbo'. Is it even possible? Unlike my model classes that become tables, there is no correlating migrations table class that I can add data annotations to provide the schema name.

Edit: To be clear, I'm talking about the table __EFMigrationsHistory that is created when first running Update-Database in the package manager console.

An answer implies I could change the default schema used, but the schema for the migration table isn't the default schema for the solution so I'd prefer not to.

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

1 answer

+2
−0

If you want to use a custom entity framework migration table, you can set it when configuring the database context as shown here:

// this code belong to the database context class
protected override void OnConfiguring(DbContextOptionsBuilder options)
    => options.UseSqlServer(
        _connectionString,
        x => x.MigrationsHistoryTable("TheMigrations", "meta"));

You are getting dbo schema for the created table, because this is the default schema for your login (used in the database connection string). There are two ways to configure the schema in a code-first project:

1. Using `TableAttribute`: `[Table(Schema="custom")] as indicated [here](https://www.entityframeworktutorial.net/code-first/table-dataannotations-attribute-in-code-first.aspx).
  1. Using fluent API: modelBuilder.HasDefaultSchema("custom"); as indicated here.
Personally, I prefer to use data annotations (attributes) whenever possible (you can easily see the configuration by looking at the model, but not all configurations can be done like this), but some prefer the fluent API because it allows a separation between the schema itself and its configuration (keys, constraints, indexes, etc.).
History
Why does this post require moderator attention?
You might want to add some details to your flag.

1 comment thread

General comments (1 comment)

Sign up to answer this question »