This looks like a really common task, but I can&#39;t find an easy way to do it. 

I want to undo the last applied migration. I would have expected a simple command, like 

    PM&gt; Update-Database -TargetMigration:&quot;-1&quot;

Instead, all I can come up with is:

    PM&gt; Get-Migrations

    Retrieving migrations that have been applied to the target database.
    201208012131302_Add-SystemCategory
    201207311827468_CategoryIdIsLong
    201207232247409_AutomaticMigration
    201207211340509_AutomaticMigration
    201207200025294_InitialCreate

    PM&gt; Update-Database -TargetMigration:&quot;CategoryIdIsLong&quot;

(At least I can use just the name, skipping the timestamp...)

Is there an easier way?

EF Migrations: Rollback last applied migration?

# I want 
to rollback only : 

`Rolled back: 2015_05_15_195423_alter_table_web_directories`

___

# I run 

`php artisan migrate:rollback`, 3 of my migration are rolling back. 
 
    Rolled back: 2015_05_15_195423_alter_table_web_directories
    Rolled back: 2015_05_13_135240_create_web_directories_table
    Rolled back: 2015_05_13_134411_create_contacts_table

___

# I delete

both of my `web_directories` and my `contacts` table unintentionally. I never want that to happen, and if I can rollback only that specific one, this disaster will never happen.


Rollback one specific migration in Laravel

I&#39;ve mucked up my migrations, I used `IgnoreChanges` on the initial migration, but now I want to delete all my migrations and start with an initial migration with all of the logic.

When I delete the migrations in the folder and try and `Add-Migration` it doesn&#39;t generate a full file (it&#39;s empty - because I haven&#39;t made any changes since my last, but now deleted, migration).

Is there any *Disable-Migrations* command, so I can rerun `Enable-Migrations`?

Reset Entity-Framework Migrations

Does anyone know how I can copy a SQL Azure database to my development machine? I&#39;d like to stop paying to have a development database in the cloud, but it&#39;s the best way to get production data. I copy my production database to a new development database but I&#39;d like to have that same database local. 

Any suggestions? 

How do I copy SQL Azure database to my local development server?

I currently have a live redis server running on a cloud instance and I want to migrate this redis server to a new cloud instance and use that instance as my new redis server. If it were MySQL, I would export the DB from the old server and import it into the new server. How should I do this with redis? 

P.S.: I&#39;m not looking to set-up replication. I want to completely migrate the redis server to a new instance.

How do I move a redis database from one server to another?

I&#39;m on a Mac OS Yosemite using Laravel 5.0.

While in my **local** environment, I run `php artisan migrate` I keep getting : 
 


&gt; Access denied for user &#39;homestead&#39;@&#39;localhost&#39; (using password: YES)


**Configuration** 

Here is my **.env** 

    APP_ENV=local
    APP_DEBUG=true
    APP_KEY=*****
    
    DB_HOST=localhost
    DB_DATABASE=homestead
    DB_USERNAME=homestead
    DB_PASSWORD=secret
   

**app\config\database.php** 


       &#39;mysql&#39;       =&gt; [
        &#39;driver&#39;      =&gt; &#39;mysql&#39;,
        &#39;host&#39;        =&gt; env(&#39;DB_HOST&#39;, &#39;localhost&#39;),
        &#39;database&#39;    =&gt; env(&#39;DB_DATABASE&#39;, &#39;homestead&#39;),
        &#39;username&#39;    =&gt; env(&#39;DB_USERNAME&#39;, &#39;homestead&#39;),
        &#39;password&#39;    =&gt; env(&#39;DB_PASSWORD&#39;, &#39;secret&#39;),
        &#39;unix_socket&#39; =&gt; &#39;/tmp/mysql.sock&#39;,
        &#39;charset&#39;     =&gt; &#39;utf8&#39;,
        &#39;collation&#39;   =&gt; &#39;utf8_unicode_ci&#39;,
        &#39;prefix&#39;      =&gt; &#39;&#39;,
        &#39;strict&#39;      =&gt; false,
        ]


How do I avoid this kind of error ?

**I&#39;ve tried :** 
_____

# 1



in **app/database.php**

Replace `localhost` with `127.0.0.1`


`&#39;host&#39;=&gt; env(&#39;DB_HOST&#39;, &#39;localhost&#39;)` --&gt;`&#39;host&#39; =&gt; env(&#39;DB_HOST&#39;, &#39;127.0.0.1&#39;)`

Also, in **.env**

`DB_HOST=localhost`  --&gt; `DB_HOST=127.0.0.1`



____


# 2

Try specify environment

`php artisan migrate --env=local`

____


# 3

Check to see if the MySQL is running by run 

`mysqladmin -u homestead -p status Enter password: secret`

 I got 

`Uptime: 21281 Threads: 3 Questions: 274 Slow queries: 0 Opens: 327 Flush tables: 1 Open tables: 80 Queries per second avg: 0.012`

Which mean it&#39;s running.

____

# 4

Check MySQL UNIX Socket (*This step work for me*)

  [1]: http://i.stack.imgur.com/Yqxns.png

Access denied for user &#39;homestead&#39;@&#39;localhost&#39; (using password: YES)

I&#39;m writing a migration to make certain columns in a table `nullable` right now. For the down function, I of course want to make those columns `not nullable` again. I looked through the [schema builder docs](http://laravel.com/docs/database/schema), but couldn&#39;t see a way to do this. 

Any help would be appreciated.

Make column not nullable in a Laravel migration

I&#39;m close to having my project ready to launch. I have big plans for after launch and the database structure is going to change -- new columns in existing tables as well as new tables, and new associations to existing and new models.

I haven&#39;t touched migrations in Sequelize yet, since I&#39;ve only had testing data which I don&#39;t mind wiping out every time the database changes.

To that end, at present I&#39;m running `sync force: true` when my app starts up, if I have changed the model definitions. This deletes all the tables and makes them from scratch. I could omit the `force` option to have it only create new tables. But if existing ones have changed this is not useful.

So once I add in migrations how do things work? Obviously I don&#39;t want existing tables (with data in them) to be wiped out, so `sync force: true` is out of the question. On other apps I&#39;ve helped develop (Laravel and other frameworks) as part of the app&#39;s deployment procedure we run the migrate command to run any pending migrations. But in these apps the very first migration has a skeleton database, with the database in the state where it was some time early in development -- the first alpha release or whatever. So even an instance of the app late to the party can get up to speed in one go, by running all migrations in sequence.

How do I generate such a &quot;first migration&quot; in Sequelize? If I don&#39;t have one, a new instance of the app some way down the line will either have no skeleton database to run the migrations on, or it will run sync at the start and will make the database in the new state with all the new tables etc, but then when it tries to run the migrations they won&#39;t make sense, since they were written with the original database and each successive iteration in mind.

My thought process: at every stage, the initial database plus each migration in sequence should equal (plus or minus data) the database generated when `sync force: true` is run. This is because the model descriptions in the code describe the database structure. So maybe if there is no migration table we just run sync and mark all the migrations as done, even though they weren&#39;t run. Is this what I need to do (how?), or is Sequelize supposed to do this itself, or am I barking up the wrong tree? And if I&#39;m in the right area, surely there should be a nice way to auto generate most of a migration, given the old models (by commit hash? or even could each migration be tied to a commit? I concede I am thinking in a non-portable git-centric universe) and the new models. It can diff the structure and generate the commands needed to transform the database from old to new, and back, and then the developer can go in and make any necessary tweaks (deleting/transitioning particular data etc).

When I run the sequelize binary with the `--init` command it gives me an empty migrations directory. When I then run `sequelize --migrate` it makes me a SequelizeMeta table with nothing in it, no other tables. Obviously not, because that binary doesn&#39;t know how to bootstrap my app and load the models.

I must be missing something.

TLDR: how do I set up my app and its migrations so various instances of the live app can be brought up to date, as well as a brand new app with no legacy starting database?

Sequelize.js: how to use migrations and sync

I have a table in a Rails application which (in schema.rb) looks like:

    create_table &quot;users&quot;, :force =&gt; true do |t|
       t.string &quot;name&quot;, :null=&gt;false
       t.string &quot;address&quot;, :null=&gt;false
    end

I would like to write a rails migration to allow nulls for the address field. i.e. after the migration the table looks like this:

    create_table &quot;users&quot;, :force =&gt; true do |t|
       t.string &quot;name&quot;, :null=&gt;false
       t.string &quot;address&quot;
    end

What do I need to do to remove the constraint?



Rails Migration: Remove constraint

When I run `python manage.py migrate` on my Django project, I get the following error:

    Traceback (most recent call last):
    File &quot;manage.py&quot;, line 22, in &lt;module&gt;
    execute_from_command_line(sys.argv)
    File &quot;/home/hari/project/env/local/lib/python2.7/site-     packages/django/core/management/__init__.py&quot;, line 363, in execute_from_command_line
    utility.execute()
    File &quot;/home/hari/project/env/local/lib/python2.7/site-packages/django/core/management/__init__.py&quot;, line 355, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
    File &quot;/home/hari/project/env/local/lib/python2.7/site-packages/django/core/management/base.py&quot;, line 283, in run_from_argv
    self.execute(*args, **cmd_options)
    File &quot;/home/hari/project/env/local/lib/python2.7/site-packages/django/core/management/base.py&quot;, line 330, in execute
    output = self.handle(*args, **options)
    File &quot;/home/hari/project/env/local/lib/python2.7/site-packages/django/core/management/commands/migrate.py&quot;, line 86, in handle
    executor.loader.check_consistent_history(connection)
    File &quot;/home/hari/project/env/local/lib/python2.7/site-packages/django/db/migrations/loader.py&quot;, line 298, in check_consistent_history
    connection.alias,
    django.db.migrations.exceptions.InconsistentMigrationHistory: Migration admin.0001_initial is applied before its dependency account.0001_initial on database &#39;default&#39;.

I have a user model like below:

    class User(AbstractUser):
        place = models.CharField(max_length=64, null=True, blank=True)
        address = models.CharField(max_length=128, null=True, blank=True)
   

How can I solve this problem?

django.db.migrations.exceptions.InconsistentMigrationHistory

Let&#39;t assume, I have a simple Room database:

    @Database(entities = {User.class}, version = 1)
    abstract class AppDatabase extends RoomDatabase {
        public abstract Dao getDao();
    }

Now, I&#39;m adding a new entity: `Pet` and bumping version to 2:

    @Database(entities = {User.class, Pet.class}, version = 2)
    abstract class AppDatabase extends RoomDatabase {
        public abstract Dao getDao();
    }

Of course, Room throws an exception: `java.lang.IllegalStateException: A migration from 1 to 2 is necessary.`

Assuming, I haven&#39;t changed `User` class (so all data is safe), I have to provide migration which just creates a new table. So, I&#39;m looking into classes generated by Room, searching for generated query to create my new table, copying it and pasting into migration:

    final Migration MIGRATION_1_2 =
            new Migration(1, 2) {
                @Override
                public void migrate(@NonNull final SupportSQLiteDatabase database) {
                    database.execSQL(&quot;CREATE TABLE IF NOT EXISTS `Pet` (`name` TEXT NOT NULL, PRIMARY KEY(`name`))&quot;);
                }
            };

However I find it inconvenient to do it manually.
Is there a way to tell Room: *I&#39;m not touching any of the existing table, so data is safe. Please create migration for me?*

Room database migration if only new table is added

How do I enable Entity Framework 5 (version 5.0.0) migrations for multiple DB contexts in the same project, where each context corresponds to its own database? When I run `Enable-Migrations` in the PM console (Visual Studio 2012), there&#39;s an error because of there being multiple contexts:

    PM&gt; Enable-Migrations
    More than one context type was found in the assembly &#39;DatabaseService&#39;.
    To enable migrations for DatabaseService.Models.Product1DbContext, use Enable-Migrations -ContextTypeName DatabaseService.Models.Product1DbContext.
    To enable migrations for DatabaseService.Models.Product2DbContext, use Enable-Migrations -ContextTypeName DatabaseService.Models.Product2DbContext.

If I run `Enable-Migrations -ContextTypeName DatabaseService.Models.Product1DbContext` I&#39;m not allowed to run `Enable-Migrations -ContextTypeName DatabaseService.Models.Product2DbContext` because a migration already exists: `Migrations have already been enabled in project &#39;DatabaseService&#39;. To overwrite the existing migrations configuration, use the -Force parameter.`

How do I enable EF migrations for multiple contexts to separate databases?

I&#39;ve created a table using migration like this:

    public function up()
    {
        Schema::create(&#39;despatch_discrepancies&#39;,  function($table) {
            $table-&gt;increments(&#39;id&#39;)-&gt;unsigned();
            $table-&gt;integer(&#39;pick_id&#39;)-&gt;unsigned();
            $table-&gt;foreign(&#39;pick_id&#39;)-&gt;references(&#39;id&#39;)-&gt;on(&#39;picks&#39;);
            $table-&gt;integer(&#39;pick_detail_id&#39;)-&gt;unsigned();
            $table-&gt;foreign(&#39;pick_detail_id&#39;)-&gt;references(&#39;id&#39;)-&gt;on(&#39;pick_details&#39;);
            $table-&gt;integer(&#39;original_qty&#39;)-&gt;unsigned();
            $table-&gt;integer(&#39;shipped_qty&#39;)-&gt;unsigned();
        });
    }
    
    public function down()
    {
        Schema::drop(&#39;despatch_discrepancies&#39;);
    }

I need to change this table and drop the foreign key reference &amp; column `pick_detail_id` and add a new varchar column called `sku` after `pick_id` column.

So, I&#39;ve created another migration, which looks like this:

	public function up()
	{
		Schema::table(&#39;despatch_discrepancies&#39;, function($table)
		{
			$table-&gt;dropForeign(&#39;pick_detail_id&#39;);
			$table-&gt;dropColumn(&#39;pick_detail_id&#39;);
			$table-&gt;string(&#39;sku&#39;, 20)-&gt;after(&#39;pick_id&#39;);
		});
	}

	public function down()
	{
		Schema::table(&#39;despatch_discrepancies&#39;, function($table)
		{
			$table-&gt;integer(&#39;pick_detail_id&#39;)-&gt;unsigned();
            $table-&gt;foreign(&#39;pick_detail_id&#39;)-&gt;references(&#39;id&#39;)-&gt;on(&#39;pick_details&#39;);
            $table-&gt;dropColumn(&#39;sku&#39;);
		});
	}

When I run this migration, I get the following error:

&gt;  [Illuminate\Database\QueryException]                                 
&gt; SQLSTATE[HY000]: General error: 1025 Error on rename of
&gt; &#39;./dev_iwms_reboot/despatch_discrepancies&#39; to
&gt; &#39;./dev_iwms_reboot/#sql2-67c-17c464&#39; (errno: 152) (SQL: alter table
&gt; `despatch_discrepancies` drop foreign key pick_detail_id)
&gt;
&gt;[PDOException]                                                        
&gt; SQLSTATE[HY000]: General error: 1025 Error on rename of
&gt; &#39;./dev_iwms_reboot/despatch_discrepancies&#39; to
&gt; &#39;./dev_iwms_reboot/#sql2-67c-17c464&#39; (errno: 152)

When I try to reverse this migration by running `php artisan migrate:rollback` command, I get a `Rolled back` message, but it&#39;s not actually doing anything in the database.

Any idea what might be wrong? How do you drop a column that has a foreign key reference?

Dropping column with foreign key Laravel error: General error: 1025 Error on rename

After installing devise MODEL User i got this.

    class DeviseCreateUsers &lt; ActiveRecord::Migration
      def self.up
        create_table(:users) do |t|
          t.database_authenticatable :null =&gt; false
          t.recoverable
          t.rememberable
          t.trackable
    
          # t.encryptable
          # t.confirmable
          # t.lockable :lock_strategy =&gt; :failed_attempts, :unlock_strategy =&gt; :both
          # t.token_authenticatable
    
    
          t.timestamps
        end
    
        add_index :users, :email,                :unique =&gt; true
        add_index :users, :reset_password_token, :unique =&gt; true
        # add_index :users, :confirmation_token,   :unique =&gt; true
        # add_index :users, :unlock_token,         :unique =&gt; true
        # add_index :users, :authentication_token, :unique =&gt; true
      end
    
      def self.down
        drop_table :users
      end
    end

Now if i do rake db:migrate the users table will be created.

How can i revert this migration, i.e. how can I delete the users table using rake again ?

Ruby on Rails: How can I revert a migration with rake db:migrate?

I&#39;m trying to convert from a SQL Server database backup file (`.bak`) to MySQL. [This question][1] and answers have been very useful, and I have successfully imported the database, but am now stuck on exporting to MySQL.

The *MySQL Migration Toolkit* was suggested, but seems to have been replaced by the *MySQL Workbench*. Is it possible to use the MySQL Workbench to migrate from SQL Server in the same way that the migration tool worked?

Or is the Migration Toolkit still available somewhere?

  [1]: https://stackoverflow.com/questions/156279/how-to-import-a-sql-server-bak-file-into-mysql

How to export SQL Server database to MySQL?

I have a local database that is currently in it&#39;s second version and should now go to it&#39;s third version.

The code for the previous migrations was generated by another programmer so I am assuming I am doing something wrong here.

In my model there are around 30 classes, and inside the model folder there is a mapping folder and it contains the mappings for those 30 classes.

So now I added 1 new class in the same manner as those previous classes and then run the add-migration command in the Package Manager Console.

Infortunately I get an empty migration Up() and Down() method.


When I look in the database there is a __migrationHistory available with the previous 2 migrations. If I run my application now, the third migration is also added but obviously the new table is not being created because it&#39;s not in the Up() method.

What could I be doing wrong?

I think something is going wrong when scaffolding the previous migrations... It&#39;s like it can&#39;t find the new Code-First classes I have added.

This is my command:

    add-migration &quot;1.2&quot; -verbose -ProjectName &quot;MyEFproject&quot;

I am assuming that the scaffolding doesn&#39;t know where to look for the new class... or is this by convention that all model classes are just expected to be in the project?

Result of add-migration:

    namespace MyProject.Migrations
    {
    using System;
    using System.Data.Entity.Migrations;
    
    public partial class _1002 : DbMigration
    {
        public override void Up()
        {
        }
        
        public override void Down()
        {
        }
    }
    }


Sample of new Model Class:

    using System;
    using System.Collections.Generic;

    namespace MyProject.Models
    {
    public partial class MyTable
    {

        public string SomeId { get; set; }
        public string SomeText { get; set; }


    }
    }



Sample of new Mapping class


    using System.ComponentModel.DataAnnotations.Schema;
    using System.Data.Entity.ModelConfiguration;

    namespace MyProject.Models.Mapping
    {
     public class MyTableMap : EntityTypeConfiguration&lt;MyTable&gt;
    {

        public MyTableMap()
        {
            // Primary Key
            this.HasKey(t =&gt; t.SomeId);

            // Properties
            this.Property(t =&gt; t.SomeText)
                .IsRequired()
                .HasMaxLength(30);



            // Table &amp; Column Mappings
            this.ToTable(&quot;MyTable&quot;, &quot;database&quot;);
            this.Property(t =&gt; t.SomeId).HasColumnName(&quot;SomeId&quot;);
            this.Property(t =&gt; t.SomeText).HasColumnName(&quot;SomeText&quot;);


        }




       }
    }


Thank you,

EF migration shows empty Up() Down() methods

I have user_id fk column in my table

    $table-&gt;foreign(&#39;user_id&#39;)-&gt;references(&#39;id&#39;)-&gt;on(&#39;users&#39;);

I should add **on cascade delete** feature to this existing column. How can I do this?

Add &quot;ON DELETE CASCADE&quot; to existing column in Laravel

I&#39;m creating a model on the Laravel 5 with this command:

    php artisan make:model Settings

As it shows on the video lessons that as soon as model is created, new migration file also must be created. But, in my situtation, migration is not being created. 
How can I get the migration generated when model is created?

composer.json:

    ...
        &quot;require&quot;: {
                &quot;php&quot;: &quot;&gt;=5.5.9&quot;,
                &quot;laravel/framework&quot;: &quot;5.1.*&quot;
            },
    ...

Laravel make model with migration

My application needs a pre registered data set to work. So i need to insert them in the database when i set up the application.

[Laravel][1] propose two mechanisms :

 - [Database migrations][2] : *&quot;They allow a team to modify the database schema and stay up to date on the current schema state.&quot;*
 - [Database seeding][3] : *&quot;Laravel also includes a simple way to seed your database with test data using seed classes.&quot;*

When I read this description, none of these solutions seems to be adapted.

A similar question has been [asked on stackoverflow][4] and [answered][5]. The answer proposes to use the a database seeder to populate the database by detecting the current environment :

    &lt;?php
    
    class DatabaseSeeder extends Seeder {
    
    	public function run()
    	{
        		Eloquent::unguard();

                if (App::environment() === &#39;production&#39;)
                {
                    $this-&gt;call(&#39;ProductionSeeder&#39;);
                }
                else
                {
                    $this-&gt;call(&#39;StagingSeeder&#39;);
                }
    	}

    }

Of course, this solution works. But i am not sure that it is the right way to do this, because by inserting data using seeders you are losing all the advantages provided by the migration mechanism (database upgrate, rollback...)

I want to know what is the best practice in this case.

  [1]: http://laravel.com/
  [2]: http://laravel.com/docs/migrations
  [3]: http://laravel.com/docs/migrations#database-seeding
  [4]: https://stackoverflow.com/questions/18950438/laravel-db-seeds-test-data-v-sample-data
  [5]: https://stackoverflow.com/a/18951089/1594933

Laravel : Migrations &amp; Seeding for production data

According to the documentation here:
https://docs.djangoproject.com/en/1.8/topics/migrations/ it says:
    
    migrate, which is responsible for applying migrations, as well as unapplying and listing their status.

and

    makemigrations, which is responsible for creating new migrations based on the changes you have made to your models.

From what I understand, I first do

    makemigrations

to create the migration file and then do

    migrate

to actually apply the migration?

Do note though that I just began my Django project and I added my app to my &quot;installed_apps&quot; list. After that, I did

    python manage.py runserver

and it said 

    You have unapplied migrations; your app may not work properly until they are applied. Run &#39;python manage.py migrate&#39; to apply them.

It didn&#39;t mention anything about running makemigrations.


Django 1.8 - what&#39;s the difference between migrate and makemigrations?

When I change `help_text` or `verbose_name` for any of my model fields and run `python manage.py makemigrations`, it detects these changes and creates a new migration, say, `0002_xxxx.py`.

I am using PostgreSQL and I think these changes are irrelevant to my database (I wonder if a DBMS for which these changes are relevant exists at all).

Why does Django generate migrations for such changes? Is there an option to ignore them?

Can I apply the changes from `0002_xxxx.py` to the previous migration (`0001_initial.py`) manually and safely delete `0002_xxxx.py`?

Is there a way to update previous migration automatically?


Why does Django make migrations for help_text and verbose_name changes?

I just install EF 4.3 and trying to upgrade my project with migration. however I am getting issues with trying to execute `add-migration initial` to my project via Package Manager console. 

It is throwing any exception now `No connection string named &#39;MyApplicationEntities&#39; could be found in the application config file.` 

Now my config has it all 

    
    &lt;connectionStrings&gt;
    &lt;add name=&quot;MyApplicationEntities&quot; 
         connectionString=&quot;metadata=res://*/DataModel.csdl|res://*/DataModel.ssdl|res://*/DataModel.msl;provider=System.Data.SqlClient;provider connection string=&amp;quot;data source=localhost;initial catalog=MyApplicationEntitiesDB;integrated security=True;multipleactiveresultsets=True;App=EntityFramework&amp;quot;&quot; 
         providerName=&quot;System.Data.EntityClient&quot; /&gt;
  &lt;/connectionStrings&gt;

I am not sure what is the issue is it a bug in EF 4.3 or there is something I am not doing right. 



I thought [this post][1] has solved the issue but not quite.

Anyone got an answer. 

Appreciate Sanj. 


  [1]: https://stackoverflow.com/questions/7493337/entity-sqlce-cant-find-connection-string-in-app-config-file

No connection string named &#39;MyApplicationEntities&#39; could be found in the application config file

In my Rails 4 app I would like to collapse my migration files into one large file (similar to schema.rb) as it&#39;s time to do some housekeeping but I&#39;m not sure on how to access the table in the database that stores migration data so that when I run a migration I don&#39;t receive any errors/conflicts.

**Question** How can I access and delete the data in the table that stores migration data?

All Database Migration Solutions on Gang of Coders

Total of 23 Database Migration Solutions