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.

Post History

66%
+2 −0
Q&A Save migration info in separate DB schema

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 cre...

1 answer  ·  posted 3y ago by mcalex‭  ·  last activity 3y ago by Alexei‭

#2: Post edited by user avatar mcalex‭ · 2021-05-01T09:35:57Z (over 3 years ago)
  • 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 this even possible?
  • 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.
#1: Initial revision by user avatar mcalex‭ · 2021-04-30T09:44:11Z (over 3 years ago)
Save migration info in separate DB schema
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 this even possible?