More information about migration version

[eaglemoor]

Now goose use version by file prefix name like 0001_, 0002_...
But this way, have one trouble. If 2+ people create migration with prefix 0003_ (0003_create_user, 0003_create_address) and try push they code to release, they catch error. Who first apply migration to staging server, before include to release brach, win. Other can't apply migration, because 0003 already exist in db.

But, if migration version have name (filename from sql file or custom name from go file) it's don't happened.

[VojtechVitek]

See discussion at #63. This is a known problem that many people struggle with. However, the sequential numbers are protecting you from running the migrations out of order, which may cause very bad side effects in master branch that you couldn't see or predict in the development branch.

[eaglemoor]

datetime prefix is good solution