Generates two migrations with the same timestamp about devise-activegraph

[LXAfterDark]

I ran into this exact same problem not moments ago. Did a little digging and here's what I found.

At first glance it appears that the DeviseCreateUserConstraintsAndIndexes migration is not being created correctly. I took a gamble and changed the migration created by devise-neo4j from this:

class DeviseCreateUserConstraintsAndIndexes < Neo4j::Migrations::Base
  def change
    add_index :User, :email, force: true
    add_index :User, :remember_token, force: true
    add_index :User, :reset_password_token, force: true
    # add_index :User, :confirmation_token, force: true
    # add_index :User, :unlock_token, force: true
    # add_index :User, :authentication_token, force: true
  end
end

to this:

class DeviseCreateUserConstraintsAndIndexes < Neo4j::Migrations::Base
  def up
    add_index :User, :email, force: true
    add_index :User, :remember_token, force: true
    add_index :User, :reset_password_token, force: true
    # add_index :User, :confirmation_token, force: true
    # add_index :User, :unlock_token, force: true
    # add_index :User, :authentication_token, force: true
  end

  def down
    # drop_index :User, :authentication_token, force: true
    # drop_index :User, :unlock_token, force: true
    # drop_index :User, :confirmation_token, force: true
    drop_index :User, :reset_password_token, force: true
    drop_index :User, :remember_token, force: true
    drop_index :User, :email, force: true
  end
end

and the migration completed successfully once I reset and re-ran it. Unfortunately since I'm relatively new to Rails (or Ruby for that matter), I can't tell you why this worked. My best guess (read: pure speculation) is that the NotImplementedError is indicative of Rails not expecting to see def change in the migration.

EDITED TO CLARIFY: I ran into the same problem with both migrations getting the same timestamp as well -- everything I outlined above was what I did to get the second migration to work after changing the timestamp on the second migration as outlined in @leehericks' post above. So, best as I can tell, there's two problems that need to be solved for... the overlapping timestamps and the content of the second migration file.

[cheerfulstoic]

Hey @TheOneTrueLX thanks for this!

I think with your issue the problem is that the change method isn't supported by the neo4j gem's migrations. Probably it could be supported at some point.

I just created an issue in the neo4j gem repo to track this idea