Skip to content

Support :change migrations in Rails 3.1 #42

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 2, 2011
Merged

Conversation

turadg
Copy link
Contributor

@turadg turadg commented Aug 11, 2011

Rails 3.1 adds :change as a way to specify a migration. Add it to the Annotate rake task so it picks those up.

@ctran
Copy link
Owner

ctran commented Aug 11, 2011

Seems like this would break for older version of Rails?

@turadg
Copy link
Contributor Author

turadg commented Aug 11, 2011

Hmm. I guess I don't understand that call then. I thought it was catching migrations of those types and would ignore them if they didn't happen.

I'd test it, but I can't actually get the annotation to happen on migration at all. The README is explicitly vague on how to accomplish this. Is it working for others?

@ctran
Copy link
Owner

ctran commented Aug 12, 2011

Now that I have time to read the change again, I think this may not break previous versions.
You don't see any things with "rake db:migrate:up"?

@turadg
Copy link
Contributor Author

turadg commented Aug 12, 2011

Nope. Maybe because I'm on Rails 3.1rc5?

I don't see anything in the logs either. I don't mind using the annotate command for now so I probably won't dig into it much further anytime soon.

turadg added a commit that referenced this pull request Sep 2, 2011
Support :change migrations in Rails 3.1
@turadg turadg merged commit 8d0b3c8 into ctran:master Sep 2, 2011
@ctran ctran added the released label Dec 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants