Migration file id clash across branches about migrate

[cihangir]

if i were the repo maintainer, i wouldn't care about finding a solution to this problem, to me this is purely SDLC/user problem. Timestamps can also create problems depending on their merge order to master.

[mattes]

@johnweldon added a fix to this. It will through an error if there are two files with the same id.

[gravis]

FYI, we're going to propose a PR soon for this. We just started to use the lib, and already have issues with version collision. Ruby on Rails did this change a few years ago for the same reason. Sequential versions simply don't work with large teams...

[johnweldon]

I've used Date+Time based migrations before which usually works, but the problem is bigger than just the naming of the migration. If you have two people doing a database migration at the same time you still have to manually inspect the two migrations to make sure they're compatible. Naming isn't the issue, and having the collision helps bring attention to the potential for conflict.