-
Notifications
You must be signed in to change notification settings - Fork 508
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
Don't know how to build task 'ar:auto:upgrade' #942
Comments
Can you type |
I'm using ActiveRecord, but mini_record looks awesome! I should try that.
|
I don't think activerecord has an 'auto:upgrade' task. That doc is probably wrong, the upgrade task is added by mini_record AFAIK. |
Which doc is that by the way? I will update for clarity. Sorry about the confusion. |
No problem, thanks for such a quick response. |
Interesting, thanks for the link. Any thoughts @DAddYE? looks like we did in fact manually add something like that to activerecord before. My suspicion is that once minirecord came out, people who want that feature may just want to use that instead. |
I man! Yup you are right, I've removed extra no AR code from padrino and put into |
Hey guys, sorry to bother but I figure while I have your attention.. I'm having trouble initializing my production & test databases. I'm using Postgres, but whenever I run migrate or reload, it automatically does it on the development database. This is problematic when I run padrino rake test. So I tried doing Oh! |
@joslinm Yeah |
I hope I'm not a bother, but I found that same inaccurate information in the docs two years later. So while this issue has been closed, the fix (updating the docs) does not seem to have been applied. |
In the documentation, it seems to indicate that I can use the
padrino rake ar:auto:upgrade
, but it's not working.mark@mark-laptop:~/dev/projects/bitfountain/yipp$ padrino rake ar:auto:upgrade
=> Executing Rake ar:auto:upgrade ...
rake aborted!
Don't know how to build task 'ar:auto:upgrade'
(See full trace by running task with --trace)
The text was updated successfully, but these errors were encountered: