-
Notifications
You must be signed in to change notification settings - Fork 98
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
Migration Error #67
Comments
@BDoom can you provide more info? |
I'm using mysql, the latest gem version, and rails 5.2.3 ruby version 2.6.3. |
That's definitely a bug. I probably won't have time to get to the mysql version of it for a bit. Would you feel comfortable offering a PR? |
I would if I can find the solution first. I think it's just this line: Do you know what I need to change? |
Entire migration:
|
Would it be default, copy, or in place? |
Looks like :concurrently is simply only for Postgres databases actually. I think I could just use :inplace for now. But from what I can tell, :concurrently actually speeds up your database a lot lol. Maybe I'll move to postgres haha |
Yeah, mysql & postgres have different strategies. It looks like we'll need to set the algorithm dynamically depending on the db-type. :/ |
I just installed postgres and it worked fine. I'm not really attached to mysql, it was just easiest to install. |
ArgumentError: Algorithm must be one of the following: :default, :copy, :inplace
I get this when I simply run rails db:migrate
The text was updated successfully, but these errors were encountered: