Mix ecto.gen.migration creates empty migration

Yes, the migration is empty! Ecto doesn’t try to magically figure out the migration from the schema. That’s why the book explicitly asks why you fill this in:

defmodule Rumbl.Repo.Migrations.CreateUsers do
  use Ecto.Migration

  def change do
    create table(:users) do
     add :name, :string
     add :username, :string, null: false
     timestamps()
    end
    create unique_index(:users, [:username]) end
  end
end

You can probably find the exact snippet in the book.

Hi @josevalim, I missed that sentence. I was actually tempted to copy/paste from the book but I honestly thought it was auto-generated. My mis-perception came from my background in Python/Django where similar commands do generate the migration code…

I’m just an Elixir newbie learning new stuff. Thanks for helping!

Hi @2trc, are you still experimenting with Elixir? I’m also used (not too much though) to Django (I come from several years on SQLAlchemy, recently moved to Django mostly because of the ease of migrations there), and I’m a bit puzzled with ecto-migrations. I’m trying to document how they work, and help people with my same background grasp the concepts. maybe you want to have a look at my work in progress pull request, and comment.

Unfortunately not at the moment. I’m spending some time looking into :erlang (Programming Erlang and Designing for Scalability with Erlang/OTP). Going back to the basics

I hit the same question. haha, got the same answer here.