Skip to content

Rename files in pegasus/migrations/ for alphabetization purposes.#9073

Merged
ashercodeorg merged 1 commit into
staging-nextfrom
renameFiles
Jun 21, 2016
Merged

Rename files in pegasus/migrations/ for alphabetization purposes.#9073
ashercodeorg merged 1 commit into
staging-nextfrom
renameFiles

Conversation

@ashercodeorg

@ashercodeorg ashercodeorg commented Jun 20, 2016

Copy link
Copy Markdown
Contributor

http://sequel.jeremyevans.net/rdoc/files/doc/migration_rdoc.html#label-IntegerMigrator+Filenames

Unfortunately, despite doing the natural renames (only appending zeroes), git apparently decided to permute the names of the noop files. Presumably this isn't problematic?

@aoby

aoby commented Jun 20, 2016

Copy link
Copy Markdown
Contributor

Is this reordering just git incorrectly matching up the files?
image

I suppose it doesn't matter since they're all noop.

@aoby

aoby commented Jun 20, 2016

Copy link
Copy Markdown
Contributor

Looks like all the migrations with actual content matched up correctly. LGTM. Make sure you test migrate & rollback locally just to be sure the 0 prefix doesn't mess up the sequel migrator.

@ashercodeorg

Copy link
Copy Markdown
Contributor Author

Yes, as noted in the summary, git seems to have permuted the files with empty migrations. Though confusing for the history, I see no other harm in this. Running rake db:migrate and rake db:rollback mostly work, some of the migrations fail for "natural" reasons.

@ashercodeorg ashercodeorg merged commit 84405f5 into staging-next Jun 21, 2016
@ashercodeorg ashercodeorg deleted the renameFiles branch June 21, 2016 14:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants