Big switching from one platform to another [closed]
Closed 11 years ago.
Big switching from one platform to another [closed]
Closed 11 years ago.
Big switching from one platform to another [closed]
Closed 11 years ago.
Big switching from one platform to another [closed]
Closed 11 years ago.
Big switching from one platform to another [closed]
Closed 11 years ago.
Handling changes to data types and entries in a database migration
I’m fully redesigning a site that indexes a number of articles with basic search functionality. The previous site was written about a decade ago, and I’m salvaging about 30,000 entries with data stored in less-than-ideal formats. While I’m moving from MSSQL to MySQL, I don’t need to make any “live” changes, so this is not a production-level migration issue so much as a redesign.
Handling changes to data types and entries in a database migration
I’m fully redesigning a site that indexes a number of articles with basic search functionality. The previous site was written about a decade ago, and I’m salvaging about 30,000 entries with data stored in less-than-ideal formats. While I’m moving from MSSQL to MySQL, I don’t need to make any “live” changes, so this is not a production-level migration issue so much as a redesign.
Migration pattern for logic too complex to cover it with SQL
When you create migration in EF Core you can spice it up with arbitrary SQL query. Yet there is a limit to it — maybe the migration is too complex in technical sense (i.e the SQL cannot handle it) or in readability sense (expressing the logic in SQL is too muddy). In short when migration logic can be only expressed in regular EF Core C# code with queries, filters, loops, ifs, etc.
How should the database schema be migrated?
I am using a bunch of freelance programmers to develop a web application. We are in the early stages of development, meaning that we are making many changes to our database schema. We have one test database and one production database, we also have a replica of the live database, which gets a clone of the live database every night (mostly used to make it easier to recreate bugs found in the live web application. Since I use many freelancers, which I do not know, I often do not trust their database skills and they do not have any understanding of the outmost importance of the data in our live database.
How should the database schema be migrated?
I am using a bunch of freelance programmers to develop a web application. We are in the early stages of development, meaning that we are making many changes to our database schema. We have one test database and one production database, we also have a replica of the live database, which gets a clone of the live database every night (mostly used to make it easier to recreate bugs found in the live web application. Since I use many freelancers, which I do not know, I often do not trust their database skills and they do not have any understanding of the outmost importance of the data in our live database.