Search Results

I'm importing data from older website to new one using database migrations. I have created first as one of first steps of development phase of new site. … I.e. the one, that updates migration table in database at the end of migration process, changes its own timestamp and thus forces migration system to "think", that there's always a new migration to be …

Either: Change all live writers to write new data to both locations Do a one-time migration of data from the old location to the new location Change all readers to read data from only the new location … writing new data to the old location or: Change all readers to read data from both locations, preferring the new location Change all writers to write new data to only the new location Do a one-time migration …

The database schema is manually updated without any sort of migration script, hence I want to introduce a database migration schemes. … This single migration will generate the existing database schema from a database dump. After that each change on the database will be placed upon a new migration script. …

I have used migration tools with Yii & Laravel in the past, but those tools aren't available as I'm using the old Zend Framework. … In a nutshell, I am looking for a solution that will allow all of my colleagues to be able to do the following: Use some form of database migration tool (supporting MySQL) to add/edit/remove tables and …

I have inherited a project via laravel that uses its database migration mechanism coming from the framework. … script: use Illuminate\Support\Facades\Schema; use Illuminate\Database\Schema\Blueprint; use Illuminate\Database\Migrations\Migration; class ActionAwardee extends Migration { /** * Run the migrations …

I have received the task to follow and take care of the whole data migration. … Technically it is everything clear, but I have to describe in a "proof of concept" the migration process. About data migration is there a general pattern that could be used to describe it? …

class Hero(Model): power = CharField(max_length=30, validators=[validate_power]) In the migration file, there will be: file web/migrations/0001_initial.py class Migration(migrations.Migration): … code, and that could be many files, and also changing migration code should not be needed). …

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. … While I understand how to do operations with regular expressions in non-database issues, my database experience isn't robust enough to know the best way to handle this. …

I was reading an old answer which was recently updated, and noticed that the author doesn't quote the simplicity of data migration as a benefit of MongoDB. … Am I missing something about the data migration in MongoDB compared to the data migration in most popular relational databases? Or is the simplicity of data migration still a huge benefit of MongoDB? …

in the database. … So I was thinking what if I roll back the database to the very first state, remove all migrations and then generate a new one, which will do only nessesary actions to bring a database to it's final state …

How do you handle migrations to your database after a long period of time? … The closest I've seen is someone doing a sort of "rebase", where they delete the migration version table, and generate new SQL scripts from a database backup tool and call it version "0" from then on. …

Idea A migration is a (name, up action, down action). … I'm open to other solutions provided they automatically detect or resolve migration conflicts and are simple. …

The normal answer to that is migration files, and we are already using the migration function of laravel. Soon, we find that some old project takes a long time in running the migration file. … Some columns that no longer exists in the latest version are still added and then deleted when running the migration file. Is there a way to do database version control in a better way? …

Resulting, customers from company B will need to be migrated to company A customer database, so that they can enjoy seamless experience by logging into app from A. … So, the question is more towards strategies that are followed to do customer data migration in such cases. …

My gut feeling is that a fresh install should create the database "as it is", not go through every mistake that was made in the product lifecycle until reaching a stable condition. … The above scenario is just an example, but I'm interested in arguments about the general case: have fresh installs create the database as it is, or go through every migration ever done in the product lifecycle …