database-migration

I came across a problem where I was working on two branches on a rails project and each project has a migration to add a column. At the time, rake db:migrate:reset cause a problem and I solely relied on my schema.rb to correctly represent the state of my database. At one point, I came across a problem where a column added by branch A got into the schema of branch B. Since migrate:reset was not an option, I resorted to manually editing the schema file to. I committed this change that basically deleted the column from branch A that I did not need in branch B's schema.rb. Problem came after I

This is a long question, but I would be very very thankful if I can get some good advice on this. In short, I’m looking for a good approach for version upgrade of MS SQL database schema that also demands data being moved from deleted tables into new tables. I think Stack Overflow is the most appropriate place for this question (not dba.stackexchange.com) because at its core, this is an issue for .NET developers using Entity Framework, and the database parts of this consists mostly of auto-generated sql scripts. Background A .NET application and SQL database is running in Azure (The application

I have a django migration I am trying to apply. It gets made fine (it's small, it's only adding a CharField to two different Models. However when I run the actual migrate it hangs (no failure, no success, just sits). Through googling I've found that other open connections can mess with it so I restarted the DB. However this DB is connect to continuously running jobs and new queries do sneak in right away. However they are small, and last time I tried restarting I THINK I was able to execute my migrate before anything else. Still nothing. Are there any other known issues that cause something

I want to create a table in Laravel Migration like this- CREATE TABLE Payroll ( ID int PRIMARY KEY, PositionID INT, Salary decimal(9,2) CHECK (Salary < 150000.00) ); What I have done is- Schema::create('Payroll', function (Blueprint $table) { $table->increments('id'); $table->integer('PositionID '); $table->decimal('Salary',9,2); //$table->timestamps(); }); But I can't create this- CHECK (Salary < 150000.00) Can anyone please tell, how to implement this CHECK constraints in Laravel Migration ? Adding constraints is not supported by the Blueprint class (at least as of Laravel 5.3), however it

I'm using Django ( < v1.7), with SQLite3 as the database engine. I am trying to add a new field to an already existing model's class. This class already has data associated to it. manage.py syncdb is not adding the new fields to the db. Is there was a way to: Add the new Field to the already existing class, and make sure a db entry is allocated to it? Populate this new field with an empty string for all the already existing db entries? Install south in your django and you can easily handle the existing tables. check this If you really want to use Django-South, install it on your django, after

I have a docker container running MySQL-5.5 with host data volume. I am upgrading my container to MySQL-5.6. I am starting a new container with the same host volume. MySQL was crashing in the container due to the crash of mysql.user table. [ERROR] Fatal error: Can't open and lock privilege tables: Incorrect key file for table 'user'; try to repair it 160523 12:04:13 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended I tried the following to fix that: root@container# mysqld --skip-grant-tables; root@container# mysql -uroot -ppassword mysql> repair table user USE_FRM; +-----------